thanks for your answer, chris.
the piece of code i was porting was registration.
i wouldn't argue about consistency, but i just feel reasonable to propagate the
explicitly assigned "name" parameter, especially as it has been done before.
i will gladly join the tw-discuss board too.
thanks,
alex
percious wrote:
> This is not so much an inconsistency as a new way of doing things. TW
> is supposed to work like the old widgets, but consistency was
> abandoned for increased operability.
>
> Also, I did new releases for almost all of the old widgets, so you
> should not have too many issues with regards to moving to 0.8. The
> new namespace is much more sensicle, and is quite a big step forward
> for TW. Which older packages are you using? The only one I can think
> that has issues is twAjaxTools, whcih I will gladly re-release when I
> see a need. tw.jquery has an ajax form which is superior in
> operability to twAjaxTools.
>
> Finally, you may see better response if you post on the toscawidgets-
> discuss board rather than the TG board. The tg board is harder for me
> to track since there is a considerable amount more traffic here. I
> think Alberto (main owner of TW would agree)
>
> cheers.
> -chris
>
> PS.Thanks to Sanjiv for helping with the responses.
>
> On Apr 27, 3:27 am, alex bodnaru <[EMAIL PROTECTED]> wrote:
>> thanks for this point, too :) .
>>
>> i'd also like to report a small inconsistency with turbogears widgets:
>>
>> class ExistingUserFields(WidgetsList):
>>
>> password_1 = widgets.PasswordField('password1',
>> label=_("New Password"),
>> help_text=_("Your new password. (If you would like to
>> change it)."))
>>
>> the code above would end in a form with a field of name="password_1"
>> id="password_1", while in classic tg widgets the name would be "password1",
>> as
>> the name parameter to the field.
>>
>> best wishes,
>>
>> alex
>>
>> [EMAIL PROTECTED] wrote:
>>> Hi Alex,
>>>> just curious that most documentation is in tg2.
>>> The doc should apply for tg1 as well. The only change in tg2 is the
>>> new "recommended" style of passing the widget to the template by
>>> placing it on the template context, that is something like:
>>> @expose('mypackage.templates.myformtemplate')
>>> def entry(self, **kw):
>>> mywidget = MyWidget()
>>> pylons.c.w.mywidget = mywidget
>>> return dict(value=kw)
>>> In tg1 you would continue to pass the widget to the template by adding
>>> to the return dictionary similar to tg widgets. That is
>>> @expose('mypackage.templates.myformtemplate')
>>> def entry(self, **kw):
>>> mywidget = MyWidget()
>>> return dict(mywidget=mywidget, value=kw)
>>> Regards,
>>> Sanjiv
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
