to be arrogant (hehe): plones skin isn't just a skin - it's 50% of the application.
Maybe that's the issue here. The skin should not be entwined into the
application.
okay you missunderstood this here ;) it's *not* entwined - but it just brings a lot of features and optimizations out of the box. (the stuff i've mentioned) there are also people that are writing completly new skins (like tonico strasser, which is also from this list). but as i said, you're throwing away 50% of plone if you do that ;)
but would really have to look at plone to judge yourself.
To use the language that's in place, you're building your skin with the muscle attached to do the work. The muscle and the skin are two entirely different organs. The skin should be just to write the available data into the required output language (html, xml whatever). The muscle or engine should just make the data or variables available.
again: we we're not mixing things together which makes it extra-hard to make a completly different skin. but there are technical reasons (i've mentioned them earlier) why we can't guarantee that it'll work with the new version as good as with the earlier version(s) - or even at all. we're just a bunch of guys, really caring about ui, dealing with concepts to make things easier and faster for webdevelopment with our product ;)
regards, michael -- </gro.jiin//:ptth> �jiin ********************************************************* The CMS discussion list for http://webstandardsgroup.org/ *********************************************************
