scperkins/SuiteHouse — pull request #3 by EJEHardenberg (2013-06-10 03:57:15+00:00)
Title: App Engine Folder

I added in the app engine folder (run it by going to the directory above it and running the dev_appserver.py SuiteHouse command. The way I'm envisioning it is that we have the app.yaml file map the root level controller class (like finance/finance.py) to all urls for /controllername (/finance.*) and then let that class handle the redirects inside of it. That's what I'm currently doing in the finance directory. You can look in the app.yaml and see all finance url's being directed the the finance.py script, and then inside that it handles /finance/checkbook /wishlist /... etc. I think it's a good way to keep things modular and seperated. Also, if we move entirely to the app engine, I already reserved the appspot name for our application so we can deploy it up there when it's done for any user testing we might need.

In addition I was talking to my friend whose a graphics designer and she might help us out with the css and visual elements of it which leaves us with more time to work on the applications themselves. I have a hankering for finance applications (I couldn't tell you why) and it sounded like when we chatted before that you were thinking of getting your javascript on for the task stuff? That'd be cool. Could also work on the finance stuff with me. The wish list is pretty simple, name and cost of an item html5 has the type="number" to input tags which we can use to restrict people to just numbers and some other stuff. I have some example code (not in this repo) that I can send you if you want. Also besides wishlist there's also the checkbook and bills...book thing. I was gonna start working on the checkbook but if you wanted to start playing with either the wish or bills list that'd be cool. Wishlist is the easiest I think because there's no date or time attached to a want, but with the bills there is , html5 gives us the type="date" for inputs which we can use to have a really nice calender, but I'm not sure about the form of that data itself and how we'll map it to a python object yet. I suppose more reading of the GAE's documentation is neccesary or a consulation the the-hobbes