WikiForm [{FormOpen}] add your own wiki text in here [{FormInput name="test"}] [{Form element='submit' name='x' value='Update'}] [{FormClose}]
web2py custom form (assuming a form object passed from the action): {{=form.custom.begin}} add your own html text in here {{=form.custom.widget.test}} {{=form.custom.submit}} {{=form.custom.end}} To me they look the same with the exception that web2py needs the preexisting "form" object to handle the form processing. WikiForms do not deal with processing. On Jun 28, 11:51 pm, Yarko Tymciurak <yark...@gmail.com> wrote: > hmmmm.... > > I do not see it; certainly not from slide 72 - in fact, I'm not sure what > this slide tells me. > Perhaps there are things on this slide that are obvious to some, but not to > others (?) > > On Sun, Jun 28, 2009 at 10:38 PM, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > Page 72 of the slides in web2py.com. It maps one to one. > > > Massimo > > > On Jun 28, 10:21 pm, Yarko Tymciurak <yark...@gmail.com> wrote: > > > That would be one thing.... > > > > I saw this today, a form defined in "wikiform" - > >http://sandbox.jspwiki.org/Wiki.jsp?page=BugReportSystem > > > > For this to be interesting, you should "edit" this sandbox page which > > holds > > > the description of the form. > > > > The fields are described here: > >http://sandbox.jspwiki.org/Wiki.jsp?page=WikiForms > > > > Now - It seems to me that something similarly simple in our web2py > > template > > > language, some standard could be useful to setup easy layout of custom > > > forms. The basic ideas are in the links I show. Users from this group > > can > > > talk through specifying what things to setup, and we can define a simple > > > interface for custom forms. > > > > This might be just enough, and just the sort of thing people have been > > > asking for. We would probably want to consider plain-html interface, > > json > > > interface, and perhaps amf interface. If the idioms were the same, I > > think > > > this would be nice. > > > > What do others think? > > > > - Yarko > > > > On Sun, Jun 28, 2009 at 10:00 PM, mdipierro <mdipie...@cs.depaul.edu> > > wrote: > > > > > I guess one think that is not documented is the css naming convention > > > > follwed by web2py > > > > > for a table "table" and a field "field" of type "type" the <input /> > > > > tag must have: > > > > > name="field" -> required for form submission and processing > > > > id="table_field" -> required for css > > > > class="type" -> required for js+jquery client side validation (for > > > > example you cannot type a-z in an "integer" field, "date" gets popup > > > > calendar, etc.) > > > > > This is done automatically by {{=form.custom.widget["field"]}}. > > > > > Massimo > > > > > On Jun 28, 9:03 pm, Yarko Tymciurak <yark...@gmail.com> wrote: > > > > > I think there are several things mixed in here, and it would be good > > to > > > > > separate them, talk about them one at a time: > > > > > > --> Photoshop design: This presumably talks about layout of html > > or > > > > flash > > > > > user interface; > > > > > > what is needed here? > > > > > Perhaps: > > > > > -- standard naming of css fields (for html layouts) > > > > > -- ?? someone applying a photoshop layout to some (perhaps?) > > grid > > > > > system, making a defacto std > > > > > -- photoshop design to other layouts: (or perhaps other than > > > > > photoshop: e.g. illustrator / vectore based): svg layout elements; > > > > flash > > > > > (that is an entirely different thing) > > > > > > I think the graphical design is independent of > > > > > > --> layout design: HTML / CSS is not the only user interface > > method > > > > (it > > > > > is old, standard, and roughly static; you can add javascript, java, > > or > > > > svg > > > > > actions within); you can also do all or parts of your layout in a > > flash > > > > vm. > > > > > > there is layout for the designer & application writer; > > > > > > there is the question (and great need) for layout modificaitons > > for > > > > the > > > > > content manager of an application / cms; e.g. something like > > jpolite; > > > > > > --> custom forms design: > > > > > > the web2py backend does many "template" (standard) things for > > you, > > > > > making thinking about forms unnecessary to get many things working. > > > > What > > > > > is needed is a clean behavioral & interface model for those > > templates, so > > > > > that people can design their own - e.g. "custom forms". > > > > > > that's the backend interface; it generates html forms; for > > > > custom, > > > > > there is a need for interaction w/ json (?), svg, flash (amf); > > > > > > It would be nice to have examples of doing each of these things - > > most of > > > > > them will never be "done" by the framework, but custom per > > application - > > > > > still, examples would be nice - soon as people have examples. > > > > > > Am I missing / misstating anything? > > > > > > Regards, > > > > > Yarko > > > > > > On Sun, Jun 28, 2009 at 6:53 PM, Pystar <aitoehi...@gmail.com> > > wrote: > > > > > > > I think that is what i need. A tutorial about how to create custom > > > > > > forms using web2py. I really need it badly and i guess some other > > > > > > people do too. > > > > > > Thanks > > > > > > Pystar > > > > > > > On Jun 29, 12:14 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > > > > > Perhaps we should make some video on how to create custom forms. > > I am > > > > > > > not the right person to do this since i do not even have > > dreamweaver. > > > > > > > > On Jun 28, 5:58 pm, weheh <richard_gor...@verizon.net> wrote: > > > > > > > > > I don't see the author's point. I'm able to easily do things > > that > > > > are > > > > > > > > visually pleasing, are information dense, yet easy to > > understand. > > > > > > > > Things that would have taken me a lot longer to hack together > > > > without > > > > > > > > web2py. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---