You could maybe try out the Quick Start here:

http://code.google.com/p/restler/

It's based on a RESTful controller I put together. It does require a
DB, but installing SQLite, say, is pretty simple. You could replace
the Monkey class in that example with a Page class and you'd have a
basic Pylons site up in running in under an hour.

__wyatt


On Apr 19, 6:28 pm, Heather <[EMAIL PROTECTED]> wrote:
> I've been reading through stuff on the pylons site for the past few
> days and feel like I'm not really getting anywhere.  But I'm a girl
> and have no problem asking for directions :)
>
> What I want to do is pretty simple.  I want to build a site for my
> son's school so there really isn't much fanciness involved.  I have
> pylons whatever the latest version is, mako (because I read that's
> where you're headed), and SQLAlchemy (no good reason).  So what now?
> Start me off.  My index.html file goes in the template directory, no?
> How do I make it show up?  I make a controller class maybe?  Give me
> an example.  I want all my pages to have an in common header and
> footer.  What kind of files would these be?  Seperate?  Would they be <
> %def>s?  I don't need to worry about any database interaction yet - I
> just want to get the bare bones up and running before that jazz.  Oh,
> and I'm a java programmer, not a python programmer (ok, I'm just a mom
> now but once upon a time...)  I feel like they are similar animals
> from reading Learning Python or whatever book I have so I think I
> shouldn't have too much a problem.   Am I wrong?
>
> So, any takers?  Think of it as the groundwork for your new docs :D
>
> TIA!


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to