Good and bad news.
I got a job!
But It’s with SQLServer 2000, and I want to do Ajax.
I’ll hopefully be bringing you some cool hacks that will make web development easier…
For instance, I know that if I work on it, I’ll be able to get an ASP class that turns SQL queries into well-formed “For XML Explicit” queries. Of course, I want to make it a class because the admins claim they’ll be getting sqlserver 2008 sometime soon (of course, they also had planned to get sqlserver 2005).
Also, I’m currently using spry, and so I’ll be trying to make that rather dandy too. I think that the number one debug issue I have is detecting malformed XML from the sqlserver, so I’m going to be making template xml pages, so that my AJAX will quickly throw out a “Oh snap, one of these things is not like the other” error. Mainly, that’s going to be heavy and slow things down a lot, so I’ll code that later when I start hitting more bugs as I grow my database… that way I can load it and it’ll hopefully integrate with the spry debugger (that thing is spiffy).
What this all means for this blog is that, as I figure stuff out, I’ll hopefully log it in here.
Up next: getting RHS to make my AJAX create bookmarks and a history for the web browser… and somehow get it to work on everything (except safari. As it is, I’d rather ‘explore’ than go on a safari. And lizards are neato. So, I’ll be prejudice and also the incompatibilities that I overheard about DHTML and safari were… cooky sounding. Anyone know if I’m off base to exclude safari?).
Also, I’m going to be making some strange uses of SPRY that… might break it. I’ll post if something goes awry.
