Call it a plug-in, not a widget when it’s really a plug-in. Pretty Please?
Tags :Plugins widgets catalog update site deployment
We need to have a long talk, mr developer. Yes we do. I am getting slightly frustrated at the number of "widgets" being placed into catalogs (OpenNTF, Greenhouse and more) that are shown as widgets. They make the instructions read to just drag and drop this into your widget box. Yes for a widget that would be correct.
The moment that widget tries to prompt me to install plug-in code from a remote site it changes the game. The security mechanisms are different. The controls are different. The policies are different. The updating architecture is different.
Go watch this webcast, see what some of the differences are and come back and label all your widgets to the appropriate name. Yes, you are allowed to deploy plug-ins via a widget. Fully supported. But it is not a widget.
This plug-in XXX is deployed via a widget
Just say that. Also make your plug-in downloadable to place into my site updates. Not yours. I don't let my users just go anywhere to get code. That is what policies and proper site update management is for.
"Deploying Plugins and Widgets for Lotus Notes and Sametime" - the webcast from Consultant In Your Pocket
blog comments powered by Disqus
On Monday, October 25th, 2010 by Chris Miller
