On 4/3/06, Jorge Godoy <[EMAIL PROTECTED]> wrote: > Let me explain with a "simple" application as a company control system. > Imagine the following parts of an application: > > - Financial > - Administrative > - HR > - Suppliers > - Clients > - ... > > Now, each part has its details and intrincacies and they can be developed > independently and tied together in the end. > > If I wish to apply some XP to this, I'd model and code each of these parts and > then release, one by one, to my client. So, I started with the part where > there's more common code: > > - Suppliers > - Clients > > There I developed contracts, contacts, some basic CRM, contract validation and > expiration, contract renewal, etc. Then these modules were both deployed. > Now I want to develop the HR part to record employees data. > > But since I can use this employee structure in other projects, I'd like to > make it as generic as possible and "plug it" into my applications. (In fact, > the application would start with all these basic modules and evolve to the > specific activity that the client performs, for several clients and different > activities, but I'd like to have this common base shared among all projects, > so this example is not 100% accurate but it shows the problem.) > > What would be the best way to do that? Entry points? Plain modules? How > about using the specific layout -- master.kid and other templates -- for each > client or application that depends on this common part? What would be the > best approach for that in TG 0.9 and later reusable on FirstClass?
The value of entry points, and the point at which you know you want them, is when you want something to happen automatically *just by installing a package*. That's the key. For example, if you install a package of widgets, those widgets show up automatically in the Widget Browser. No configuration necessary. For your example above, it's entirely likely that you'll want to compose those apps into a single system via some kind of configuration (be it a Python script or the ini config files). That configuration step would likely work in place of entry points, because you'd specifically mention which pieces you want to pull together. In 0.9, your best bet is to hook things up CherryPy-style. That means to attach the subapps to your main app. Right now, there's an issue with how you'd handle static files, but I just opened a ticket that, when completed, would solve that problem and get things ready for First Class. Ben's right about template search paths, which is a feature we'll need for sure for First Class, if not sooner. Kevin Kevin > > (If my question wasn't clear, please ask me to explain better :-)) > > -- > Jorge Godoy <[EMAIL PROTECTED]> > > > > -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk -~----------~----~----~----~------~----~------~--~---
