[development] Migrate users from Thickbox to Colorbox

[Fredrik Jonsson]

I'm the maintainer of Thickbox and co-maintainer of Colorbox. The Thickbox 
script is getting a bit old and I think Colorbox could be a good upgrade path. 

What are your tips and suggestions on how to best help/encourage the 17000+ 
Thickbox users to migrate?

* Is a hook_upgrade() function to automatically update the "Display fields" 
settings a good idea?
* Should I after some time unpublish the releases of Thickbox?
* Any other tips?

For people interested in checking out Colorbox I recommend the 6-dev version. 
There are a lot of changes there that soon will be released as beta 3.

http://drupal.org/project/colorbox

Fredrik

-- 
Web site: 
Drupal stuff: 

Re: [development] Migrate users from Thickbox to Colorbox

[nan wich]

Fredrik Jonsson wote: 
> * Should I after some time unpublish the releases of Thickbox?
This is an easy answer: Yes. But it may be longer than you think.

Consider that, according to the Thickbox usage stats, more than 60% of your 
users are already using an "unpublished" version (i.e. below the current 
official release). So they aren't paying much attention to the flag that the 
Update module is giving them.

My experience is that many users will only be dragged into the present kicking 
and screaming.

 
Nancy E. Wichmann, PMP
Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.

Re: [development] Migrate users from Thickbox to Colorbox

[Daniel F. Kudwien]

> What are your tips and suggestions on how to best 
> help/encourage the 17000+ Thickbox users to migrate?

Whatever you do, you will not be able to encourage or force users to
migrate.  Most users are just happy when they manage to get JavaScript stuff
like this to finally work properly on their sites (if at all).  "Never
change a running system."


> * Is a hook_upgrade() function to automatically update the 
> "Display fields" settings a good idea?

If I would migrate one of my sites, then I'd have to re-configure,
double-check, and manually test all occurrences.  Automagical updates always
scare me a bit, FWIW.  Since I will need to properly re-configure my site
anyway, it's not worth the trouble for you as maintainer to implement such a
upgrade path.


> * Should I after some time unpublish the releases of Thickbox?

Unless you are strictly enforced to do this (security issues), releases
should not be unpublished.  You can configure, which releases are supported.
A notice on the project page would help new users to choose the right
module.


> * Any other tips?

Yes, but we'd have to lock Stella, tstoeckler, others and me into a room
without windows and networking to talk about it.


sun