Tim Gossett wrote:
None of the models would be renamed (right?), so users should be able to
swap out the existing extension directory for a renamed one and get off
without a hitch. If I had a few spare moments, I'd try it for myself right
now... maybe there'd be a clash with the version number in the
extension_meta table, and maybe there wouldn't because it's listed as
"Styles 'n Scripts".
No, I can keep the "Styles 'n Scripts" name in the meta table and in the Admin-Extensions page. So all that would be needed is for the user to update to the latest version of SnS and to change the "styles_n_scripts" folder name to "sns". (Or change the /vendor/extensions folder's properties if using svn:externals).

But for me it does require renaming all the rake tasks, the xx_extension.rb file, and probably something else I'm not thinking of.

I'd also probably change StylesNScripts::Config to SnS::Config (and there would be a *bunch* of references to that that would need to change accordingly). Not strictly necessary but something I'd want.

-Chris
_______________________________________________
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to