Custom Speed Dial thumbnails – Vivaldi Browser snapshot 1.10.862.6
-
@g_bartsch Does it make sense to apply the lock to the Speed Dial page itself as an initial fix, then invest time to refine the Speed Dial UX as a whole later?
-
@Pesala The right-click (anywhere on the tile) was precisely what I was thinking.
-
@xyzzy I think that makes the most sense. Refreshing the Speed Dial and losing all of the thumbnails is the worst case to protect against. Replacing one thumbnail is not such a big deal.
-
@Pesala said in Custom Speed Dial thumbnails – Vivaldi Browser snapshot 1.10.862.6:
which requires no icon, and no accuracy.
This I like. My disability makes it difficult to right click with accuracy but the speed dial tile is a big target and easy to hit.
-
@xyzzy I would say yes, lock the whole SD page from refreshing at once. Maybe individual tiles could be refreshed themselves?
-
Soon-to-come snapshots will protect custom dials from F5 refresh.
-
In case anyone didn't see JuniorSilva30's thread "I'm creating some thumbnails for the Speed Dial, sharing ...", I have some good ones that go along well with Vivaldi's stock SD thumbnail style: https://drive.google.com/drive/folders/0BwcOkwtCjr51T0psOHJXb0M4VmM?usp=sharing
-
@D0J0P said in Custom Speed Dial thumbnails – Vivaldi Browser snapshot 1.10.862.6:
In case anyone didn't see JuniorSilva30's thread "I'm creating some thumbnails for the Speed Dial, sharing ...", I have some good ones that go along well with Vivaldi's stock SD thumbnail style:
And also is here some Gifs, if you are interested
-
@g_bartsch Yep, also like this
-
@nekomajin:
The only native thing you will have and get for the foreseeable future is the native window frame, if you set it like that in the settings.Other than that let me quote from https://vivaldi.com/ :
"One of the things that makes Vivaldi unique is that it is built on modern web technologies. We use JavaScript and React to create the user interface with the help of Node.js and a long list of NPM modules. Vivaldi is the web built with the web."Native GUI would mean: Add a framework like e.g. QT or build an own cross platform framework, make the browser heavier and throw out all of the options you have now or hack the framework into oblivion, only to maintain a huge bunch of window managers and operating systems that all can display HTML CSS and JS just fine inside of the browser window.
Does that answer the question about a native UI?
(mind: I didn't write "never", because I too can't look into the future - but definitely not with a team of the size as it is now)
-
@QuHno
I know it would be a huge task, but I don't see many features from the outside, that would be affected by a change like this.There was a time when native window design replaced the UI hacks, but it seems that they are constantly gaining more and more territory again. Sadly.
-
@g_bartsch Next snapshot will just ignore F5 reload on any custom thumbnail. To reload them, you need to explicitly select reload on the speed dial entry.
-
@derday: Oh that's right it's Super Mario Run! Thanks!
-
@QuHno It's not just a matter of "looking native" but behaving like a native app as well. You can't "fake it" or emulate it because you'll never get it 100% right. The whole purpose of using native widgets is so that you don't have to fake anything. In the macOS world, Camino lacked many features compared to Firefox but still had a loyal following because its platform integration was superb. It actually felt fast and lightweight too because it didn't implement its UI with XUL... and many Mac users liked it better because it didn't implement any of its UI with XUL.
Right now, on macOS, Vivaldi is somewhat broken from both an aesthetic and functional perspective. Native widgets may or may not be the answer but Vivaldi still has to behave properly in every manner on the platform. As longtime users, we're used to its quirks. For new users, it makes a really good first impression but can turn them off when it misbehaves in some really annoying ways.
It's like that kid in the restaurant... nicely dressed, quiet, well mannered, doesn't run run around... then he goes to the salad bar, grabs a pickle with his hands, takes a bite, doesn't like it, and puts it right back.
-
@xyzzy I understand that this is totally a personal preference and a matter of taste, but I find Vivaldi a beautiful application, I love the minimal UI design and clean language, choosing platform integration would throw that away right out the window, with all the work and investment made along with it.
Besides that it would basically triple the work necessary to maintain the UI. Right now you design the UI based on HTML+CSS+JS and it is mostly expected to work the same across all supported platforms, save for any occasional bugs or incompatibilities.
Native UI would require writing and testing and debugging the UI for three entirely distinct platforms (Win, Mac, Linux), plus different versions like Windows 7/8/10, KDE, Gnome, other desktop environments, different themes or combinations the user might have.
-
@duarte.framos As I understand it, devs also save hours each day, first of all, not having to figure out how to mold the features needed/wanted out of native elements and second, not having to wait forever for a native-elements build to compile. Development using web technologies is an order of magnitude faster than trying to reconfigure native elements to match the vision they are trying to execute.
When every day the browser remains unfinished is money out of Jon's pocket, one can understand the "need for speed."
-
@duarte.framos I don't disagree at all, and actually made the exact same points that you just did in a previous post. The reason we have the awesome browser that we have today is because Vivaldi took a platform-neutral approach.
That said, on macOS, there are a lot of things that look and feel out of place on the platform because Vivaldi tries but doesn't really conform to platform norms. It also lacks some of the basic platform integration that macOS users expect. Other "non-native" browsers do a better job of it and this is something that Vivaldi should aspire to do better as well. These "little" things matter, and that's the point that other users were simply trying to make.
To some, having a truly native look and feel is also just as important as it is for others to be able to apply a wooden veneer to the entire browser chrome, or to have Vivaldi "work like it does on Windows" on all platforms.
-
@xyzzy Currently there are only two minor problems on osx I feel. The absence of switching to the desktop Vivaldi is on, when you open a link from another one. The greyed out/disabled minimize button after being in fullscreen. Other issues I apparently don't care about, I wouldn't call it a problem overall. If you want a browser that is made for the osx environment, your best bet is Safari.
-
@luetage I'm not bashing Vivaldi. Quite the opposite. I want Vivaldi to grow and gain marketshare. However, as an advocate for the Mac community and the Vivaldi community as a whole, I'm simply agreeing with valid points that others are trying to make, including yours.
You have your issues that you would like to see fixed. My primary wish list consists of a Bookmarks menu, for colours and gradients to be faithful to the native OS, and to be able to set Corner Rounding in themes so that buttons and the URL bar can look right without other elements (that should be square) looking like squircles. Some want better macOS platform integration -- e.g. Services integration, Keychain integration, to be able to input emojis with Control-Command-Space, for Data Detectors to work properly... Others want Vivaldi to work with their third-party window manager, or for windows to simply maintain their correct size when you open a new one.
Some of the "native widget" advocates here could be Windows users too, but I understand and empathize as a Mac user as well.
The key to making any product better is to focus on your strengths and to improve on your weaknesses. If you don't, you'll die a death from 1000 paper cuts.
-
@Ayespy
I see all the reason against a native interface, but it does not have to be all native. Most of the features are connected to the engine and the internal pages. That's where the JS approach is very good. But a native window frame, including the scrollbars and native menus are not something they change every day. The only other component are the toolbars, but the appearance of those can be mimicked quite well even with CSS. I don't think it's such a huge task.