What happened to the Widgets?
Friday, 30. October 2009, 08:40:44
In our recent Desktop Team blog post, "Post-seminar Unite build", certain users in the comments section seem to be unsure what we are doing with Widgets, after previously showing them off running as stand alone applications in the "Opera Widgets for Desktop Labs release" blog post. There also appears to be an underlying confusion about what all the various releases are about (Stable, Beta, Snapshots and Labs).
Let me attempt to make it clear. I can't promise I'll succeed as I think we have done a pretty good job already and yet some are still confused, so what do I know?
Let me attempt to make it clear. I can't promise I'll succeed as I think we have done a pretty good job already and yet some are still confused, so what do I know?
We will be making Widgets full applications. That is the long term goal. Don't get thrown by the fact that we have subsequently released Opera versions where they are integrated with the browser. Remember that the Widget release, was a 'Labs release'. It is exactly the same as with the Video 'Labs release'. Both of these features are coming ... just not yet.
The 'Labs releases' are to show off ideas for major new features and to give some outline of our future vision. When a cool new feature is only appearing in a Labs release, you shouldn't worry too much about the Opera version number that is actually displayed. The 'Labs' label trumps this. Labs releases are very much about experimental features or stuff that is early in development cycle and hence they have not been assigned to a fixed version number of Opera yet.
Outside of Labs, lets look at the other stuff. As I write this post, the 10.0* line is the current stable browser. It is the only current 'proper release' of Desktop and the version that the vast majority of our users are actually using right now. Potential future versions numbered 10.02, 10.03, etc. won't have Unite, or any other major new feature. If there are further updates, it is a line that will consist of security and bug fixes for what we released as 10.00. The 10.10 Beta 1 is a Beta of the next release with a new major feature (Unite). In addition to the Beta, we have snapshots of the work that has happened subsequent to the Beta, one of which is what we offered in the "Post-seminar Unite build" blog post.
On a personal level I must admit I am baffled as to why certain people are having trouble with this? This is a pretty common and standard way to release new software and show off major new features. Other software companies do exactly the same thing. Also, even if you are one of the people who is confused, don't forget that Labs and Snapshots are just stuff provided for testing. They are not guaranteed to be consistent. Indeed they are not even guaranteed to be stable!
With complaints from certain people, It does feel like there are those that would prefer that we released less. And yet at the same time I have also heard cries from others that we should offer up even more. We do after all have more things we are working on (Carakan, newer versions of Core, etc.).
So to people who feel that it is all too confusing, I would echo the comments of my some of my colleagues and honestly advise you to stick with the stable releases. There is only one of these at any given time and hence no room for confusion. If we have to spend significant amounts of time constantly re-explaining what we are offering up for testing, it lessens the likelihood that we will do so frequently. This is not so good for the users who do 'get it' and who are keen to try everything new we offer up.















Galileo # 30. October 2009, 10:25
FreeBrain # 30. October 2009, 11:49
Daniel James Hendrycks # 30. October 2009, 11:58
Originally posted by ruario:
I didn't see any issues with it when we tested it, what was wrong with the current code?
Ruari Ødegaard # 30. October 2009, 13:04
That said, the team in Poland working on Widgets for the Desktop are doing a great job
To semi-answer your question, there are still quite a large number bugs, and also a number of things we'd like to do to improve the experience. I won't go into a list here though as I don't want to stray too far from the topic at hand, nor am I really permitted to recreate an open bug tracker within my blog.
netwolf # 30. October 2009, 18:51
(I really wonder what's so hard to understand about that)!
It's great the we (users) get lab, alpha, beta and nightly versions (besides the finals of course
Personally, I'd even love to get more (and more frequent) builds to play with.
Especially now that 10.10 will (hopefully) soon be released, I'm really looking forward to Carakan, new Presto etc.
Keep up the great work!
furue # 30. October 2009, 21:00
I was following the main 10.10 line when I tried the lab build and played with the new widget handling just for once. Then I returned to the main line to find widgets stopped working. I had to manually clean up what's left by the lab release. This was because the lab version overwrote my ~/.opera and left other files under my home directory.
To avoid this problem, I suppse a "branch" version should be installed as a separate application without overwriting the existing settings. (It could import existing settings without overwriting them.) It could use ~/.opera-lab to store settings and be installed as "Opera Lab" separately from "Opera" in the main menu.
Daniel James Hendrycks # 30. October 2009, 21:27
Originally posted by ruario:
Well, I just used two widgets on my OS. A weather and calculator widget. So as far as I could see it was well ironed. I should have reviewed more before I spoke.
Ruari Ødegaard # 30. October 2009, 21:30
One thing I would advise you to do, given you are a Linux user is to scan through my earlier blog post where I discuss testing snapshots cleanly. Particularly the 'Method 3' section. None of it may be new to you but just in case.
P.S. I would also advise backing up your ~/.opera regularly if you like to test snapshots and labs builds (just in case).
furue # 2. November 2009, 19:47
Originally posted by ruario:
Wow. That's comprehensive. Thanks for the tip, which is certainly the way to go when testing a "branch" build just for a short while.
Originally posted by ruario:
Thanks.