Where are the bookmarks in Opera 18?
-
soundinhell last edited by
Opera has become the worst browser and I have tried them all.
Where do I import my Opera bookmarks backup?
Why no bookmarks in this horrible updated browser?
Where's the quick bookmark bar that was on top of where you type the website urls?They must have been totally drunk when removing these essential features. Speed Dial is useless like it always was.
Some may say this is whining but its not. Things such as Bookmarks shouldn't be removed from a browser.
After using it for almost 5 years I must say goodbye Opera, you won't be missed after this.
-
Deleted User last edited by
Originally posted by Pesala:
Instead of importing 4,000 bookmarks to Speed Dial, import them to the Quick Access Bar (aka Bookmarks Bar).
Unfortunately, the Quick Access Bar/Bookmarks Bar appears to be an undocumented feature. At least in the Opera help site, which loops back on itself, and never actually allows access to help searches.
1) "Help is just a click away. Select your product:" (Opera for computers in my case)
2) Help for computers: Help Files
3) Search help (anything you want). Enter.
1) "Help is just a click away. Select your product:"
...While people at Google do such a good job at creating a gratifying UX, Opera seems to be intent on the opposite. Only 10% of users use bookmarks—might those be the ones we'd call "power users?" Throw them under the bus! This is why I abandoned Opera years ago after being an early advocate (even paid for the thing).
I just reinstalled it after reading a reco for free Mac apps, and couldn't agree with the OP more. I can't criticize people for being proselytizers for Opera, but I do think I understand better why users of Opera accounted for a whopping 1.2% (Hey, more than Netscape!) of my company's web site visitors last month.
-
-
Deleted User last edited by
Originally posted by LeoCG:
Originally posted by priehl:
Unfortunately, the Quick Access Bar/Bookmarks Bar appears to be an undocumented feature.
Because it's experimental yet and not enabled by default on the Stable version.
I appreciate this explanation, but still: ROFLMAO...the year is 2014 and a bookmarks bar has to be 'experimental'-- because it's such a new concept?
-
Deleted User last edited by
It may be 2014 but I don't think you fully understand the incredible amount of work to rewrite a browser from scratch. THAT is the reason many features are still experimental.
-
-
Deleted User last edited by
Whatever. I'll take the developers' word for it. They're rewriting the Blink browser from scratch. You choose to believe whatever you like. Bottom line: no one cares what either of us believe anyway.
-
Deleted User last edited by
Originally posted by leushino:
Bottom line: no one cares what either of us believe anyway.
It certainly appears that way. For a company whose browser market share is basically a rounding error, you'd think there would be some concern for users. I've provided feedback to developers of several miniscule apps, and received grateful replies, and several of my suggestions have been implemented in the next release.
Opera? Under the bus with you, whiner!
-
-
-
scorpiopt last edited by
Originally posted by missingno:
Forking Chromium doesn't qualify as "rewriting a browser from scratch".
specialy wen the removed it in the first place chromium has bookmarks by default
-
blackbird71 last edited byOriginally posted by Scorpiopt:
Originally posted by missingno:
Forking Chromium doesn't qualify as "rewriting a browser from scratch".
specialy wen the removed it in the first place chromium has bookmarks by default
Do you even realize how a web browser works? It has a rendering engine (a core block of code) that processes the code from a website and makes the result available for display, but the user almost never interacts with the rendering engine - he uses an interface engine that converts commands corresponding to browser "features" into commands that the rendering engine can understand. This is much like a computer, where a user interacts with an application program, which in turn makes use of the code in an underlying operating system.
Opera adopted the Blink rendering engine (which is a fork or variant from Chromium's WebKit), but rather than utilize somebody else's existing interface code, it chose to develop its own hopeully-unique interface from scratch. That means browser "features," to be included, must be coded from essentially nothing to work in whatever way Opera wants them to work, all the while still obeying the coding rules and requirements needed to properly support or communicate with the chosen rendering engine. There are literally thousands of coding nooks and crannies that must be worked out, all without cross-interfering with each other - and all competing for scarce developer resources and scheduling time.
The only way Opera could have "removed" Chromium's bookmarks is if they had adopted Chromium's user interface and cut that part out of it - which they did not, simply because they never adopted that user interface. They chose to write their own from scratch, and bookmarks didn't receive enough initial priority as a feature to merit the necessary initial development time.
Certainly, one might argue over Opera's choice of features to emphasize in initial designs or whether they properly ascertained the priorities of some of them (and I have, elsewhere). But it's erroneous to argue that they cut out something that was never in that which they adopted in the first place. In any case, Opera is free to choose how to develop the browser however they want... and Opera users are free to accept the results or not, If they don't like it, they can always ask for their money back.
-
Deleted User last edited by
Originally posted by blackbird71:
If they don't like it, they can always ask for their money back.
Ever the master of gently-veiled sarcasm.
-
Deleted User last edited by
Originally posted by blackbird71:
... and Opera users are free to accept the results or not, If they don't like it, they can always ask for their money back.
So can users of Google Chrome and Firefox, but they won't over an issue as silly and simple as this.
-
scorpiopt last edited by
Originally posted by blackbird71:
Originally posted by Scorpiopt:
Originally posted by missingno:
Forking Chromium doesn't qualify as "rewriting a browser from scratch".
specialy wen the removed it in the first place chromium has bookmarks by default
Do you even realize how a web browser works? It has a rendering engine (a core block of code) that processes the code from a website and makes the result available for display, but the user almost never interacts with the rendering engine - he uses an interface engine that converts commands corresponding to browser "features" into commands that the rendering engine can understand. This is much like a computer, where a user interacts with an application program, which in turn makes use of the code in an underlying operating system.
Opera adopted the Blink rendering engine (which is a fork or variant from Chromium's WebKit), but rather than utilize somebody else's existing interface code, it chose to develop its own hopeully-unique interface from scratch. That means browser "features," to be included, must be coded from essentially nothing to work in whatever way Opera wants them to work, all the while still obeying the coding rules and requirements needed to properly support or communicate with the chosen rendering engine. There are literally thousands of coding nooks and crannies that must be worked out, all without cross-interfering with each other - and all competing for scarce developer resources and scheduling time.
The only way Opera could have "removed" Chromium's bookmarks is if they had adopted Chromium's user interface and cut that part out of it - which they did not, simply because they never adopted that user interface. They chose to write their own from scratch, and bookmarks didn't receive enough initial priority as a feature to merit the necessary initial development time.
Certainly, one might argue over Opera's choice of features to emphasize in initial designs or whether they properly ascertained the priorities of some of them (and I have, elsewhere). But it's erroneous to argue that they cut out something that was never in that which they adopted in the first place. In any case, Opera is free to choose how to develop the browser however they want... and Opera users are free to accept the results or not, If they don't like it, they can always ask for their money back.
Looool really? like opera and chrome have very different interfaces right now, months since its release the browser is still in a piss poor shape with no real improvements what so ever
With less features than even the original chrome , and having to go to huge workarounds to get such basic feature back and the Qab is not a replacement for bookmarks
Opera is going on an terrible path
love the sarcams coming from fanboys like you -
jmiichell last edited by
I can't quite understand what all the fuss is about.
Bookmarks work fine for me either on the Bookmarks Bar or with the Bookmarks Manager add-on.
Importing a bit over 2,000 of them was also easy.
-
Deleted User last edited by
Originally posted by jmiichell:
I can't quite understand what all the fuss is about.
Bookmarks work fine for me either on the Bookmarks Bar or with the Bookmarks Manager add-on.
Importing a bit over 2,000 of them was also easy.
Thanks for the heads up on the Bookmarks Manager extension. It works well.
I still find the Quick Access Bar puzzling and useless. No organizing bookmarks, just dumping them one by one into it?
-
scorpiopt last edited by
well on the dev version that extension is broken due to extension windows being blank
-
Deleted User last edited by
Originally posted by Scorpiopt:
love the sarcams coming from fanboys like you
Blackbird is not a fanboy. Your problem is quite simple: you haven't a clue what you're talking about. You simply do not understand what constitutes a browser.
-
Deleted User last edited by
Originally posted by priehl:
I still find the Quick Access Bar puzzling and useless. No organizing bookmarks, just dumping them one by one into it?
Actually, if you do a search through Pesala's posts, you'll find a very useful post in which he demonstrated "how" to set up your QAB with folders nested within folders... not dumping bookmarks onto it one by one as you say.
