On 9 Jul 2012, at 09:08, Olexiy Chudnovskyy wrote: > Hi Scott, > > yes, we've already tried Opera widgets - unfortunately many of them are > broken.
Well, a lot of them use Opera's own earlier spec rather than W3C - which mostly just looks like a broken wgt. There are also a couple of W3C widgets on the ROLE widgetstore: http://www.role-widgetstore.eu/ And of course you can do a search for .wgt files, e.g. on Filecrop - that mostly turns up a lot of clock and weather widgets for different phones :) Part of the issue is that most of the other implementations tend to rebrand W3C widgets - e.g. as "samsung apps", "blackberry widgets", "vodafone widgets" etc., and then only allow download via their services or devices. > We haven't found any W3C repository - the only idea we came up with > - converting iGoogle, Netvibes, Opera to W3C to create some initial > database. A student of us is working on a conversion tool, tackling > peculiarities of different formats. Currently he is evaluating which > percentage of Netvibes / iGoogle widgets the tool will manage to convert. > First results were pretty promising. Thats a great idea. I had some code for converting Chrome Installed Apps into Widgets; its probably outdated now, but its on Github if he wants to reuse it: http://scottbw.wordpress.com/2011/02/17/converting-chrome-installed-web-apps-into-w3c-widgets/ > > Best Regards, > Olexiy > --- > Chemnitz University of Technology > Department of Computer Science > Distributed and Self-organizing Systems Group > Straße der Nationen 62 > D-09107 Chemnitz > Germany > E-Mail: [email protected] > WWW: http://vsr.informatik.tu-chemnitz.de/people/chudnovskyy > Phone: +49 371 531 39146 > > >> -----Original Message----- >> From: Scott Wilson [mailto:[email protected]] >> Sent: Monday, July 09, 2012 9:59 AM >> To: [email protected] >> Subject: Re: Extending widgets towards Inter-Widget-Communication >> >> >> On 9 Jul 2012, at 08:50, Olexiy Chudnovskyy wrote: >> >>> Hi Ross, >>> >>>> >>>> I suspect the best way to proceed is to start out extracting your >>>> code >>> into the >>>> stand-alone project we've discussed. It would be best to do that in >>>> stages contributing patches directly to Wookie as you go. This will >>>> enable us to evaluate individual contributors patches and recognise >>>> individual merit as appropriate. It will make things a little slower >>>> to start with as you will >>> need >>>> someone here to submit your patches to version control. However, >>>> since nobody here is likely to work on it in the short term this >>>> shouldn't pose >>> much >>>> of a problem. >>>> The advantage is that we would be able to give commit rights in >>> recognition >>>> of the work being done during the porting. >>>> >>> >>> I think this is the best option. As soon as we have IWC-Enchancer >>> extracted out of Wookie I will come back to you. >>> >>> One other question - do you know if and where we can find some >>> real-life W3C widgets to experiment with? Are there any widget >>> repositories existing on the Web or being developed in other projects >> (beside OMELETTE)? >> >> Opera have some: >> >> http://widgets.opera.com/ >> >> .. though not all are W3C-compliant >> >> A lot of the other widgets around seem to be locked into mobile >> operator/handset vendor app stores e.g. Vodafone, Samsung rather than >> publicly downloadable via the browser >> >> >>> >>> Best Regards, >>> Olexiy >>> >> > >
