Hi Dave You should obtain experience with individual controllers and views. The book is well ordered to take you through the learning curve. Try to get to the point where you feel confident about what's going on before moving down the list.
The Crud is ideal for fast prototyping and quick apps for internal use. These days I often start with Crud to quickly get things working and then write full controllers and views later. The Plugin_wiki and Restful stuff are still beta at this point. However, it is great to experiment with them and over the next few weeks I am sure these will become increasingly stable so you can start to consider the possibility of including them in your project even now. As with many things, it is often best to learn things the long way around before taking too many shortcuts. We are, after all, already taking a massive shortcut by using web2py itself :) Best wishes, David On Mar 17, 3:11 pm, Dave Warnock <dwarn...@gmail.com> wrote: > Hi, > > I am new to web2py and am developing a GPL application which I plan to > deploy in Google App Engine. > > From my reading there appear to be at least 4 ways of building the web pages > to maintain the application data: > > - writing individual controllers and views > - using the CRUD tools > - using the Wiki plugin > - using the new Restful stuff > > I think these are listed oldest first. > > What I lack is an understanding of what is considered the current best way > to use web2py (especially with a focus on GAE for deployment). > > If you were starting a clean empty project which style of web2py would you > choose and why? > > Thanks > > Dave > > -- > Dave Warnock:http://42.blogs.warnock.me.uk
