well, suppose you've a form for registeration that's related to auth_user table Now you can register new users and no problem
suppose after a while you need a page where manager can add special users to them , [firs_name, last_name , ......] but in the registration form you need a new field to be added , let's say the new field is a combo box that selects some thing from another table . This 's ok if I'm going to use SQLFORM.factory what if .... I already have the Form that adds this special user that satisfied me in the past , now I need to change it to suit my needs so this needs to refactor my code using SQLFORM.factory as you can see refactoring my code can be painful, and I'm always refactoring my code Now I can take a decision to simply use just SQLFORM.factory from the beginning if my software changes frequently and this's not easy as using SQLFORM my other decision is to add the table manually to the form (form.insert.....) but this has a problem that this field can not be validated upon accepting the form Now we need SQLFORM to be more customizable, meaning that I can add to it a field from another table, another field that doesn't belong to any table and that can be validated upon accepting the form - may be we need a new SMARTFORM - as you've suggested - -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@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.
