Hi Thiago, thanks for your reply!

Totally agree with your statement: Tapestry templates are meant to be used
by developers, not users. 
But in our CMS there are some sections which will require some technical
knowledge.
The good thing of templates is that they are easy to understand by a web
developer 
as it´s a mix of html and some components. 
For example we want to be able to publish any web static file (css,
images,etc) and templates.
For the first one I´ve already used some tricks creating a contribution to
the assetFactory and assetAliasMAnager so now I can do things like

@Inject
      @Path("uri:http://www.someurl.org/myfile.jpg";)
      private Asset testAsset1;

@Inject
      @Path("uri:file:///C/templ/myfil.png")

About your question:
> What parts of the page need templating? 
Everything. The idea is that we use the cms as a way of defining the page as
layout made of different blocks in the cms. So you can see our POJO objects
in the cms are Page, Block (and loads of subtypes)
Each block will have a template (.tml). So we want to be able to modify the
template just publishing from a CMS. Probably the CMS could be in other
machine, so probably using shame shared NFS would do.
Other issue I´ll have to face is about caching templates, because I´d like
T5 to detect when a template has changed to remove it from the cache) 

As you can see we do really need an external template loading mechanism. 

Ideally I´d like to register in my module a new implementation of
PageTemplateLocator
Any other idea how can I do this? (If you think override PageTemplateLocator
is not the right thing..)

Thanks 

-- 
View this message in context: 
http://tapestry-users.832.n2.nabble.com/How-to-load-tml-files-from-the-filesystem-instead-of-classpath-tp5009386p5011085.html
Sent from the Tapestry Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to