Speedial is very poor
-
You will note that I did not respond to Unhived. I never do. I did respond to ANOTHER user on this thread, as I sometimes will, But I do not post in response to the self-important ravings of the originator of this thread. I was the one, in fact, who first recommended such a course of action.
Of course Tiamarth, or anyone, may engage in whatever sort of recreation they chose.
-
I'm not here to stir Vivaldi beer goggle fans, I'm here to hopefully push Vivaldi into sorting out their most obvious problems. Now simply because I'm a fan of the new Opera and admit it then the beer gogglers seem to think I cannot criticize their favourite ALPHA browser they set as default on their computers. It must really hurt that someone can point out flaws with your favourite browser. When Vivaldi gets its act together at some point soon then I will no longer have any complaints and may end up using the browser. Vivaldi can't afford to have mere sheople followers who at most might find a tiny bug here and there, they need people to push them into getting important things corrected like the functionality of the browser. Who cares if website x crashes, it's an alpha right? But I care if the browser itself crashes or doesn't complete a task. If more of the beer gogglers pushed Vivaldi to sort out that speed dial then maybe Vivaldi would've completed the task by now but instead months and months on we still cannot have saved dials stored and only the last two releases have captured dials well. Why do the beer gogglers brag about how good the speed dial is compared to the competition when the competition at least presents their dials when requested. Right now the best speed dial is Opera as it looks reasonable compared to all except Vivaldi but more importantly Opera's dials save well. My only anger at Opera is that we cannot seem to save the dials to a file no more and instead rely on sync or manual. I've asked Vivaldi to also make their speed dial savable to a file.
Ayespy has often ragged on Opera but he uses the best browser currently available like I do but at least I'm not a hypocrite. The reason characters like Ayespy try to avoid tangling with me is simply because they cannot thought reform me or win any battle as evident in the past. I'm not here to suck up to Vivaldi because I was a fan of the old Opera which after a long time I dumped for Palemoon x64. I'm here to occasionally have a moan about what I dislike on the browser because I'm fed up of getting the itch to try Vivaldi only to be let down time after time by something that hasn't been fixed. When I have to get the geek uninstaller out after five minutes on Vivaldi I get angry because I was excited as installing then let down. I want to keep this browser on my system for longer than 5-10 minutes. I have numerous other browsers on my PC but they're portable files apart from Opera. Right now if I had to choose four browsers to have on my PC it would be OPERA, CyberFox, Maxthon and Palemoon when dealing with Windows. So as you can see I'm not a beer goggler and I used rational thinking. It's very interesting that the gogglers will make Alpha excuses for numerous issues with Vivaldi but they also admit they use the browser as default??? Using Vivaldi in its current state as default shows the beer goggles are on maybe using superglue for added effect. As I've said before I'm not here to give a damn about beer gogglers or anyone else on this forum other than those in Vivaldi who might make a change for the better with their browser. Collectivism isn't appealing so if someone isn't individual then I'd rather they didn't address me. I was the only being who gave Vivaldi a couple of screens of data on what their browser could add and change when they first released the browser, no one else spent as much time as me going through issues so when someone says I've done nothing constructive then it shows the lack of worth and knowledge. I often find if a being shows intellect, rational thinking and can type more than one sentence unlike the collective linguistic minimalism then those collective show signs of fear and anger.
-
No problems with Speed Dial here either. There's always room for refinements later, but there are many other more important features to add and improve before they get around to things like customisable thumbs.
[attachment=1832]SpeedDial.png[/attachment]
Attachments:
-
I'm not here to stir Vivaldi beer goggle fans, I'm here to hopefully push Vivaldi into sorting out their most obvious problems. …
What you are actually here to do is to push your own agenda for what you think is most important during the early development of a browser - and you want Vivaldi to drop whatever they're doing and alter their development priorities and matrices to match your particular list of priorities. Don't you think other folks on these forums, as well as Vivaldi's devs, are already abundantly aware of the points you keep raising? Don't you read the threads and dev blog comments? Are you suggesting Vivaldi devs simply aren't smart enough to fix your pet issues? My belief and my experience indicate that they'll deal with those things in due time, primarily when it makes sense to apply the necessary effort to kill off those issues without disrupting their entire flow of development of everything else they believe they need to do at this stage. Sure, the things you point out are significant… but so are a lot of other things. Who are you to rant and rave about what Vivaldi "ought" to be doing with a design whose development flow, scheduling, and resource constraints you have not an ounce of insight into? You so obviously have no concept of the real-world nature of an alpha-stage development project that you are really embarrassing yourself here.
-
No problems with Speed Dial here either. There's always room for refinements later, but there are many other more important features to add and improve before they get around to things like customisable thumbs.
There's no problem in making dials to look just like your photo especially as the capture has been improved (only in the last two releases) but the problem is that those dials never store for long and all we end up with is empty dials unless we do a trick found by another user which is very cumbersome especially for multiple dials. Are you trying to tell me you never lose your dials? I use the x64 experimental version for Windows.
-
I'm not here to stir Vivaldi beer goggle fans, I'm here to hopefully push Vivaldi into sorting out their most obvious problems. …
What you are actually here to do is to push your own agenda for what you think is most important during the early development of a browser - and you want Vivaldi to drop whatever they're doing and alter their development priorities and matrices to match your particular list of priorities. Don't you think other folks on these forums, as well as Vivaldi's devs, are already abundantly aware of the points you keep raising? Don't you read the threads and dev blog comments? Are you suggesting Vivaldi devs simply aren't smart enough to fix your pet issues? My belief and my experience indicate that they'll deal with those things in due time, primarily when it makes sense to apply the necessary effort to kill off those issues without disrupting their entire flow of development of everything else they believe they need to do at this stage. Sure, the things you point out are significant… but so are a lot of other things. Who are you to rant and rave about what Vivaldi "ought" to be doing with a design whose development flow, scheduling, and resource constraints you have not an ounce of insight into? You so obviously have no concept of the real-world nature of an alpha-stage development project that you are really embarrassing yourself here.
I don't think I'm embarrassing myself by asking Vivaldi to improve the main browser performance. I just don't see the point in making a speed dial and a decent one at that only to spoil it for months on end with what I would expect is something not that difficult to fix. It took months to be able to capture a full dial and I hope it's not going to take more months just to store a dial. We''re hearing Vivaldi talking about soon being at beta stage and yet it still cannot perform a speed-dial need for the users. I just cannot comprehend why people think it's more important to throw features into a browser than fix what you already have let alone something as important as a speed dial which hits you almost from the start of the browser. Vivaldi are old and new school Opera people and considering Opera has almost always done everything right almost from the get go then I cannot see why Vivaldi can let itself down on simply tasks. Why have a speed dial without allowing it as either the home button or having its own separate button as in Opera? What I'm trying to say is that whilst fancy features are fun they're not always as important as the simplest ideas and its just a fact that so far Opera has always been spot on with the simplest ideas that work so well. If the speed dial was working then I would stand more chance of using it as a default browser if the resource usage was better. I have no agenda, some said I worked for Opera, well ask Opera if they employee internet users to promote their browser, they've been laying important people off so don't hold your breath. My only wish is to see Vivaldi come to a standard of operation with the browser that Opera has or close to it. I'm open to a new browser and always will be if something is better. I just cannot over hype something or forgive something just because of a name or a clan of past browser creators. If Vivaldi produce the goods then I will give them as much credit as I give Opera over others maybe more. If that happens I'll get the same crap again by others claiming I'm a paid Vivaldi cheerleader. Brand snobbery is very belittling to those who do it for the wrong reasons. I'm not going to buy Nike sneakers just because you like them, I only want them if they work and suit my needs. Brand snobbery is what is ruining competition.
-
For me, SpeedDial works. One small feature I would like to have is a possibility to select the size of the SpeedDial Buttons.
-
@ OP
Get Well Soon -
@TurkishCoffee:
@ThomasMo I would also like to see them scale because I don't like to have to scroll it… that said it's not really a dealbreaker.
Greater flexibility in both the size of the speed dials and the number of columns is sure to come along, in keeping with the overall goal of the browser.
-
Software is always Alpha or Beta at a developers discretion, and nobody that understands Alpha status will be claiming it is perfect in any way.
Only the fans that don't read instructions will be claiming any such nonsense.
You know the ones. The ones that comment on each new Alpha or Beta of anything with "Awesome, this is the best news ever", because they don't understand the responsibility and problems of being a tester.
All they want is something newer, or with a bigger number, or more exclusive, than their friends.
None of them will ever use the official bug reporting systems, and just post in blog comments or forums, always forgetting to write the useful info that is required.
Here is a good example. Vivaldi have https://vivaldi.com/bugreport/
It is the only way I report bugs here, as forum posts create extra unnecessary admin, and means the devs have to try to read threads, when they should be working on the next ticket.I wish we would just go back to the days of Alphas being closed projects, and the Beta being what the public get to play with (like the Avira "Scout" browser is being done. Much more sensible bug reporting there).
We also seem to have abandoned the traditional "It is not v1 until it is out of Beta".
Becoming v1 used to be a big deal to the authors, and it was a day of pride.
Now the lines are blurred,Vivaldi is trying to build a stable framework, but also adding the features that users demand at the same time.
Each time they add a new feature, a new problem is very, very, likely to happen, because the framework is not yet stable.
The public are just getting to see what software developers and testers have to put up with, and they don't like it.You will know when they will be considering Beta, because this forum will have less angry people shouting their demands.
That will be because it is finally reasonably stable for most people, and will have all the main features and most of the minor features.
Depending on how things go, a Beta stage could easily take another year, although at the rate Vivaldi are adding features there won't be much to do but test and fix during Beta, so maybe it could be less than 6 months.My primary browser is Opera 12 for basic browsing (forums and media streams), and Firefox for secure or logged-in browsing.
I only use Vivaldi and Avira Scout for "testing" purposes, because they are not ready to be trusted for primary use.
Avira browser was only offered to the public once it reached Beta, so it is faster and more stable (by a huge margin).
However it came out of closed Alpha very fast, because they could concentrate on the framework first, and now features are being added through Beta, so they will also have a long Beta stage.
Depending on how things turn out I may still be happily using Firefox for many years to come, and either Vivaldi, or Scout will be my second browser.
Chromium does not allow certain functionality that is very important, so certain security extensions / features are not possible.Oh BTW. Any time the speed dial is empty for me, I just restart Vivaldi to get them back, but experience will vary to mine and it may only work for some.
-
I'ma basically quote myself so that I don't have to write it all again. With respect to the "modern" development process, this way of doing things is dictated by the fact that Chromium keeps releasing new engine versions, and Google keeps DeFacto changing web standards by releasing new versions of Chrome based on these engine versions, rapid-fire:
_Once a Vivaldi Beta stream is started, one assumes there will be betas upon betas forever. Really hard to say at this point how many beta versions there might be before there is one declared "Stable."
But if Vivaldi follows a similar development pattern to that of Chrome and Opera, Vivaldi Beta and then "Stable" versions will be built on top of the same engine we have now, Chromium 45.
Then a snapshot with additional features will be released built on Chromium 46, and it will be debugged until it's Beta-ready, and then we will have Stable on 45, Beta on 46, and then a new snapshot will be introduced on top of Chromium 47, new features will be added and it will be debugged, etc. Features will ONLY be added to snapshots, never to Beta, the Beta stream will be ONLY for debugging, optimization and stabilization with no new features added to a browser that has been declared Beta, and when a Beta is good enough and clean and stable enough, it will graduate and become the new Stable.
So there will be three version streams at all times - Stable, which never gets any updates except security updates and engine updates WITHIN ITS WHOLE NUMBER LINE (in other words, the very first stable would get only updates to the 45 engine and would never get the 46 engine), Beta, which is built on the next whole number engine version above Stable, and is for bug-fixing and stabilization only, and Snapshots, which will be built on the next newer engine version than Beta, and which will be where features are added, and the kinks are worked out for the new engine, because EVERY TIME Chromium puts out a new engine version, it breaks shit that was working fine on top of the last version.
Chromium, in fact, has FOUR streams, being Stable, Beta, Developer and Canary. Right now there are Chromium Canary-level browsers on Chromium ver. 48. Opera has Stable, Beta and Developer versions on 45, 46 and 47, respectively.
So really all we can know is, when Vivaldi thinks the browser built on the 45 engine is ready for prime time, no matter how many Beta releases that takes, it will be dubbed "Stable" and a whole new series of Betas will be begun to get ready for the next "Stable" release.
Vivaldi could really only follow the old traditional development pattern if it were writing its own engine._
-
The reason the above pattern is necessary is because the engine keeps changing, and Vivaldi can do nothing about that but try to keep up.
The reason it's possible is because once a version is Stable, it basically can be ignored, absent some glaring and urgent bug that escaped unfixed in Beta or the occasional engine or security update.
So then, developers only have two tasks to do, which they are ALREADY doing, and that's debug (beta) and add new features (snapshot). Even a crew of limited size, which is already doing these two functions, can manage a division of labor so that they don't get left in the dust, stuck on Blink 45, while everyone else is already on Blink 50.
-