Comments on: Converting a MiniAPI module to a UWA widget (part 7) http://dev.netvibes.com/blog/2008/03/19/converting-a-miniapi-module-to-a-uwa-widget-part-7/ News and articles about the Netvibes API Fri, 16 May 2008 20:52:03 +0000 http://wordpress.org/?v=2.5 By: Xavier http://dev.netvibes.com/blog/2008/03/19/converting-a-miniapi-module-to-a-uwa-widget-part-7/#comment-4663 Xavier Tue, 25 Mar 2008 17:15:21 +0000 http://dev.netvibes.com/blog/2008/03/19/converting-a-miniapi-module-to-a-uwa-widget-part-7/#comment-4663 Yes, there is a way. It is the subject to a forthcoming blogpost, but I'll give directly give you the end of the story: widget.readOnly :) This Netvibes-specific property is logically set to true on Universes, and to false anywhere else (where the widget is supposed to be able to read & write data, and not only display it). Yes, there is a way. It is the subject to a forthcoming blogpost, but I’ll give directly give you the end of the story: widget.readOnly :) This Netvibes-specific property is logically set to true on Universes, and to false anywhere else (where the widget is supposed to be able to read & write data, and not only display it).

]]> By: jeremy http://dev.netvibes.com/blog/2008/03/19/converting-a-miniapi-module-to-a-uwa-widget-part-7/#comment-4662 jeremy Tue, 25 Mar 2008 13:39:23 +0000 http://dev.netvibes.com/blog/2008/03/19/converting-a-miniapi-module-to-a-uwa-widget-part-7/#comment-4662 Now that I implemented this method. It seems that something is a little annoying. When you add a UWA widget with custom preferences into your universe, everyone can acces to the edit panel (of course), but it seems like the options aren't saved. Can you confirm this? It can be a little unsafe if we imagine a developper putting login/password into his custom preferences part. Of course the developper needs to deal with it but is there a way to detect if we are in a universe page or not? Now that I implemented this method. It seems that something is a little annoying. When you add a UWA widget with custom preferences into your universe, everyone can acces to the edit panel (of course), but it seems like the options aren’t saved. Can you confirm this?

It can be a little unsafe if we imagine a developper putting login/password into his custom preferences part. Of course the developper needs to deal with it but is there a way to detect if we are in a universe page or not?

]]> By: Xavier http://dev.netvibes.com/blog/2008/03/19/converting-a-miniapi-module-to-a-uwa-widget-part-7/#comment-4611 Xavier Thu, 20 Mar 2008 14:11:22 +0000 http://dev.netvibes.com/blog/2008/03/19/converting-a-miniapi-module-to-a-uwa-widget-part-7/#comment-4611 Yes, using widget.setValue(name, value) will save the value, even if the widget has no preference of this name. Yes, using widget.setValue(name, value) will save the value, even if the widget has no preference of this name.

]]> By: jeremy http://dev.netvibes.com/blog/2008/03/19/converting-a-miniapi-module-to-a-uwa-widget-part-7/#comment-4603 jeremy Wed, 19 Mar 2008 22:19:20 +0000 http://dev.netvibes.com/blog/2008/03/19/converting-a-miniapi-module-to-a-uwa-widget-part-7/#comment-4603 Well, what I mean is actually in my widget, I have a preferences part with all the user params I want to store in hidden fields: [widget:preferences] [preference name="period" type="hidden" defaultValue="7" /] [/widget:preferences] In my custom preferences form, when I save, I use: widget.setValue('period', period); to store in my hidden fields. My question is: is it useless to add the widget:preferences part in my widget or is it just another security to be sure that my data are stored in a correct UWA way? Well, what I mean is actually in my widget, I have a preferences part with all the user params I want to store in hidden fields:

[widget:preferences]
[preference name=”period” type=”hidden” defaultValue=”7″ /]
[/widget:preferences]

In my custom preferences form, when I save, I use:

widget.setValue(’period’, period);

to store in my hidden fields. My question is: is it useless to add the widget:preferences part in my widget or is it just another security to be sure that my data are stored in a correct UWA way?

]]> By: Xavier http://dev.netvibes.com/blog/2008/03/19/converting-a-miniapi-module-to-a-uwa-widget-part-7/#comment-4599 Xavier Wed, 19 Mar 2008 18:13:49 +0000 http://dev.netvibes.com/blog/2008/03/19/converting-a-miniapi-module-to-a-uwa-widget-part-7/#comment-4599 Hey Jeremy, could you be more precise about your final question? If you intend to have them saved with you widget's configuration, custom hidden fields should also be stored using <code>widget.setValue()</code>. But your method of putting these hidden fields in the standard UWA <code>widget:preferences</code> format can relieve you from some work :) Hey Jeremy, could you be more precise about your final question? If you intend to have them saved with you widget’s configuration, custom hidden fields should also be stored using widget.setValue(). But your method of putting these hidden fields in the standard UWA widget:preferences format can relieve you from some work :)

]]> By: jeremy http://dev.netvibes.com/blog/2008/03/19/converting-a-miniapi-module-to-a-uwa-widget-part-7/#comment-4598 jeremy Wed, 19 Mar 2008 17:51:37 +0000 http://dev.netvibes.com/blog/2008/03/19/converting-a-miniapi-module-to-a-uwa-widget-part-7/#comment-4598 Currently I'm doing the same on my <a href="http://eco.netvibes.com/widgets/230121/tv-shows" rel="nofollow">TV Shows</a> widget. Mainly to deal with internationalization. The only difference was that I keep hidden fields on my preferences definition to save data. What I can see from this point of view is that we don't have to store data in hidden preferences fields ? Currently I’m doing the same on my TV Shows widget. Mainly to deal with internationalization. The only difference was that I keep hidden fields on my preferences definition to save data. What I can see from this point of view is that we don’t have to store data in hidden preferences fields ?

]]>