@Chris J. Davis While plugins are somewhat tied to the version and must be updated because capabilities change, there is no good reason why themes could not work from version to version without modification (except if you encourage themers to tie to core software libraries). This forces themes to be version dependent, when they do not have to be.
Encouraging themers to tie to the Habari core libraries is short- sighted and will ultimately lead to development compromises due to fear of breaking legacy code references. Including a ~50kb jQuery file or better yet, a CDN link in your theme to ensure version independence is not stupid and is common practice in many CMS packages. I disagree with the goal of providing theming tools (not plugin, as they are tied to core), as ultimately, you are making a lot of assumptions for the theme designer. What if I want to use another javascript library or CSS framework? It is best for Habari to remain agnostic in these regards, allowing the theme designers to make these decisions for themselves. In the future, instead of simply writing off an idea as stupid, maybe we should be actually discuss the merits (pros AND cons) of what is being said. Help people understand where you are coming from. ------- Colin On Apr 26, 6:07 pm, "Chris J. Davis" <[email protected]> wrote: > Colin was advocating either having them include their own (which is > stupid) or calling googles. I am not in favor of either method > honestly but I was one of the proponents of having Habari provide > plugin and theme developers an up-to-date environment that includes > all the tools they need. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
