On Wed, Apr 25, 2012 at 9:23 AM, Damien Accorsi <[email protected]> wrote: > Hello Alessandro, > > It seems that it's exactly what I'm looking for. I'll test it, but as you > are the developer I have two questions for you (I ask them here because I > believe they may be of some interest for other people): > > 1. What about configuration parameters? I like to parameterize stuff in the > development.ini / production.ini. Should plugable application get their own > .ini or should they be mixed together in the main .ini? >
tg.config object inside the plugged applications will be the same of the application where they are plugged in. So usually you will write your options inside the same .ini file of the main app. > 2. What about pluggable apps dependencies? I mean... For example, in my > pluggable_app_1, I'd like to add links to pluggable_app_2/feature_A; but I > do not know yet where the app 2 will be mounted. Is there a way to get that > parameter? Or to parameterize it? (I mean... there is a way, for sure, but > maybe you already defined something for that use case; if so, this is what > I'm looking for). > You can specify required dependencies inside the setup.py of the pluggable app. If you want to automatically plug them you can do that. The plugme method of pluggable apps is able to plug any other number of apps. Usually I tend to prefer reporting an error saying something like "app X requires app Y to run, please plug it in". But I can see why someone would want to automatically plug used apps, keep in mind that in that case you must check that you are not plugging again an already plugged application. -- You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
