Last night, I wasn't really feeling up to writing. Chapter 10 is giving me a bit of difficulty and I haven't muscled through it. Mainly, I'm not sure of the emotional transition during the first scene with a lot of tension. It is one of those scenes where things go wrong in a lot of different ways at the same time and I'm struggling with how the character would struggle through them.
One of the frustrating things is the appearance of the site. Every single site has a different way of creating themes. Some are fairly simple (SMF) while others require massive changes across the board (Mantis BTS). Most are in-between in complexity. More importantly, it takes 4-5 days to convert a base theme into the application-specific theme.
I had this great idea. Model-View-Controller (MVC). Why have the server do all the skinning for a website theme? Just move all the processing down to the client. Make them work for it and maybe reduce the amount of bandwidth transferred. I started with the XSLT PI (the thing). That worked very badly. As in crashed web browsers.
I did write this in jQuery, but I'm using the jQuery() calls instead of $() so it will integrate with Prototype or anything else that uses $(). I also don't have it include jQuery, just in case someone has a different version they want to work it.
The next steps in rough order:
- Reduce the footprint to a single theme file (Easy)
- Allow for theme switching using cookies (Hard)
- Allow for cookie-base settings for things like font sizes (Moderate)
- Get it documented (Easy but tedious)
- Throw a license on it, probably MIT or the MS- version of MIT (Easy)
- Figure out where it breaks (Hard and I need help from others doing that)
- Create a DokuWiki theme that can use the JS themes (Moderate)
- Create a Wordpress theme that can use the JS themes (Hard)
- Create a SMF theme that can use the JS themes (Moderate)
- Create a Drupal theme that can use the JS themes (Hard)