Adrian Holovaty wrote:
> On 1/10/07, Mikko Ohtamaa <[EMAIL PROTECTED]> wrote:
> > I have toyed around with newforms a bit.
> >
> > We should subclass Widget to TemplateWidget and then rebuild all widget
> > class hierarchy usingTemplateWidget based widgets. I'd rather throw
> > away the current wi
Adrian Holovaty wrote:
> On 1/10/07, Mikko Ohtamaa <[EMAIL PROTECTED]> wrote:
>
> I see a huge drawback in offloading widget rendering to the template
> system -- it couples the forms library to the template system. Ideally
> the newforms library, when solidified, would be distributed as a
> stan
Adrian Holovaty wrote:
> Have you guys checked out the Widget class / capability in newforms?
> That's the part that lets you define how a field should be output as
> HTML. I'm definitely interested in hearing whether/how that doesn't
> let you do what you want to do.
Yes it worked out well.
Bu
On 1/10/07, Mikko Ohtamaa <[EMAIL PROTECTED]> wrote:
> I have toyed around with newforms a bit.
>
> We should subclass Widget to TemplateWidget and then rebuild all widget
> class hierarchy usingTemplateWidget based widgets. I'd rather throw
> away the current widgets outputting HTML in Python cod
Mikko Ohtamaa wrote:
>
> I don't see any drawback for template based widgets expect that running
> template engine consumes more CPU cycles. But if that's a problem for
> someone, I am willing to buy him/her a new server :)
Well, that's a handy coincidence, because it's suddenly become a
problem
>
> Have you guys checked out the Widget class / capability in newforms?
> That's the part that lets you define how a field should be output as
> HTML. I'm definitely interested in hearing whether/how that doesn't
> let you do what you want to do.
I have toyed around with newforms a bit.
We sho
On 1/8/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
> I just wanted to say that this is the reason I'm reluctant to use
> Django's forms (new or old) no matter how stable it is. I like that
> any major chunk of HTML code is visible for tinkering in my template
> files. Maybe a template solution w
I just wanted to say that this is the reason I'm reluctant to use
Django's forms (new or old) no matter how stable it is. I like that
any major chunk of HTML code is visible for tinkering in my template
files. Maybe a template solution would be more work (probably some
repetition, I haven't re
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
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
On 1/6/07, Mikko Ohtamaa <[EMAIL PROTECTED]> wrote:
Hi fellow snaky coders,
I just started a new web project. After a short evaluation of
Turbogears, Ruby on Rails and Django, I decided to use Django for the
project - again. Though Turbogears has good AJAX & etc. stuff, the lack
of middleware c
11 matches
Mail list logo
