Have you seen the dbsettings [1] app? If I'm understanding you
correctly, it does everything you want.
[1]: http://code.google.com/p/django-values/
On Fri, Mar 28, 2008 at 8:15 AM, Alberto García Hierro <[EMAIL PROTECTED]>
wrote:
>
> Hi Django developers,
> In first place, let me introduce myself. I'm a free software
> developer, mostly focused on PDAs running Linux. I think 90% of the
> code I've wrote in my live has been in C, but I've loved Python since
> the day I discovered it, five years ago IIRC.
> A few months ago I got greatly interested in recommendation systems
> applied to social news sites and finally decided to write one of such
> sites. That's how I found Django. And let me say it's awesome, almost
> everything from the database layer to the templates worked fine for
> me, even when I was doing unusual things like ordering the items at
> the application level, bypassing the QuerySets.
>
> Currently, I'm finishing my studies in Informatics (that's how we
> call CS here in Europe). If everything goes well, I'll finish them in
> September :).
>
> Well, now let's start with my proposal. I'm also developing a Django
> based blog and the biggest annoyance I found is they're no way to set
> app specific settings and exporting them to the template without
> writing a wrapper for render_to_response (or whatever you use for
> rendering your templates) or writing a custom context processor. Both
> approaches require to write some boilerplate code, which, having
> worked a lot with GLib/GObject, is something I really *hate*. On the
> other hand, I also think it annoys the user. Imagine I set up a blog
> for someone at one of my servers, but I don't want to give him shell
> access. How can he change the blog title or subtitle? Definitely, he
> can't do it unless I write some code which modifies settings.py and
> reloads it. Not a good solution in my opinion.
>
> So, I thought that writing a solution for this problem could be both
> useful for a lot of people and also make a good GSoC project. My idea
> is adding a new (optional) file to the Django apps, specifying some
> settings with the default values and if they should be exported to the
> template engine. These settings would be kept in the database,
> avoiding the requirement for writing to settings.py. However, since
> some of these values would be read for every request, caching them and
> invalidating the cache (or renewing it's value) when they change seems
> logical. In addition, since they won't be a lot of data, that cache
> could use a simple dict structure when no cache engine is present. The
> project would also include any needed modifications to the admin
> interface, so users can edit application settings from it.
>
> ¿What do you think about it?
>
> P.S. : Sorry if you get more than one copy of this message. I'm having
> problems with my mail server.
>
>
> Regards,
> Alberto
> >
>
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---
