So now there's an alternate proposal for TWIG 3. It's much less ambitious, and completely based on improvements from the current codebase rather than my work so far. Sort of annoying. But there's an upside to this, and it's that I may be able to convince everyone else of the dire need for good UI's in TWIG for first-time install, setup, ongoing configuration, and first-time user logins. Frankly, if we can tackle all of that then I'll be happy calling it TWIG 3.
March 2005 Archives
Finals this quarter weren't horrible so much as because the tests were hard, but I just wasn't in the state of mind for them. Total bummer. I'm wishing myself luck in passing classes. Otherwise. No otherwise.
On a more exciting note, I'm in the process of rewriting the TWIG Admin Manual into DocBook. Apparently it was originally written with MS FrontPage, then lots of editing by hand, then let to rot for too many versions. DocBook is a semantic markup format that can easily produce HTML, PDF and other formats with pretty looking layout. I really don't want to spend more than a long afternoon on this; I'm not going to rewrite the actual manual right now, just convert the data over to DocBook, generate something good looking but still horridly out of date, and make it much easier to be updated in the future.
And thenceforth a fortnight later the bugs were done or passed along. Big relief. Can't wait for the next releases! I need to kick some butt on my computer science homework this weekend. It's almost mind numbing, because the instructor wants things done in just such a way, and worse yet, on tests, won't accept any form of written explanation. Code or die. On paper. This must make sense to people who come to these classes with their own experience and knowledge in square one, but mine's not. I hate coding real C on paper. Where they ding you for all sorts of stupid syntactic and even sylistic conventions. Dude, it's paper. Not paper tape, not punchcards, but pencil and paper. I code in vim.