From: Chris C. <ch...@cp...> - 2007-11-26 20:50:22
|
A Bowtell wrote: > > > > Denis Mishunov wrote: >> >> >> I think there is no need in "just-another-one-skinning-doc". What we >> need is maybe collect all information in one reference-like document >> with links to already-existing documents. >> >> > > That was my idea - an overall reference rather than a how to. It would > simply help to point people in the right direction. Even with the > tutorials and Martin Aspeli's book it was really hard and after a while we > just got in a muddle with all the documents and files we had open. > > Anne > > That's me too. I consider myself a technical person but not a developer and I have read all this material a number of times and don't have a clear understanding. Could I add the following points needed to be included IMHO; Are 'Theme' and 'Skin' synonyms in every case? Are Skin Layers Theme Layers? Why override in browser and not a skin layer? Merits of each. Is main.css the preferred place now in Plone 3? Where TTW do you override this? Is DTML use of Base Props the only reason for using a skin layer? And please please a diagram showing the dependencies of files/objects in a 'Product' interfaces.py, configure.zcml, profiles.zcml That's my wish list :) -- View this message in context: http://www.nabble.com/Skinning-reference-for-Plone-3-tf4873938s6744.html#a13958532 Sent from the Documentation Team mailing list archive at Nabble.com. |