I'd also suggest, if you're considering those other frameworks (and are someewhat familiar with them) you might find it instructive to see the recent video which works thru a django tutorial, implementing it in web2py. You might even use this to compare the same solution at some basic level with those two.
Coding Django "polls" tutorial in web2py http://www.vimeo.com/6507384 On Mon, Sep 14, 2009 at 1:54 AM, Yarko Tymciurak <yark...@gmail.com> wrote: > On Mon, Sep 14, 2009 at 12:18 AM, mdipierro <mdipie...@cs.depaul.edu>wrote: > >> >> Thanks for your questions. Please find some answers below. I am sure >> other users will have something to add. >> >> On Sep 13, 8:02 pm, mengu <whalb...@gmail.com> wrote: >> > hello everyone, >> >> ..... > > >> > 4) what are the main things that web2py needs to be better? >> >> > Currently, web2py will connect to multiple databases (including ones under > django); last I heard, django did not yet work for multiple connections, > but will soon (or maybe already). > > I think a couple of things in core web2py that will improve the framework: > > [] alternate naming of automatic index ('id') field will ease accessing > legacy databases (I think I have a solution that should work for this, but > will wait for new DAL), > [] Currently, prototyping is easiest with some data persistent shape (even > if transitory), and this is fine, but I think some UI / client based > prototyping and layout focus would be helpful. Two things are in the works > that could positively affect this (that I know of) - T4, and (I believe) a > new jpolite version. > [] potentially, some helpers for custom forms setup; > > > >> >> > 5) how to set routes.py for an url like "/blog/post/view/5" or "/blog/ >> > post/blog-post-title/"? >> >> > web2py does this as a reasonable default: URL( a=application, > c=controller, f=function, args=[arg] ) (there's more, but I'll leave it at > this for now), which translates into: > > /application/controller/function/arg > > So, for your use, let's say you have an application, "blog" - then you > would create a controller file, post.py where you would have a couple of > functions: view() which would read request.args[0] to get the '5' (in the > first instance), and post(), which would read request.args[0] to get > 'blog-post-title (and then likely do a db select to fetch the matching > article, or present multiple matches for selection). > > Of course, you could have either of these be a pointer to one conglomerate > function, or have either use logic to redirect to another handler (e.g. > date-based selection, item-based selection, title-based, general search, > etc. etc.) > > That would be the "web2py" way to handle your example. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@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 -~----------~----~----~----~------~----~------~--~---
