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?
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).
Thanks for your answers (and for this extension)
Damien
On 04/25/2012 01:05 AM, Alessandro Molina wrote:
Take a look at pluggable applications, they are meant to do this kind of things:
http://www.turbogears.org/2.2/docs/main/Extensions/Pluggable/index.html
On Tue, Apr 24, 2012 at 3:17 PM, Damien Accorsi<[email protected]> wrote:
On 04/24/2012 03:05 PM, Damien Accorsi wrote:
Hi all,
I'm developping a web application with several services. I'd like to
build this application as a SOA (service oriented architecture)
platform, so that it will be easy to update and/or add services.
The way I'm about to write my application is to build TG applications
like this:
- base application (including global model, authentication, master
template, etc)
- app_1 including brain for a batch of services (lib, templates,
controllers)
- app_2 including brain for another batch of services (lib, templates,
controllers)
- ...
Everything being linked with the base application.
For example, the parts I'd like to add to the base application are:
- reusable icons
- helper functions
- ORM and data model
- base templates
What would be the best way to do? Should I do something like tg
extensions or tg applications? (I believe TG applications is the right
way to do...)
What method for development? Working with "virtual" eggs like if I add
installed my applications? Is there any tutorial about this?
Thanks for your help.
A related question is: how do you manage dependencies between
modules/applications? By setup parameters? Hard links? ...
Here comes an example: I want to manage two types of media, eg. video and
photo. I'd like to build a "video" application which will allow to
add/edit/delete/search/share videos. I'd also build an application for
similar tasks for images (but also including images from other websites, for
example). => 2 applications.
Both will allow to add comments, tags, etc. => another application?
Would you make something like "application inheritance"? What about a
"helper" comment application?
Damien
--
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.
--
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.
