Hi All,
fyi, I couldn't resist trying out Artisteer 3.0 since it is very close to shipping.
For those working from the mojoPortal source code repository, support for Artisteer 3.0 has landed in the repository. I've upgraded the artisteer-24* skins to artisteer-30* and added 2 new skins, one was a sample included with Artisteer, it is named artisteer-30alphamotors, and one that I created myself named artisteer-30business1. You can also see these skins now on demo.mojoportal.com
I have archived the previous versions of those artisteer-24* skins and will make them available in the extraskins.zip file that is available with each release, so they will still be available for those who do not upgrade to Artisteer 3.0 for whatever reason, but I could not see keeping them in the package since the 3.0 versions of the same skins are the same designs just with slightly different implementations.
There are of course some differences in the output produced by Artisteer 3 than previous versions. Most of the changes are reflected in the layout.master files of the new version skins, but there were a few minor changes that needed additional options in mojoPortal to produce the correct markup. These differences are reflected in different settings in the theme.skin file which enables the new markup, while previous versions of Artisteer are still supported by other settings in theme.skin in older skins.
The instructions for creating a mojoPortal skin from an html export from Artisteer are essentially the same as before except that you use the artisteer-30* skins as a starting point. Which skin you use as a starting point is still based on the menu location and whether using vertical horizontal or both menu types. The new Fluid layouts of Artisteer have no impact on this since there is no difference in html markup for fluid layouts, only differences in CSS.
You'll notice that the files exported by Artisteer include jquery.js (which actually has both jquery and sizzle.js inside it), since mojoPortal already includes jquery you do not need to include that file in your skin. I've added sizzle.js as a separate file and there is a setting on <portal:ScriptLoader in the artisteer-30* skins that makes it load the sizzle.js.
So, if you are working from our repository, feel free to try out Artisteer 3.0 designs and let me know if you run into any problems.
Best,
Joe