Web Frameworks Jam, continued
The TurboGears team finally is all working with the 0.9 release, and we made a lot of progress today. I was able to get the things working that didn’t work yesterday (i.e., the JSON support), and we moved forward, exploring the TurboTunes tutorial and more of the supporting code.
The TurboTunes tutorial is a lot of Javascript, so not as much in terms of kid and pure TurboGears, but it’s a nice looking demo. Here are some of our notes about that tutorial:
TurboTunes Tutorial Feedback
1.tutorial refers to prod.cfg, which doesn’t exist. Assuming should copy sampleprod.cfg to prod.cfg. No big deal, since we were in development mode anyhow (using dev.cfg)
2.In 0.9.a7, sqlite is assumed in dev.cfg … needs to be commented out. This is kind of annoying.
3.Tutorial uses old start command: python turboTunes-start.py, while new version uses start-turboTunes.py
4.Use tg-admin toolbox to start toolbox to access Catwalk. We were able to leave out all mounting of CatWalk, but still need to import model.
The Google Web Toolkit team seems to be doing well with their exploration, and the Spring team is making progress too. During the hiking breaks (and at dinner), we all discuss what people are doing. Ah, it would have been nice to have had more time, so that each group could have looked at another framework as well. Ah, sigh, but realistically, we likely would have just gone into more depth with what we were doing.
This afternoon, we all took a hike to Copper Creek. It’s up by Gothic, which is an old town now used by biologists. The waterfalls were gorgeous and the hike had more elevation (and length) than the previous days.
In the evening, a few of us went to see “An Inconvenient Truth”, which was (IMO) both fascinating and disturbing. In any case, it was great to see someone handing out flyers about how to convert to using wind power in Colorado after the movie.
Ah, tomorrow is our last day here, and I’m hoping that we can look at some more TurboGears in detail.