[Michael Morris]

Beta 0.0.2 introduces a major change in how Joomla handles modules. Traditionally Joomla wraps module content in one of 4 wrappers - div, 3 div, table or raw. The code of frontend.php and frontend.html.php has been rewritten so that now Joomla calls the vbulletin template engine to perform the wrapping process. The exact wrap used depends on which module position was used. The tradeoff (for the moment) is the moduleclass suffix is ignored. However this allows for much more powerful templating of the module blocks than CSS can hope to offer. It also moves the control of the module appearance fully into the vbulletin template engine which I'll wager will be more familiar to users than Joomla's engine anyway.

Tomorrow night I will do the same thing to Joomla's com_content component. Most Joomla content goes through this component so that should complete the skinning process - just keep in mind that 3rd party modules may use wildly different schema for populating their content block.

Also progress is being made on the module to view recent threads out of the vbulletin database. For those familiar with vbAdvanced you'll find most of the same options in the Joomla version of the latest topics module - but one major difference is the Joomla version will have a caching system so that instead of loading the recent threads on each view of the thread list at set intervals. This is for large boards like ENWorld where such queries can slow down the system noticeably.