Jörn Nettingsmeier schrieb:
Andreas Hartmann wrote:
If you want WYSIWYG across multiple applications, I'd recommend the
following basic principles:
- Keep the templates as simple as possible.
- Avoid duplicating template logic. If you have to duplicate them, try
to generate them automatically from a single source (meta templates).
- Do everything you can in CSS. CSS can be shared.
In your specific case, I'd try to strip down the Tapestry templates to a
very basic XHTML structure, which can be duplicated in the Lenya
application with low maintainance costs.
why would anyone want to do that? if you are prepared to touch and
refactor existing templates, why not just migrate to lenya (or another
CMS) entirely? or is there something special that only tapestry can do?
As I understand it, the Tapestry site is a dynamic application - IMO
combining dynamic webapps with CMSs for static content is a quite
typical approach. But of course I can't tell if it makes sense in this
special scenario here.
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
