Version 1.4b11 of the Qwicap Java web application framework (or anti-framework, IMO) has been released. This beta kind of got away from me, frankly. It really should have been broken-up into a succession of betas, and possibly version 1.5 betas, at that. But I was running low on things to do before declaring version 1.4 done, and some untouched items on the original 1.4 "to do" list were staring at me, and I started to think that it'd just be a downright shame to go to release without a few more of those features. One thing led to another, of course, and here we are.
My project management skills aside, good things have happened to Qwicap. Notably, this version embraces Java 1.5, provides Qwicap's first support for internationalization/localization/multi-lingualism, and allows Qwicap applications to run both directly from their WAR files, and within the default configuration of the Security Manager in Tomcat. It also wraps-up the effort to make Qwicap fully character-set aware. (It's so character-set aware at this point, that you can make web applications that operate entirely in the EBCDIC code page of your choice, or in any mix of the many other character sets known to Java. The limiting factor is the range of character sets supported by the various browsers, and the bugs therein.) See the change history for full details.
By the way, in connection with Qwicap's new internationalization features, I'm looking for people with good non-English language skills who'd be willing to translate Qwicap's internal error messages (there are something like 22 of them), and its "number guess" example application (one web page, and a few other strings). I expect that Qwicap's internationalization features will evolve with use, so translations will help not only with the actual translation problem, but will probably aid in the refinement and growth of Qwicap's internationalization API. If you're interested, there's contact information on the Qwicap main page, or you can leave me a comment here.
No comments:
Post a Comment