On 1/4/07, Suriya <[EMAIL PROTECTED]> wrote:
Russell Keith-Magee wrote:
>
> Read the thread on the ticket - Jacob has stated what is standing
> between the ticket and acceptance - documentation of the feature.
>
> Write some documentation (or at least get an intitial draft ready),
> add it to t
Hi,
http://code.djangoproject.com/ticket/3250
This adds the RequiredIfOtherFieldsNotGiven validator documented at
http://www.djangoproject.com/documentation/forms/#validators but
missing from trunk.
It also adds two supporting validators:
RequiredIfAllOtherFieldsNotGiven and AllValidators, sem
On 1/7/07, jfroehlich <[EMAIL PROTECTED]> wrote:
Hi, not sure but i think there is a bug in a fields choices
with python 2.3
When i do something like http://dpaste.com/hold/4454/ i get an
UnicodeDecodeError when rendering the form to html. A friend of mine
tested it with python 2.4 without a pr
Hi, not sure but i think there is a bug in a fields choices
with python 2.3
When i do something like http://dpaste.com/hold/4454/ i get an
UnicodeDecodeError when rendering the form to html. A friend of mine
tested it with python 2.4 without a problem.
-johannes
--~--~-~--~~--
On 1/7/07, Philipp Keller <[EMAIL PROTECTED]> wrote:
One further question: db.models.fields.TextField.formfield() currently returns
a CharField
witout its widget set. I would have expected its widget set to
widgets.Textarea. Is this
by design?
No, that's not by design -- it just hasn't been
Ok, I'll post the patches.
One further question: db.models.fields.TextField.formfield() currently returns
a CharField witout its widget set. I would have expected its widget set to
widgets.Textarea. Is this by design?
greets
Philipp
On Sun, Jan 07, 2007 at 01:15:41PM -0600, Adrian Holovat
On 1/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I made two patches in newforms.models part of django (one is taking
field.editable in account, the other fixes the create-function so it
maps the data coming from the form to the corresponding db-columns)
The question now: is it of any use
Mikko Ohtamaa wrote:
Producing HTML is Python is the root of the problem. Most of HTML
widget libraries out there use template pieces to produce form output -
one template per widget. Have you had any though to move this kind of
solution? I already once hacked oldforms a bit to provide me
Templa
I am fairly new to python and also to django, so please forgive me any
missteps:
I made two patches in newforms.models part of django (one is taking
field.editable in account, the other fixes the create-function so it
maps the data coming from the form to the corresponding db-columns)
The quest
I was wondering whether I could just grab django/contrib/search, and
now I know. Thanks! I'll give that a shot. Given that workaround, I
wouldn't worry about a downmerge right now, I know how time-consuming
they are.
TK
--~--~-~--~~~---~--~~
You received this me
On 1/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi all,
the select-form-widget and the selectmultiple-form-widget display's a
choices-list as
...
...
From the per-row-level-permision branch there is an alternative issue to do
something like this:
...
...
I made
Honza Král wrote:
On 1/6/07, Mikko Ohtamaa <[EMAIL PROTECTED]> wrote:
well, the problem I see here is that you move the responsibility to
programmer, if designer wishes to change the output, he would have to
go to python...
Producing HTML is Python is the root of the problem. Most of HTML
Hi all,
the select-form-widget and the selectmultiple-form-widget display's a
choices-list as
...
...
From the per-row-level-permision branch there is an alternative issue to do
something like this:
...
...
I made 2 new widgets, selectgrouped and selectmultiplegrouped, which w
13 matches
Mail list logo
