ToscaWidgets2 is designed to be able to work also by itself in a pure WSGI environment, without a web framework, so it also has the concept of web Page (the FormPage), but as you already have a framework providing template and controller you usually don't want to use them.
Generally speaking you avoid using Page subclasses when using TW2 inside a framework, being it TG or something else. Otherwise you end up doing the same work twice. On Thu, Dec 19, 2013 at 5:39 PM, enrico secco <[email protected]>wrote: > Thank you Alessandro! > Now it run. > There was 3 problems. > 1) the buttons was in the array. > 2) the buttons not have the 'key' attribute > 3) the TableForm was 'child' af a FormPage > > After I did defined the buttons like direct elements of the Form and with > the 'key' attribute I recived a value for the 'action' parameter but it was > always empty. > Then I did observed that you do'nt use the FormPage and I did the same. > Now it work. > > allow_extra_fields was just a try ... > > Just a little note: could be there are to many styles used in the examples > of Toscawidgets2. > Allmost all the examples use the TableForm inside a PageForm and I did the > same without understand why. > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/turbogears. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears. For more options, visit https://groups.google.com/groups/opt_out.
