STrRedWolf (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
strredwolf) wrote2005-06-19 12:25 am
strredwolf) wrote2005-06-19 12:25 am
Geriatric code. Can't stand it.
I can't stand geriatric code -- code so anchent it's a wonder it works. KeenSpace's autoupdate engine is the main highlight here.
I'm rewriting it. Parts are already working on the Wolf357 engine, and I'm testing it with my own comic on my laptop.
The design is much better -- metainfo (from the DB) is stored in a hash (comming from an SQL DB), and comic dates are stored in a hash of arrays. It's in Perl (like the old code), and uses Perl 5's reference (aka C-like pointers) features to keep the organization sane. Plugins are designed to be "write, chmod +x, and forget" instead of having to edit a central configuration file.
***todays_comics*** is implimented and tested.
***advertisement*** is implimented, but not tested.
***first/next/previous/last_day*** is being implimented.
I need to go through and see which tags are being used. Hei-ho shell scripting!!!
I'm rewriting it. Parts are already working on the Wolf357 engine, and I'm testing it with my own comic on my laptop.
The design is much better -- metainfo (from the DB) is stored in a hash (comming from an SQL DB), and comic dates are stored in a hash of arrays. It's in Perl (like the old code), and uses Perl 5's reference (aka C-like pointers) features to keep the organization sane. Plugins are designed to be "write, chmod +x, and forget" instead of having to edit a central configuration file.
***todays_comics*** is implimented and tested.
***advertisement*** is implimented, but not tested.
***first/next/previous/last_day*** is being implimented.
I need to go through and see which tags are being used. Hei-ho shell scripting!!!
no subject
Like this is what I'd like to do:
Probe for a template, compile this in memory, spit out the flatfiles, basically changing the variables for each comic.
The ***todays_comics*** is the source of much trouble since it assumes that all comics you want one-after-the-other, when it really should only put one comic in, but compile a one-time include file where if defined as css, table, or one-after-the-other it would pre-generate that the first time, and never have to regenerate it.
Oh
xHTML and CSS compliance please.
Two tags I'd like to add, if we can address the xhtml/css compliance is ***header_data*** where it would put in the link to a css file defined (remember, people know how to change colors, not code if they don't know html) or replace the entire header/footer with ***all_headers*** which would replace advertisement, and ***all_footers*** which would put all the footer data in. The all_headers would address the html declaration, all the HEAD data so all the features would be available (css, rss, loading hints, meta tags, etc) It would then go as far as the body tag, put the advertisement in the "above the fold". Expert users can then go back to just the advertisement code if they wish. Have autokeen make sure that the advertisement is placed only once.