On Thu, 2010-01-14 at 19:09 +0100, Florent André wrote: > GREAT thanks Andreas, your answers help me to fight down the graphical > template of my pub without pollute the default publication ! > > During my template war I have an idea. What do you think about that : > > - Have a "templates" folder under default pub or mypub > - in this templates folder we have : > -- classic_template > -- punchy_template > -- my_template > > - and in each *_template folder we have this structure : > -- xsl > -- css > -- images > > IMO, it's make the graphical templating dealing more easy for user and more > simple to share graphical template in community. > > The "problem" I see is that it will cut the actual idea of templating in > Lenya. A graphical-template tag have to be add in publication.xml (as I > imagine this for now...). > > On the other hand, during the Vik's training, Torsten speak about his > "forrest template mechanism" (if I well remenber the name). His mechanism > seems to be very powerfull (like Thorsten is :) ). If the "forrest Dad > could" say something about that, it could be cool. > > Wish you a great year Andreas > (and to Thorsten... if you anser :) )
Sorry just saw this thread. If you mean integrating the dispatcher into lenya as a templating engine that is possible but not that easy. One would need to rewrite the part of aggregating the page components and further implementing that lenya is aware of using the structurer template. salu2 > > ++ > > On Thu, 14 Jan 2010 18:44:50 +0100, Andreas Hartmann <andr...@apache.org> > wrote: > > Am 14.01.10 18:32, schrieb Florent André: > >> > >> One more information, and one more question :) : > >> > >> Information : > >> - the error appear uniquely in authoring area, not on live... > >> > >> Question : > >> - the "template" idea of Lenya (and in consequence the template-fallback > >> protocol and template tag in publication.xml) are just related to > >> *graphical* template, or also to *administrative* template (workflow, > >> users > >> management, etc...) > > > > The fallback mechanism applies to all resources that are referenced > > using the fallback:// protocol. That should include virtually all > > resources in a publication, including sitemaps, stylesheets of all kinds > > and the workflow schema. > > > > Regarding users: IIRC you can specify a shared access control (users, > > groups etc.) directory in access-control.xml. > > > > HTH, > > > > -- Andreas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@lenya.apache.org > For additional commands, e-mail: user-h...@lenya.apache.org > -- Thorsten Scherler <thorsten.at.apache.org> Open Source Java <consulting, training and solutions> Sociedad Andaluza para el Desarrollo de la Sociedad de la Información, S.A.U. (SADESI) --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@lenya.apache.org For additional commands, e-mail: user-h...@lenya.apache.org
