• From: Las Vegas, NV
  • Registered: 2007-11-20
  • Posts: 31

Topic: Posting new versions of widgets

Just reworking a couple of my widgets,
And I'd like to talk about updating vs replacing.

I know the current rule is that any update is a complete replacement.
If not updaing the parameters, then it should be possible to just update the guid of the new piece,
With the guid of the old piece.

I wouldn't matter if the client ran the old or new version,
As long as all parameters are the same.

The only thing that would break a widget would be a new parameter.
Requiring a new verison.

Anyhow, it's something that needs looked at.

CRJ
Charley Jones, PMP
A+ MOUS MCP MCSA MCSE MCDBA MCAD MCT MCTS MCITP PMP ITIL
Founder & President: S3OLV.Com    Founder & President: LVXUG.Com

dataman's Website

2 Reply by jforsythe (edited by jforsythe 2007-11-26 08:44:37)

  • From: San Francisco, CA
  • Registered: 2007-11-01
  • Posts: 98

Re: Posting new versions of widgets

Perhaps adding new XML parameters should just require more diligent validation for those still using the old version of the widget.

For example, if you currently use X and Y to store parameters, in version 1.0. And now in version 1.1 you use X, Y and Z, you should add default values for Z to your widget if you can.

If not, maybe add a notification screen to let the user know that the new version needs additional attention @ the configuration panel.

-John Forsythe
www.jforsythe.com

jforsythe's Website

  • From: Las Vegas, NV
  • Registered: 2007-11-20
  • Posts: 31

Re: Posting new versions of widgets

That's actually a pretty good idea.
Default all new parameters,
And make sure users are aware of the new version.

MS published a note to that effect once.
Ok to make changes to a function as long as the parameters (singature) does not change,
The moment you change parameters though, needs a new function name.

Applying that here,
New versions should default all new parameters,
And warn users of new version.

I've noticed some problems with caching though.
On the Chumby side and the Website side.
While working on my last config widget,
I noticed I had to dumb browser cache,
To see the new version.
Seems like a forced browser expiration for config controls is in order.

Lots more to talk about on this subject.

Perhaps it's time to start working up a FAQ on how to create, post, update widgets.

CRJ
Charley Jones, PMP
A+ MOUS MCP MCSA MCSE MCDBA MCAD MCT MCTS MCITP PMP ITIL
Founder & President: S3OLV.Com    Founder & President: LVXUG.Com

dataman's Website