I am still working on the tag board :p It took me a whole day to figure out what needed to be done for version 2.0 and then it took me like an hour to do the coding for version 3.0 and *I* think version 3.0 is more complex since it uses a mySQL database to store the tags :p The biggest problem I faced with 2.0 was that I wasn’t debugging it properly :p I would make a script change, upload to server and then run it and it would say “Server error” but not provide me any useful Per errors. I continued to (stupidly <g>) make changes in the dark and upload to server for most of the day till I realized that it just wouldn’t work that way. So I enabled IIS on my machine, set Perl up to handle CGI requests and had pinpointed the error in a matter of minutes Once I got that sorted out, the rest was a cakewalk.
I haven’t worked with mySQL before and so don’t know how fast data access and response is. I have created the new version of the tagboard to add new tags to the database and then recreate the whole tagboard display again from the raw input so as to incorporate any new formatting/smiley rules that may have been added to the code since the last run. Most tagboards I have seen do the formatted output once and so code changes to the formatting aren’t applied to the old entries. I know my method is slow but what I’m interested in finding out is how slow :p If the response time is acceptable, I think I will stick with my method since it gives a lot more flexibility to the user/coder. If this works, then it’s on to version 4.0 which will add administrative access and the ability to simply click on a user and ban them or delete their post and I think that will be it from me for this session of Perl coding.
I haven’t been slacking on other coding stuff while working on the Perl stuff though. I’ve also managed to add B2 support to BlogMan, incorporate proxy support for all the API calls and even got started on the documentation :p I hope to release the first beta today (or at least upload all the screenshots, BlogMan page and the distro today) though the announcement itself might not come till tomorrow. I want to test it out one more time on Movable Type before I do that though and that will probably come in the form of a new entry for SM since I do have a rant about the American embassy (or rather the Sri Lankan personnel working there) and the whole visa process :p
In the meantime, I have received several more interesting ideas suggestions for Blog but the only one I can remember is one from Duane about having a set of default settings for Blog. Duane wanted this so that he can setup Blog a specific way and then send it to a friend so that they don’t have to do any setting up. Since the Blog configuration is spread over multiple files, the only way I can think of to do this is to have two options “Save as default” and “Restore Defaults” where the former would actually copy all the data files and the Blog.INI file to a special directory (probably named “defaults”) and then the latter will copy the files back from there. Seems like a good idea to me actually – what does everybody else think?