Sells,

this is interesting. But what about the integration with the framework? I
mean, I can import a plug in, but I still need to create a template and to
give a url, etc.

2011/4/5 Sells, Fred <fred.se...@adventistcare.org>

> There are guys in this group who are much more sophisticated meta
> programmers than I.  But here's a very simple method:
>
> It is easiest if each unique module has the same class name, such as
> "class Controller:"
>
> Then define and import all your plugins (does not allow uploading
> plugin, but that's risky anyway).  You can get all the files in your
> plugins dir and import them using the python function (forgot it's name,
> don't use it) or just eval ('import %s' % filename)  crude but works for
> older python
>
> Create a dictionary of key:module's
>
> Mymodule = ModuleDictionary[somekey]
> Workingobject = Mymodule.Controller(**parms)
>
> -----Original Message-----
> From: django-users@googlegroups.com
> [mailto:django-users@googlegroups.com] On Behalf Of alessio c
> Sent: Tuesday, April 05, 2011 9:40 AM
> To: Django users
> Subject: [Suspected Spam] Django app for data management and
> visualization
>
> Hello,
>
> I am thinking about starting a Django app to manage data (I need it
> for financial reporting).
>
> What I am wondering about those days is a way to create an application
> that:
>
> 1) Allows the privileged user to insert a "plug in" that adds a module
> and its views.
>
> 2) Allows the user to add views and "scripts" to an existing model.
>
> The way I think this is a model centric application with different
> views and file uploaders. For me this would be a break out as we use
> to run different reports from the same dataset (just changing the
> grouping, filtering, formulas). I need file uploaders as the same
> model can be populated from different files, organized in different
> ways.
>
> Do you have some aviced on best practices to achieve this? I don't
> want the user to touch the main web site when adding modules and
> views.
>
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>
> --
> 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+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to