One more thing to keep in mind. With an MVC framework like web2py, it is important to understand that URL's do not refer directly to individual HTML pages in directories on the server (as they might with a static site). Rather, a URL is a route to a function in a controller, and that function generates and returns the response (typically a web page) to the browser. Hopefully the MVC, Workflow, and Dispatching sections linked below will make this process more clear. Once you understand this foundation, it should be easier to figure out how to go about things.
Anthony On Sunday, June 16, 2013 9:05:45 AM UTC-4, Anthony wrote: > > If you're completely new to web programming (particularly with an MVC > framework), I would strongly suggest going through at least the > Introduction <http://web2py.com/books/default/chapter/29/01> (particularly > the > MVC<http://web2py.com/books/default/chapter/29/01#Model-View-Controller>section) > and > Overview <http://web2py.com/books/default/chapter/29/03> chapters of the > book. You might also find it helpful to review the sections on > Workflow<http://web2py.com/books/default/chapter/29/04#Workflow>and > Dispatching <http://web2py.com/books/default/chapter/29/04#Dispatching>in the > chapter on The Core. Other tutorials to consider are Killer > Web Development <http://killer-web-development.com/> and these > videos<http://www.youtube.com/playlist?list=PL5E2E223FE3777851> > . > > It sounds like you're starting with HTML pages and then trying to work > backwards to incorporate web2py. In general, it is probably more common to > take the opposite approach -- start by developing the controllers (and > models if needed), using either the generic views or very simple views at > first, and then build out the full views. > > In web2py, you would also typically have a master layout view for all of > the common page elements, so if you have existing HTML pages, you would > first extract out the layout from them. You can learn more about this in > the Page > Layout<http://web2py.com/books/default/chapter/29/05#Page-layout>section of > the book. Especially since you are new to this, you might > consider starting with the scaffolding application, which already includes > a layout and a few views. Start by customizing that application to get a > feel for how things work. Then you can replace the layout with your own. > > Anthony > > On Sunday, June 16, 2013 8:35:49 AM UTC-4, Alessandro Piroddi wrote: >> >> Hi :) >> I guess this kind of post comes up a lot, but I tryed searching the group >> and I still have problems... so I'm trying to ask a direct question. >> I hope you won't mind ^__^ >> >> I am no programmer. >> I know a bit my way around HTML and CSS, had (long time ago) an idea on >> how to use Javascript. >> I'm starting to chew a liiitle bit of Python (using the Codeacademy.com >> free course) and just graduated from the 10Gen MongoDB free course. >> But my skills are still veeeeery low and I'm struggling with basically >> everything I try to do :P >> >> So I bumped into web2py and decided I wanted to build a website with it >> (and maybe link it to a MongoDB, but I'll see to it later). >> And, well, I'm hitting a wall ç_ç >> >> I thought I would use html and css AND some python here and there to >> "link" the pages I make to the underlying dynamic framework ... turns out >> every page is actually decontructed in a clockwork of elements, all heavily >> based on python language. >> I'm not understanding WHERE to put my hands to edit this or that element >> of any given page... and even when I figure it out by tryal and error, then >> I have no idea HOW to modify the content. >> Some things look more or less familiar, most don't, and I'm feeling like >> progressing in a veeeeery slow crawl ... that I'm doing it all wrong. >> >> My website should be pretty simple... a couple of static "landing" pages >> and a blog-like system to easily post news and updates (with tags etc). >> And I wanted to try and DO something before resorting to full >> read-through of the whole web2py book. >> (which I skimmed briefly anyway) >> >> Most tutorials I found are either very basic (like the "Crash Course") >> and give no answers to my doubts, or very advanced, diving right into deep >> coding with no explanations to help along. >> Any help? >> Any pointers? >> Is a full and attentive read-through of the online book my only (or best) >> way to go BEFORE I even consider firing up the web2py program? >> > -- --- 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/groups/opt_out.
