You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
z3cform has a complex set of widgets to handle dicts, lists, lists of objects etc. Rapido currently has only text, int and datetime. If you want more complex widgets you would have to do them manually using html which can would take more time. Being able to quickly use complex widgets could save a lot of time.
Allow rapido to render a form defined in a DX type and then handle the result. Perhaps a ttw DX type that is never meant to be added anywhere.
c.easyform
Allow rapido to render a form defined in c.easyform and then handle the result.
c.easyform submit to rapido
Change easyform to allow submission into an rapido block
zope schema widgets only
In a rapido yaml definition allow defining a element which is a zope schema field. Elements still need to be placed into an html layout. Maybe don't support validations and field labels etc to make it work more like a basic element. Support hints to pick a widget. Widgets processing of inputs might have to be called manually in rapido action code.
z3cforms
same as above but you don't have to define a layout works much more like a normal z3cform with labels, layout and validations all coming from z3cform. A blocks code would have have different semantics so functions could be used for validation, default values, and the actions take a final dict.
??
The text was updated successfully, but these errors were encountered:
User problem
z3cform has a complex set of widgets to handle dicts, lists, lists of objects etc. Rapido currently has only text, int and datetime. If you want more complex widgets you would have to do them manually using html which can would take more time. Being able to quickly use complex widgets could save a lot of time.
(from #9)
Options
Render DX schemas
Allow rapido to render a form defined in a DX type and then handle the result. Perhaps a ttw DX type that is never meant to be added anywhere.
c.easyform
Allow rapido to render a form defined in c.easyform and then handle the result.
c.easyform submit to rapido
Change easyform to allow submission into an rapido block
zope schema widgets only
In a rapido yaml definition allow defining a element which is a zope schema field. Elements still need to be placed into an html layout. Maybe don't support validations and field labels etc to make it work more like a basic element. Support hints to pick a widget. Widgets processing of inputs might have to be called manually in rapido action code.
z3cforms
same as above but you don't have to define a layout works much more like a normal z3cform with labels, layout and validations all coming from z3cform. A blocks code would have have different semantics so functions could be used for validation, default values, and the actions take a final dict.
??
The text was updated successfully, but these errors were encountered: