Back to seating charts

Last couple of days I've been working on mapping technology that is required of my seating charts. Lots of python scripts. Been having the hardest time just getting some examples working on this python based map server. 1 week ago I had never touched anything python in my life and now I'm having to dive into the belly of some of these python scripts to get this to work on windows. I suspect the scripts were originally written for unix or a Mac so certain things aren't wired up to work properly like path variables etc. Oh and this stuff has all kinds of dependencies so there is been a crap load of installing other python packages. It's absurd how much I've had to learn in just the past week. But these seating charts will be worth it. Just a few more hurdles to overcome like having a properly assigned spatial reference and figuring out how to cache my maps. From there it should be smooth sailing.

I hate CSS when doing layouts

I hate CSS when doing layout stuff. I could take a vacation with the amount of time I've wasted trying to do with Divs what I can do with a table in minutes. They should have made CSS with some constraint based selectors so element heights and widths could be defined as a function of other element heights and widths. Just like how one constrains layouts in a CAD program. Float and clear just don't cut it and all too often we have to fall back on absolute positioning and JavaScript to achieve a truly fluid layout that doesn't screw up when changing the browser zoom level.