Daniel started a great thing with Blog tag: 5 things I’d like to see in Opera. If the spreading remains at the current speed it will be, well, let's count-guess, Millions of posts in quite a short while … This has potential to get a hype (well, if it stops before we reach the Million we'll have to add another Opera tag question, maybe about 5 tips towards using the Opera browser).
I was tagged by: Claudio Santambrogio aka Csant, Non-Troppo, Pallab, Tobias Murano aka Tomu and Ayush.
Originally posted by Daniel Goldman:
Once you’ve been tagged by someone, share your list (on your blog) of 5 things you’d like to see in Opera
– looks like I have to post 5×5 points which actually came in handy as I already started wishes including a cluster of several things. Now I try to do 5 wishes each having about 5 somehow connected points.
A collection of links to many people's posts taking part in this Opera tag game can be found at the ChooseOpera blog. And Remco Lanting made a nice tagging tree.
Well, just when I was about finishing this post I got notice to be tagged another time by burnout426. Nonetheless I'll stick with 5×5 right now 😉 …
…
I think Opera is already a very useful power tool to get access to WWW and email and I'm looking forward to Opera being improved even further with Kestrel and Peregrine. My wishes will be more imaginative for a future that might be a bit more far away (although I wished to already have this features, well, I dream of it).
1. Save & monitor text in form-fields
Autosave (at least on demand) text-input on webpages to Opera notes (automatically into a subfolder related to the URL) as the instant letter by letter saving is just genius. This should probably be saved together with an offline version of the page. Offer to track changes (replies to your input, esp. useful for posts, comments etc.) on the page – one difficulty would be to define the correct landing page, so probably it is much easier to implement and the same time more powerful for the user to separate saving and tracking and make tracking available for any page. The tracking result could be displayed as custom RSS feeds (even for pages that don't provide them). As it would be nice to organize this by date&time just integrate it as one viewpoint of the new calendar 🙂 I trust in the Opera people to make it work together very clever.
Note: similar tracking (not saving) functionality is provided by online services like co.mments and coComment.
2. Sophisticated control of add-ons
Implement integrity information for all customizations like especially Widgets and userJS and maybe even Skins, CustomButtons, settings etc. For userJS and Widgets this could be realized by required tags at the beginning of the code (maybe together with hash codes of the used files if it's critical for security). For customized buttons and other settings there could be an online-check instead: the users can upload one or several files with the user applied configuration and there could be syntax checks etc. which returns information about the status of this (this could also be used to check the required tags of userJS and Widgets). For all the add-ons the user would get a status like o.k. / depreciated / update available / security risk etc. – as you can see this would be greatly complemented by automatic updates for this parts. Furthermore if this files could be saved (online or offline) it would offer the capability to synchronize and transfer settings (and even something like preferences sessions). To make it complete there should / could be a control mechanism to select which parts should be uploaded, exported or imported (together with the preferences session management this control panel could be used as something like an userJS&more manager). Well, this sounds well connected for me but reading it again I do not really know what this would look like.
3. Unified service and support on Opera.com
Put all things you can download to customize Opera on one subdomain of Opera.com and call them Add-Ons or Extensions (do not differentiate between the technical means in presentation and search but just focus on the needs or benefits for the user). Equally unify and improve the documentation (www.opera.com/support/, help.opera.com/, www.opera.com/docs/ etc.) – yes, I know, it is already improving. An official FAQ should be really simple to do – even a bad one could answer a lot of questions many new users will have (as Opera actually is looking for new users). Tips could make the browser more interesting and the features better known (just think about 30 days to become an Opera lover). Additionally deliver a more complete documentation (including change logs) for developers of skins, buttons etc. – it is a shame that Opera fans have to document changes and reverse engineer (hack) the possibilities of Opera's GUI-API (AllActions), Skin (AdvancedSkinGuide) etc.
The target of all this should be to provide user oriented support and service with unified starting points for new users, normal and advanced users and developers. Each of this has to be split up for different platforms desktop, mobile, mini and devices. I think this proposal should be refined although I'd wish the main point would be realized: one collection for all support and help stuff and one collection for all add-ons.
4. Magic UI
I have the idea to use the magic power of CORE2 Presto (the forthcoming rendering engine of Opera) to provide the visible parts of the user interface. This should make it quite a bit easier and faster to adopt Opera to run on any device (for the Opera developers). It is the idea of Opera Platform aka Opera Widgets applied to the Opera Browser itself. And there is already an interesting concept with Wiiminder enhancing the UI of the Wii and also a Webrowser panel by Shoust allowing you to browse in a panel. The functionality is still limited due to the limitation by Opera's great security concept. I'd think it should be relatively easy to add some parent nodes to the DOM tree delivering access to the new browser elements. I do not know whether it is possible to make the used (XHTML+CSS+JS) code completly accessible for customizations, which would provide the possibility to generate "real" extensions (powered by JS and WebStandards) and to completely exchange the chromeless chrome (funny, isn't it?). One possibility to have this in the real world would be a Second UI or Web UI which could be provided additionally besides QUICK – while Quick would serve as standard on Desktop the Web UI would bring the power to the devices and deliver the ability to completely tweak Opera on desktop, where a switch is needed to toggle the chrome on/off. Maybe it is even possible to bind native UI elements from the OS to the Second UI for those asking for better integration in some special environments like MacOSX or GTK. Although I think this idea is more than just a nice thought it will require lots of thoughtful inspection and huge amount of initial work for the developers.
5. Customizable and better UI defaults for Opera Mobile for WM
Yet another wish about UI, now towards another great browser: Opera Mobile for Windows Mobile. I'd wish Opera would make benefit from the possibilities that already are there. You can switch to another skin pretty easy but yet there is nothing to download and no place provided to make the community provide a skin (except hidden in the forum). This is simple. And it would make Opera Mobile more interesting and outstanding. As I am more interested in functionality I'd even more wish to have some menu.ini providing the possibility to have my own customized menus with the functionality I mostly use provided with fewer clicks. There could be also different setups provided by Opera. For one of it I'd wish better default menus and keyboard shortcuts for Pocket PCs empowered with a touch screen and non spatial navigation (Opera Mobile feels pretty optimized for phones with a keyboard). At best there should be a much easier and quicker access to toggle such important settings like drag+scroll and spatial navigation.
I'll not tag 5×5 but only 5 people – all of them Opera users as I'm not yet active on a different blog topic:
Blinkybill (Australia)
Friedrich (Germany)
Gerður Jónsdóttir aka MediumGeek (Norway)
Grafio (Poland)
Jan Standal aka Think (Far north)
Note that the rendering engine is not called Core-2. The rendering engine is still called Presto. Core-2 is a version idenitifier for all the core code, which does include the rendering engine.
Junyor, thanks for the clarification. This is good to know and I updated the post. So do I understand it right that Core-2 is the core code used on all the platforms, which contains the rendering engine and some surrounded stuff (like API) and which is part of Kestrel and Peregrine? So the difference between Core-2 and Opera Desktop would be GUI, M2, IRC, BT, the panels and some other extra features.
I would really like to see #2 being implemented.
@ResearchWizard: No, that’s not really correct either. Core-2 is a version of our Core code a la Mozilla 1.9. Core-2 is already used in Merlin and will be the basis for Kestrel and Peregrine. Core-1 was the basis for 8.x.
Junyor, now I’m confused again, not really because of your comments but because of some posts by Opera employees that write about core-2 as the new rendering engine of Kestrel. I suppose you’d need some clarification inside the company as well.New development techniques using Opera Kestrel (9.5) Originally posted by Chris Mills:Now that Opera has fully migrated to the new version of its rendering engine, Core-2, Opera Kestrel has a few new techniques available for developers to play with. Opera 9.5 alpha is out Originally posted by Daniel Goldman:Opera 9.5 alpha uses the new rendering engine, core-2, the same used on Opera Mini 4.Dev.Relations Originally posted by David Storey:Their upcoming Foleo product uses the Opera Core-2 rendering enginebut also by David, a bit more obscure, pointing towards core-2 is not the rendering engine Kestrel spreads its wings on test flight Originally posted by David Storey:the engine that went into making Core-2Though some older words pointed towards core-2 as rendering engine, which are corrected in a comment: New Rendering Engine, Core 2Originally posted by Saito:Though Merlin, Kestrel or Peregrine are code for browser inside the company, core 2 is a code name for the rendering engine, the heart of browsers. comment: Originally posted by Petter Nilsen aka Mitchman2:”core-2″ is the the core platform and not just the rendering engine. core-2 was also used for merlin, although in an earlier incarnation. Opera Mini 4 uses the very latest of the core-2 code (which still uses “presto” as the layout engine), the same core-2 branch that kestrel will use.
Yes, I’m not surprised. Basically, they (except Petter) are referring to it wrong. Again, the rendering engine is still Presto, but the code-branch (AKA version) of *all* core code (including the rendering engine, network stack, etc.) is core-2. It’s a code-name, the same as referring to Opera for Desktop as Merlin or Kestrel.
WOULD SOMEONE WRITE A “RIGHT-CLICK” or “LEFT” that will close the current tab that is open. One thing that I don’t need is to move the mouse from the center of the screen to close the currently viewed tab. Sorry for shouting. I beleive that OPERA is the best browser, and I am glad that I found it.I need a better Opera browser for my Palm Centro, too. I am back to surfing on the computer with Opera because it is so good. But my life truely revolves around my Centro, and the Opera mini keeps crashing it. Must be time to look for a newer firmware update even though I just performed this last month.BTW: I LOVE THE BLACK BACK GROUND AND WHITE TEXT!GemRainPS. sorry for shouting.
any new wishes ? 🙂
Jonquil writes:Something like an integrated Belvedere would be nice for automatically organizing downloads based on file type, size, keywords, etc. along with the usual operators. As a student, this would really be convenient because lecture pdfs would be automatically placed into the appropriate folder. But, of course, that is just one example. There are probably programs other than Belvedere (which is buggy at best) that do this, but a browser integration would be quite neat.