It sounds like what you are doing with the skin object is the same as what cufon is doing?  Cufon uses javascript to "find" a specific class, generate an image using a javascript font file, and splice in the image.  The original text is hidden by the generated image which renders on top of it, but still visible to web crawlers so there is no seo concerns at all.  Anyway, hope you didn't do too much along the lines of reinventing the wheel so to speak... I've used cufon on a couple skins to render the website name in the header as well as render module titles and it worked really well, and really fast to the point you don't even notice it at all.  The only problem I really ran into with cufon was it didn't play nicely with the png fix javascript I was using, but then none of the png fix scripts are really very good at least since I last looked at them... Browsers that don't support png's should have self-destructed by now with everything that has changed on the web since IE6 was the most used browser... Not sure those ancient versions would even work except in an intranet that's beyond outdated and not used to access the outside world!

JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke  

Hi,

Any idea when you will release the skin object Timo ?
I would love to try it out.

I'm using Cufon at the moment but it gives me problems when using edit in place on my module titles. It shows the code that generates the image replacement.

Regards,
Ely
HolonCom

I have been very busy recently, but will keep you posted.