On Apr 10, 6:51 pm, Ian Holsman <[EMAIL PROTECTED]> wrote:
> The zyons version allows for:
> - constants at the site level (ie max blog comments can be different
> on different sites)
True, site-awareness would be a definite benefit that I hadn't yet
included.
> - allows users (registered and an
On Apr 10, 6:28 pm, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> How would a FileField or an ImageField work? How would the proposed
> CreatedTimestamp/ModifiedTimestamp fields work?
> ForeignKey? yikes.
Very true. I hadn't considered the many fields that wouldn't even make
sense themselves i
I have something similar to this in the Zyon's codebase. but I called
it 'preferences' (see http://zyons.com/preferences/ )
The zyons version allows for:
- constants at the site level (ie max blog comments can be different
on different sites)
- allows users (registered and anonymous) to set t
I am not a fan of reusing the existing model fields classes for all
the reasons you specified.
How would a FileField or an ImageField work? How would the proposed
CreatedTimestamp/ModifiedTimestamp fields work?
ForeignKey? yikes.
The added confusion for users and developers who are extending or
c
In working a bit with this, I noticed something. Once these constant
definitions are moved outside the main field namespace, there's no
longer a clash of functionality between standard fields and these
constant values. That clash was the primary reason I had to recreate
the basic functionality of
On Apr 9, 9:02 am, "Gulopine" <[EMAIL PROTECTED]> wrote:
> > So, my first question is whether this could be designed to work
> > without respect to models. For example, there are a lot of cases where
> > views might refer to the same data, but not the same models. It would
> > seem cleaner if ther
On Apr 8, 11:18 pm, "oggie rob" <[EMAIL PROTECTED]> wrote:
> So, my first question is whether this could be designed to work
> without respect to models. For example, there are a lot of cases where
> views might refer to the same data, but not the same models. It would
> seem cleaner if there were
On 4/9/07, Marc Fargas Esteve <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On 4/8/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> > * The name "values" is a bit too abstract -- it took me a while to
> > figure out exactly what this framework *does*. Maybe something like
> > "editable constants" or "model-
Hi,
On 4/8/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> * The name "values" is a bit too abstract -- it took me a while to
> figure out exactly what this framework *does*. Maybe something like
> "editable constants" or "model-specific options" would be more clear.
Isn't a constant supposed
On 4/8/07, Max Battcher <[EMAIL PROTECTED]> wrote:
> It's a magic numbers (avoidance) framework. I know this is going to
> sound like a joke, but what about calling it
> django.contrib.magic_numbers?
But we've *removed* the magic!
:)
I like the idea of thinking out of the box, though, along th
> I'm glad you like it! I really hope it does help many other people who
> have a need for something like this. I'm very eager to hear what other
> thoughts and questions you (and anyone else!) have about it. I'm glad
> to clarify.
>
> -Gul
Good timing! I was planning to look to something like th
On 4/8/07, Gulopine <[EMAIL PROTECTED]> wrote:
>
> > * The name "values" is a bit too abstract -- it took me a while to
> > figure out exactly what this framework *does*. Maybe something like
> > "editable constants" or "model-specific options" would be more clear.
>
> I will admit that I never re
> * The name "values" is a bit too abstract -- it took me a while to
> figure out exactly what this framework *does*. Maybe something like
> "editable constants" or "model-specific options" would be more clear.
I will admit that I never really had a clear idea on what to call it.
I knew going in
On 4/7/07, Gulopine <[EMAIL PROTECTED]> wrote:
> http://code.google.com/p/django-values/
>
> It is essentially an entire subframework, but it exists entirely as a
> contrib app, utilizing newforms and standard Django permissions for
> its value editor, and supplying class attributes for direct use
Hey all,
Many projects require a certain amount of calculations and other
features that are based on organizational (or other) policies, rather
than any technical requirements imposed by Python or Django. As those
policies may change and evolve over time, programmers are often
required to change
15 matches
Mail list logo
