I occurred to me last night right before sleep that I can patch this
in my code by deriving all my forms from my MyForm, fixing it in one
place and remaining DRY.
Nice to see I'm not the only one that found this to be a bit strange.
--~--~-~--~~~---~--~~
You
On Tue, Feb 24, 2009 at 8:08 AM, bruno desthuilliers <
bruno.desthuilli...@gmail.com> wrote:
>
>
>
> On 24 fév, 05:46, Mark Jones wrote:
> > That is exactly the kind of WET I was talking about. as_p() with
> > appropriate CSS styling will render really nice forms as is, with
On 24 fév, 05:46, Mark Jones wrote:
> That is exactly the kind of WET I was talking about. as_p() with
> appropriate CSS styling will render really nice forms as is, with the
> exception of the help_text. I even think that could be fixed without
> any major rework, just a
That is exactly the kind of WET I was talking about. as_p() with
appropriate CSS styling will render really nice forms as is, with the
exception of the help_text. I even think that could be fixed without
any major rework, just a change in the as_p() string
from
def as_p(self):
On Mon, Feb 23, 2009 at 4:10 PM, Mark Jones wrote:
>
> When a model field has help_text, that text will be show in the form.
> I'm a little bothered by this because effectively the model is doing
> something that really belongs in the view, but I understand the point
> is to
When a model field has help_text, that text will be show in the form.
I'm a little bothered by this because effectively the model is doing
something that really belongs in the view, but I understand the point
is to make it easy to create forms based on a model and I can just
live with it.
What
6 matches
Mail list logo