Extension management has come a long way... we now have a registry and
install/uninstall scripts, but it still leaves a lot to be desired in
terms of keeping track of what extensions work with a given version of
Radiant and at what point. Generally things are okay and you can just
install an extension and be pretty sure it will work, but there's
always a time around Radiant releases when extensions are in limbo.
I'd like to have us articulate a plan for conquering this sooner
rather than later.
My suggestions for requirements:
1.) Extension authors have a way of specifying a minimum Radiant
version with each release/revision of the extension.
2.) Extensions not be dependent on authors to specify compatibility
with newer versions of Radiant. If the extension was last updated in
2008 but it works for 0.8 without changes, you don't have to do a
thing. I want to avoid the Firefox Add-ons problem where I upgrade FF
and my extensions are disabled because their authors are behind the
curve. Too pessimistic for my tastes.
3.) Perhaps some way of the community saying, "this extension needs
fixing before it will work with 0.8." And a way for the extension
maintainer to clear that note once they make the upgrade. (Maybe just
an all-users-writable text field per extension in the registry)
4.) The extension install script installs the latest compatible
version of an extension.
5.) Easy upgrades. One command to upgrade Radiant and all my
extensions.
Discuss.
Sean, you mentioned you had an idea about how extension gems might
work. I'd love to hear it when you're ready. I think gems could help
solve many of the above requirements.
Jason
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
