Thank you Anthony. As always very informative. There is so much knowledge waiting for us about web2py internals if we start from scratch. Things that we take for granted and never questioned them. there should be a chapter about "Starting from scratch" in the book. It will help me and others.
Regards António 2015-11-15 15:47 GMT+00:00 Anthony <[email protected]>: > By the way, if you don't want to use the scaffolding app at all, to create > a new app, just make a new empty folder inside the /applications folder. > Once you make a single request to the app (which will initially yield an > error), web2py will automatically create all the necessary (empty) > sub-folders (i.e., controllers, models, etc.). You can then create your > entire app from scratch as you please, just like with other frameworks that > provide no scaffolding. > > Anthony > > > On Sunday, November 15, 2015 at 10:41:49 AM UTC-5, Anthony wrote: >> >> On Sunday, November 15, 2015 at 9:37:34 AM UTC-5, Ramos wrote: >>> >>> This is the login form where i see bootstrap all over the place. >>> >> >> I think there is some confusion. Just to be clear, Bootstrap is *not* >> the default formstyle used by web2py -- the default formstyle is the >> generic "table3cols" style. Bootstrap is used only in the web2py >> scaffolding app, which is completely optional. The reason you see Bootstrap >> form styles in the scaffolding app is because of this single line in db.py: >> >> response.formstyle = myconf.take('forms.formstyle') >> >> The forms.formstyle setting defined in the /private/appconfig.ini >> settings file is set to "bootstrap3_inline". If you edit appconfig.ini or >> remove the line above, you're back to the "table3cols" default. >> >> If i want to use semantic instead i not only have to change layout but >>> also have to look for all of the forms. and remove css classes. >>> >> >> As noted above, no need for this. Of course, you may need to define your >> own formstyle to work with Semantic-UI, but that will be true for any >> front-end framework with idiosyncratic forms markup requirements. >> >> >>> I think web2py is very above average in an overall review but this issue >>> cracks my head completely. why ? and why not completely agnostic ? >>> >> >> Hopefully it is now clear that the core framework *is *front-end >> agnostic and not tied to Bootstrap. The front-end scaffold is based on >> Bootstrap, but you can simply replace the layout.html and switch to >> whatever you want. >> >> in this aspect i think weppy is in a more clever path. >>> >> >> weppy (like most other frameworks) provides no front-end scaffolding app >> at all, so even if you simply remove web2py's front-end scaffold and start >> from scratch, you are no worse off than you would be with weppy (where you >> have to start from scratch whether or not you want to use Bootstrap). >> >> Anthony >> > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
