On Aug 10, 7:23 pm, osimons <[email protected]> wrote: > On Aug 10, 2:14 pm, Bart Ogryczak <[email protected]> wrote: > > > Hi, > > I'm currently working on plugin, which requires a) additional tables, > > and b) JQuery-UI. > > > What are the best practices concerning this? > > First the tables. Is there any standard when the should be created? In > > the setup script? Some 'first-run' script? > > Here is a quite clean implementation you could 'borrow' - i'm still at > version 1 of db schema, so it just has placeholders for future > upgrades which also needs to be handled gracefully: > > http://trac-hacks.org/browser/fullblogplugin/0.11/tracfullblog/db.py
Nice, but has downside -- causes the Trac to go off-line with message about needing env upgrade. I'd rather have the environment set up while installing the .egg. > > How about JQuery-UI? Including it in every plugin which would need to > > use it seems waste, so what other alternatives are? > > Like John says, add it in process_request() if its only needed when > handling requests to your plugin. Sure, that's not the problem. The problem is that now I have jquery- ui.js in my plugin's /js/ dir. It's ok, but I'd be better to actually share jquery-ui between plugins. I think the easiest way would be to create jquery-ui plugin containing only the jquery-ui.js. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
