Hi Michael, > 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. 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. > in case someone thinks this is some kind of weird promotion: i don't > really want to advertize plone here - but it's all i can take > as example > for the things i do. Absolutely not a problem on the CMS list. This is exactly the kind of discussion this list was started for. P ********************************************************* The CMS discussion list for http://webstandardsgroup.org/ *********************************************************
