TED]> wrote:
> Hi all,
>
> I'm a complete Django noob, but I've reached the same conclusions,
> namely:
> 1. Django is really wonderful!
> 2. I need an ordered ManyToMany relationship :-)
>
> (long story short: my project involves photos and galleries; the
> photos
Hi all,
I'm a complete Django noob, but I've reached the same conclusions,
namely:
1. Django is really wonderful!
2. I need an ordered ManyToMany relationship :-)
(long story short: my project involves photos and galleries; the
photos can belong to multiple galleries with a potentially
Thanks for your answer all!
I really appreciate it!
In the meantime, I have thought of the following ugly but simple
solution. A comma (or whatever character) seperated list of primary
keys in a CharField can hold the values in the order needed. Now the
only thing I need is a widget that
> I think Django is really wonderful, but I am puzzled that it contains
> so few "ordering features". We often have the case that a user wants
> to select from a list of possible choices (normal select) *plus* wants
> to specify an ordering. Typically in applications this is done using
> up/down
On Thu, Jun 26, 2008 at 7:36 PM, Tom Tobin <[EMAIL PROTECTED]> wrote:
> The various Javascript toolkits vary wildly in their implementations;
> any API attempting to unify them would necessarily become a
> toolkit-onto-itself, which is *way* out of Django's scope.
Totally agreed.
> Many of us
>
On Thu, Jun 26, 2008 at 9:05 AM, Mike Scott <[EMAIL PROTECTED]> wrote:
> I understand there are some complexities involved, but essentially its
> just creating a uniform javascript API to use - not unlike the may we
> have a uniform database api.
That's a gross understatement. :-)
The various
Could this not be further discussed?
I understand the need to be toolkit agnostic, but could we not take a
similar approach as the Ext js framework, where by you can use one of
many existing frameworks as your base. Then the django community can
build connectors as demanded.
I understand there
On Thu, Jun 26, 2008 at 3:41 PM, OliverMarchand
<[EMAIL PROTECTED]> wrote:
> === Form Field/Widget ===
>
> The normal ChoiceField has no ordering. I am no Javascript expert, but
> I think it is very simple to write a widget where the selected choices
> can also be ordered. Assuming that the
Dear Django Developers,
I think Django is really wonderful, but I am puzzled that it contains
so few "ordering features". We often have the case that a user wants
to select from a list of possible choices (normal select) *plus* wants
to specify an ordering. Typically in applications this is done