A game of ‘Opera tag’ - 5 things I’d like to see in Opera
Friday, 27. July 2007, 03:04:00
I was tagged by: Claudio Santambrogio aka Csant, Non-Troppo, Pallab, Tobias Murano aka Tomu and Ayush.
Originally posted by Daniel Goldman:
- looks like I have to post 5x5 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.Once you’ve been tagged by someone, share your list (on your blog) of 5 things you’d like to see in Opera
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 5x5 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
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
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 5x5 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)








Tim Altman # 27. July 2007, 12:21
Christian # 27. July 2007, 12:48
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.
Pallab De # 27. July 2007, 18:32
Tim Altman # 7. August 2007, 14:12
Christian # 10. September 2007, 01:52
New development techniques using Opera Kestrel (9.5)
Originally posted by Chris Mills:
Opera 9.5 alpha is out
Originally posted by Daniel Goldman:
Dev.Relations
Originally posted by David Storey:
but 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:
Though some older words pointed towards core-2 as rendering engine, which are corrected in a comment: New Rendering Engine, Core 2
Originally posted by Saito:
comment:Originally posted by Petter Nilsen aka Mitchman2:
Tim Altman # 10. September 2007, 15:17
GemRain # 13. October 2008, 16:17
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!
GemRain
PS. sorry for shouting.