On Wed, Dec 23, 2009 at 6:34 PM, W. Martin Borgert <[email protected]> wrote:
> Quoting "Noah Kantrowitz" <[email protected]>:
>> Just remember the alternative is that every plugin has its own copy. However
>> much work it might be to retrofit Trac to use a central version, it will be
>> much harder to do this for every plugin that wants to use jQuery UI.
>
> No question: This would be worse.
>
If plugin X (packaged as deb) depends on `trac` for obvious reasons,
and Trac depends on jQuery then there is a transitive deps
relationship. So I suppose that no further work will be needed (`trac`
will always be a dependency for the plugin ;o), isn't it ? In the end
he will end up making reference to the js files using `/chrome/common`
If a plugin author doesn't wanna assume the challenge that's (his|her)
choice in the end, and he will have one of three options :
- do not include the widgets (... and IMHO that means to be frozen in time
and obviate the benefits of lovely useful widgets provided by JS UI libs ;o)
- bundle jQuery UI with the plugin code (i.e. a lot of copies of the
lib js files
and an even worst scenario than a single copy inside Trac if packaged
as a deb ;o)
- reinvent jQuery UI (no further comments)
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Assessment of unittest 2.7 API : new features and opinions -
http://feedproxy.google.com/~r/simelo-en/~3/cVOgG8NIBFY/assessment-of-unittest-27-api-new.html
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
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/trac-users?hl=en.
