I just started a new open source project aimed at small companies that would
need a tool to manage its resources
(http://github.com/myOpenCompany/myOpenCompany not much to see at the
moment...), and one of the central idea would be modularization:
For example, we will start with an "employee" and a "hardware" module. The
hardware module allows tracking the phones and laptops affected to
employees. In the employee property page, the list of hardware for this
employee is displayed.
Now, if the company does not need the "hardware" module, the property page
will of course not contain this information. This is implies some kind of
dependency between the two modules, and that the "employee" module is somehow
aware of the information that the "hardware" module can provide.
The application will contain probably many modules (attendance management,
skills, missions, training...)
Being still quite new to django, I have some very basic questions on this:
* Should each module be a django app ? Or is it something different ?
* Is there already something existing (a third party app ?) to provide this
kind of mechanism ?
* If not, does anyone has experience implementing such behaviour ?
Thanks in advance for any feedback,
Guillaume
--
Skrooge, a free, Open Source, personal finances software
http://skrooge.org
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment