Thanks for the update Rick! I'm looking forward to trying the page-wide headers and footers with fixed-width page. That seems to be a popular styling choice these days.

Thanks Joe, your quick work is appreciated as always!

Jamie

Hi Jamie,

Artisteer 3.0 uses h3 tag for side bar columns, my recollection is that they just used divs for previous versions which was semantically unacceptable to me so the instructions were more complicated in order to have real headings there while still keeping the Artisteer style.

I'm not entirely wild about h3 there, really it seems like h2 would be better. The document structure should never have an h3 without an h2 somewhere above it, but they also changed the slogan to an h2 which I'm also not wild about but at least that makes the document structure correct semantically since it is above the h3s used in the left side bar and the h2 in the center is above h3 used in the right column.

So in the end I decided to just make it use the headings as prescribed/output by Artisteer because it does reduce the steps to converting the design to a mojoPortal skin. Someone like me with strong opinions about the headings could still use h2 in the side bars and modify the css accordingly, there is a setting in theme.skin on ModuleTitle which controls it.

I think there may also be some occasional design glitches (in some designs) when upgrading a design that was originally created in older versions of Artisteer vs new designs created from scratch in the new version. I also have noticed some rendering anomalies under IE 7 even in the html output from Artisteer (not just in the mojoPortal skin created from it) so I think Artisteer still has some bugs to work through. Hopefully these issues will be resolved in the final 3.0 release.

Best,

Joe

Hi Rick,

Thanks as always for the beers!

artisteer-greenlagoon was (I guess) produced with Artisteer 2.3 but I did not make that design, I downloaded it as an html template from here before I ever purchased Artisteer. It was my proof of concept first skin, after getting it to work I purchased Artisteer 2.3 and artisteer-swirly1 was the first one I made myself (though I never thought it was very good looking). So I keep those 2 skins around primarily so people can use them as a starting point for Artisteer 2.3 or from designs downloaded from the above linked site. I also agree that artisteer-greenlagoon is one of the best looking ones, I think Artisteer had some licensing issues and changed some of the images included in the product since that beach image does not seem to be there anymore.

I'll have to re-export the skins using the latest update and then again with the final release.

Best,

Joe

Hi Mario,

So you are working from our source code repository? That is the only version of mojoPortal that has the needed changes for Artisteer 3.

If you are using the latest mojoPortal code and having trouble with an Artisteer 3.0 skin, you could zip up both your skin and the .artx file and send it to me at joe dot audette at g mail dot com and I will take a look at it tomorrow. 

Best,

Joe

Hi Mario,

Yesterday I made a fix in the Artisteer menu so that it now correctly highlights the currently active page. If you get the latest code and rebuild the solution I think you will find it works correctly.

The only other problem I noticed was the dynamic sub menu in your skin was using white text on a light colored background. This is probably caused by the javascript for the ASP.NET menu which sets some style on the menu that conflicts with the Artisteer CSS. I was able to fix it by adding this in your style-artisteer-overrides.css like this:

.art-menu a .t
{
  color: #232F13 !important;

}

the color is the same as defined in style.css but the !important makes it work around the style added by the menu javascript.

Hope it helps,

Joe

Hi Mario,

I think you are not getting the updates correctly, you should not be doing any merging nor using the joedev branch for anything, that is my developer sandbox, I merge my changes from there into the default branch and you should always use the default branch and never use my sandbox branch.

After you pull all change sets by using the green down arrow in Repository Explorer, then you need to close out of Repository explorer and right click the topmost folder and choose TortoiseHG > Update to apply the change sets to your working copy. In the update dialog make sure it points to the default branch do not update to my joedev branch.

I'm not sure the implications of the merging you did, you may need to get a clean clone of the repository if all else fails.

Hope it helps,

Joe