This post originated from an RSS feed registered with Python Buzz
by Victor Ng.
Original Post: CrazedAndCranky with PEAK and Webware
Feed Title: Victor Ng's Weblog
Feed URL: https://blog.crankycoder.com/feed/atom/
Feed Description: Python Feed
I've spent the better part of the last week playing with PEAK trying to figure out the odds and ends of the PEAK framework. There's definitely pieces of code that I can use right now - specifically the binding, naming and config APIs. Wiring up components and locating services will be a hell of a lot easier from now on (btw - thanks Ulrick! My brain is a little fuller after Friday's long IRC session). Again - if you're not comfortable with really alpha level software with very little in the way of documentation - stay away from PEAK.
Yesterday was bake day - I helped Liz make some "Chinese Chews". Being half chinese - I have to say that the cookie resembles more of a beaver dam than anything that came from China. But what do I know? There's a big batch of peanut brittle and almond brittle (yay samples!). Some of that comes with me to work tomorrow.
And of course - today was nerd day. Hacked a tiny bit of Python code with Ian. Mostly it was getting comfortable with pair programming via SubEthaEdit and my iBook and Powerbook, going over the somewhat crufty Webware/WebKit API and how I saw PEAK fitting into grand scheme of what I see as a nice set of re-usable webapp tools.
Considering it was the first day - not too bad. I think we covered a lot of ground and we'll have to spend a couple more sessions together to get some real code up and running. SubEthaEdit is very sweet for pair programming. We had the two laptops running side by side with SubEthaEdit sharing the Python servlet that we were working on. It's nice to be able to work together on the same file - but what makes this particular way especially nice is that while one of us is programming, the other can actually double check the API in a web browser to verify what's going on without having to interrupt my 'flow' as I'm writing code. 2 monitors means 2 windows in the foreground.
Cool.
The main thing we learned today - Webware needs a refactoring. Badly. There's a ton of weird code sitting around in places like the SidebarPage.
I'm pretty sure that a reusable side navigation page renderer doesn't have to have SourceForge. Or Python.org. -- Ian Stevens
The bright side is that Webware is open source - so we're starting to hack the bits of Webware that we feel are ugly and need a cleanup. This is going to be fun! I've got my own ideas about the current configuration mess in WebKit/Configs - want to flesh'em out a little on paper before I start spewing my not-so-well-thought-out ideas on the web though.
So - current Pythonic toolchain for web app development: Webware, Cheetah, PEAK and SQLObject.
Previous Topic
