للحصول على وزن مثالي في يوم واحد ادخل هنا
http://www.antya7la.com/vb/t26066.html
خبر مؤسف ومؤلم اتمنى الدخووول
http://www.antya7la.com/vb/t26168.html
اختاري لون الصبغ اللي اناسبح ( السايت عجيب) للنساء فقط
http://www.antya7la.com/vb/t26211.html
السلسلة الوثائقية الشيقة Walking with Dinosaurs كا
I am in the middle of porting some code to the newforms admin branch.
One of the fields in my models was as follows:
sites = models.ManyToManyField(Site)
...where 'Site' is django.contrib.sites.models.Site
Before switching to the newforms admin branch, if I created a new
entry in admin, by defa
I know this has been touched on a couple times, but I have an itch for
database schema support I'd like to scratch. The relevant ticket it
#6148 [1]. I was thinking the Options class would grow a db_schema
field, which would default to settings.DEFAULT_DATABASE_SCHEMA. Then
everywhere that current
See ticket #6095 in trac. The fix is on its way.
Cheers,
Cliff
On Mon, 2008-05-19 at 06:53 -0700, JReynolds wrote:
> I posted this on django-users before and didn't get much response, so
> asking here...
>
> I have seen this posted a few times on the list here, but it always
> seems to become
Hello,
I'm quite new to django (first real project) and stumbled across several
bugs/features that I'd like to see in trunk. And I'm willing and
hopefully able
to help. Here they are: #2539, #3544, #6915, #7154, #7215, #7312, and
(cosmetic)
#5537.
The following should probably be split into
> Also, when the number of choices is big, none of the provided widgets
> are very usable, so I have for instance created a TreeSelect widget
> which groups choices into categories (columns in the table) and
> displays them in a tree whose branches are collapsible (see an example
> at [1]). But i
On 28 May 2008, at 3:12 pm, phillc wrote:
> i would use it as well.
> i was actually thinking how on earth could i simplify the same thing i
> do for every single project
> (splitting settings.py to allow for revision control, splitting
> urls.py, etc.)
Ok, thanks everyone for your feedback, I
Thanks Ben,
That looks like it'll do it, I'll give it a whirl.
Chris
On May 29, 3:34 pm, "Ben Ford" <[EMAIL PROTECTED]> wrote:
> Hi Chris,
>
> You could copy the whole model, ala DynamicModels on the wiki
> [http://code.djangoproject.com/wiki/DynamicModels], I've sketched out a more
> complete
Hi,
I would like to suggest a modest change in some newforms objects,
namely ModelChoiceField and MultipleModelChoiceField, and how they
interact with their widgets. Before I describe the change, let me
explain an example in which I think this is desirable.
There is also the possibility that I
Hi Chris,
You could copy the whole model, ala DynamicModels on the wiki [
http://code.djangoproject.com/wiki/DynamicModels], I've sketched out a more
complete example here: http://www.djangosnippets.org/snippets/442/. This
example (I say example as it's a bit rough around the edges - especially th
10 matches
Mail list logo