Hi,

The cornerrounders in theme.skin if DoRounding is true just renders the extra markup needed for nifty corners though it uses divs rather than <b>

Then css is applied, you can find it is used in most of the dcarter-* skins in our extra-skins.zip

for example this is the css in dcarter-businessone:

/* Corner Rounding with Nifty Corners */
.rtop,.rbottom { display:block; background:#F5F6F0; }
.rtop .r1,.rtop .r2,.rtop .r3,.rtop .r4,.rbottom .r1,.rbottom .r2,.rbottom .r3,.rbottom .r4 {
background:#E1E5D5;
display:block;
height:1px;
overflow:hidden; }
.r1 { margin:0 5px; }
.r2 { margin:0 3px; }
.r3 { margin:0 2px; }
.rtop .r4,.rbottom .r4 { height:2px; margin:0 1px; }
.rbottom { margin-bottom:10px; }

.center-leftmargin .rtop,.center-leftmargin .rbottom,.center-rightmargin .rtop,.center-rightmargin .rbottom,.center-nomargins .rtop,.center-nomargins .rbottom,.center-rightandleftmargins .rtop,.center-rightandleftmargins .rbottom,.logolist,.pageicons,.skiplink {
display:none;
}

However the newer niftycube stuff looks like it creates the extra merkup from javascript. I don't see any reason why you couldn't use it in mojoPortal though I have no specific advice for you and don't have time to experiment with it myself. If you study the existing markup you should be able to figure out selectors to use with it.

It isn't something I plan to ever include in mojoPortal because NiftyCube javascript is licensed under GPL which is not a compatible license, so I cannot ship it with mojoPortal, though there is no reason you can't use it on your own site if it works for you.

Really I don't see a huge benefit vs the older NiftyCorners since they are adding the extra markup one way or another in order to do the rounding with css. I'd just enable it to be rendered using our theme.skin file and use css with no need to load extra javascript. The only advantage of the javascript approach is to be able to leave it out of the raw markup but we can do that by turning it off in theme.skin anyway. So how that extra markup gets in there is not important, it will be faster just rendering it rather than using dom manipulation from javascript.

Also all of this approach is old school and can be done with newer CSS 3 things without extra markup or javascript.

Best,

Joe