On 3/28/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
> If possible I would like to see dojo *not* included in django's SVN repo.
> just a pointer to where DOJO is installed on your docroot should be
> sufficent for most things, and remove the need to figure out what
> things should/shoiuldn't be i
On 3/28/06, Eugene Lazutkin <[EMAIL PROTECTED]> wrote:
> From the top of my head we need dojo.io, but I assume it is included
> indirectly by other packages.
Ack. Yeah, I just forgot that one when I compiled my list.
--
"May the forces of evil become confused on the way to your house."
-- Geor
On 3/28/06, Neboj¹a Ðorðeviæ <[EMAIL PROTECTED]> wrote:
> Currently implemented validate() methods (in EmailField, IPAddressField and
> PhoneNumberField) just call
> validators.isValidFOO(field_data, all_data) and, for example, validate method
> for PositiveIntegerField will look
> something like
Andy Dustman wrote:
> It might be worth considering puting in some backwards-compatibility
> with 0.91, though, keeping a meta module but giving a deprecation
> warning if it's used, warning if your model has a META class, etc. I'm
> thinking meta can be a light wrapper around model in a lot of ca
On 3/28/06, pbx <[EMAIL PROTECTED]> wrote:
>
> At this point I'm just pretending magic-removal *is* the trunk. I've
> ported all my play stuff to it, am using the admin to manage content
> for a couple existing non-Django sites, and am developing a production
> site in it at work now as well. Most
At this point I'm just pretending magic-removal *is* the trunk. I've
ported all my play stuff to it, am using the admin to manage content
for a couple existing non-Django sites, and am developing a production
site in it at work now as well. Most of the time the limiting factor in
functionality is
On 3/28/06, limodou <[EMAIL PROTECTED]> wrote:
>
> On 3/28/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> >
> > On 3/28/06, Gábor Farkas <[EMAIL PROTECTED]> wrote:
> > > i assume the answer to my second question is: Nothing.
> > >
> > > am i correct?
> >
> > The best thing everybody can do to he
I can also attest to the 'MR' branch.
I've been using it for zyons.com and except for a weird redirect not
working when you create a forum.. it's pretty dang sweet.
On 3/29/06, limodou <[EMAIL PROTECTED]> wrote:
>
> On 3/28/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> >
> > On 3/28/06, Gábor
On 3/28/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 3/28/06, Gábor Farkas <[EMAIL PROTECTED]> wrote:
> > i assume the answer to my second question is: Nothing.
> >
> > am i correct?
>
> The best thing everybody can do to help is start using the
> magic-removal branch and reporting any an
If possible I would like to see dojo *not* included in django's SVN repo.
just a pointer to where DOJO is installed on your docroot should be
sufficent for most things, and remove the need to figure out what
things should/shoiuldn't be included.
(ps.. I use AOL's base at
http://o.aolcdn.com/iam
James Bennett wrote:
>
> dojo.dom
> dojo.event
> dojo.html
> dojo.lang
> dojo.widget
> dojo.xml
>
> What else needs to be included?
From the top of my head we need dojo.io, but I assume it is included
indirectly by other packages.
Thanks,
Eugene
--~--~-~--~~~--
Quick update: I now have a magic-removal install with all of the admin
JS ported to Dojo packages. There are some crufty bits that still need
to be cleaned up, but it works!
Next step: I need to know what sort of Dojo functionality people are
going to rely on, because we're going to have to do a
Nope, I just didn't notice you had added that. Looks great.
--~--~-~--~~~---~--~~
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 unsub
Michael Radziej wrote:
> Nebojša Đorđević schrieb:
>> And for ordering, I can't find any logic in model order, it's not
>> alphabetical as I presumed before.
>
> Hmhm ... then don't let me take you on the wrong track for debugging:
> I'm only sure that they were _not_ ordered alphabetically. I
Adrian Holovaty wrote:
> Yeah, it doesn't get called on save() yet. It's not really intended
> for general use, because only a few of the Field classes have the
> validation method implemented. Help coding this up would be *much*
> appreciated!
I'll will try to help if I can.
Currently implemen
Adrian Holovaty wrote:
> The best thing everybody can do to help is start using the
> magic-removal branch and reporting any and all problems. It's getting
> to a point where it's not too horrible. :)
I just started with MR (again) and I like it!!! Some polishing is needed
alright, but for now
On 3/28/06, binaryfeed <[EMAIL PROTECTED]> wrote:
> These kinds of answers only serve to alienate people. Non-committal
> order-of-magnitude estimates can be very helpful, but apparently you
> disagree.
>
> That's your perogative, I suppose. It *is* your project. But it sure
> would be more fri
These kinds of answers only serve to alienate people. Non-committal
order-of-magnitude estimates can be very helpful, but apparently you
disagree.
That's your perogative, I suppose. It *is* your project. But it sure
would be more friendly to say something like, "I can't promise
everything, but
These kinds of answers only serve to alienate people. Non-committal
order-of-magnitude estimates can be very helpful, but apparently you
disagree.
That's your perogative, I suppose. It *is* your project. But it sure
would be more friendly to say something like, "I can't promise
everything, but
Am 28.03.2006 um 17:39 schrieb Adrian Holovaty:
>
> On 3/28/06, Gábor Farkas <[EMAIL PROTECTED]> wrote:
>> i assume the answer to my second question is: Nothing.
>>
>> am i correct?
>
> The best thing everybody can do to help is start using the
> magic-removal branch and reporting any and all pr
On 3/28/06, Neboj¹a Ðorðeviæ <[EMAIL PROTECTED]> wrote:
> I just tried to use new model validate() method (R2571) but
>
> It's don't get called when I save or change object. I looked a little in
> Model class and I
> can't find any invocation of
> the validate() method. Is it available for gen
On 3/28/06, Gábor Farkas <[EMAIL PROTECTED]> wrote:
> i assume the answer to my second question is: Nothing.
>
> am i correct?
The best thing everybody can do to help is start using the
magic-removal branch and reporting any and all problems. It's getting
to a point where it's not too horrible. :
I just tried to use new model validate() method (R2571) but
It's don't get called when I save or change object. I looked a little in Model
class and I can't find any invocation of
the validate() method. Is it available for general use or I must wait a little
bit more ;) ?
Also, I presume (
--~--~-~--~~~---~--~~
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 PRO
Nebojša Đorđević schrieb:
> And for ordering, I can't find any logic in model order, it's not
> alphabetical as I presumed before.
Hmhm ... then don't let me take you on the wrong track for debugging:
I'm only sure that they were _not_ ordered alphabetically. I don't
recall if they were in cre
Michael Radziej wrote:
> Nebojša Đorđević schrieb:
>> I probably missed this, but in m-r branch admin interface all models are
>> sorted alphabetically and not in creation order
>> like in current trunk. Is this intentional or feature ;)?
>>
>> Also (with sqlite) I noticed that order of CREATE SQ
Nebojša Đorđević schrieb:
> I probably missed this, but in m-r branch admin interface all models are
> sorted alphabetically and not in creation order
> like in current trunk. Is this intentional or feature ;)?
>
> Also (with sqlite) I noticed that order of CREATE SQL statements are also
> sort
I probably missed this, but in m-r branch admin interface all models are sorted
alphabetically and not in creation order
like in current trunk. Is this intentional or feature ;)?
Also (with sqlite) I noticed that order of CREATE SQL statements are also
sorted alphabetically which (for example)
28 matches
Mail list logo
