Be careful that you can no longer change attributes everywhere you like as in:
db.tablename.fieldname.readable = False In web2py this is ok. In web3py this is not safe. Attributes must be global. The state of fixtures must not be modified inside actions. On Thursday, 13 June 2019 17:57:49 UTC-7, 黄祥 wrote: > > tryin to move define_tables from web2py to web3py, run well just a few > note about field constuctor, (related with ui, FORM and T) : > - comment : run well, but if you not use bootstrap, then it's should be > modified (e.g. _class or function modal in boostrap) > - represent : run well, but if you not use bootstrap, then it's should be > modified (e.g. _class) > - widget : not sure how to use it using FORM(), since the book only > written using SQLFOrm(), perhaps some guidance > - labels : run well, but if using T(), the result is not expected when > editing in _dashboard (database), detail in previous msg > > just tests the models part, not yet using any controllers > > best regards, > stifan > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/f43f434a-0d75-469e-81c5-6b2de10276bb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
