Antwort: Re: Antwort: RE: T5 Decoupling a Template From its Component Class

14:10 Bitte antworten an Tapestry users users@tapestry.apache.org An Tapestry users users@tapestry.apache.org Kopie Thema RE: T5 Decoupling a Template From its Component Class On Mon, 2007-07-02

Re: Antwort: Re: Antwort: RE: T5 Decoupling a Template From its Component Class

an Tapestry users users@tapestry.apache.org An Tapestry users users@tapestry.apache.org Kopie Thema Re: Antwort: RE: T5 Decoupling a Template From its Component Class On Mon, 2007-07-02 at 16:06 +0200, Kristian

RE: T5 Decoupling a Template From its Component Class

Digging through the code I notice there is a PageTemplateLocator interface which seems like the appropriate service to override. What I have tried is to add the following method to my AppModule class public static void bind(ServiceBinder binder) { ServiceBindingOptions options =

RE: T5 Decoupling a Template From its Component Class

@tapestry.apache.org Kopie Thema RE: T5 Decoupling a Template From its Component Class Digging through the code I notice there is a PageTemplateLocator interface which seems like the appropriate service to override. What I have tried is to add the following method to my AppModule class

RE: T5 Decoupling a Template From its Component Class

An Tapestry users users@tapestry.apache.org Kopie Thema RE: T5 Decoupling a Template From its Component Class Digging through the code I notice there is a PageTemplateLocator interface which seems like the appropriate service

Antwort: RE: T5 Decoupling a Template From its Component Class

users@tapestry.apache.org An Tapestry users users@tapestry.apache.org Kopie Thema RE: T5 Decoupling a Template From its Component Class Digging through the code I notice there is a PageTemplateLocator interface which seems

Re: Antwort: RE: T5 Decoupling a Template From its Component Class

an Tapestry users users@tapestry.apache.org An Tapestry users users@tapestry.apache.org Kopie Thema RE: T5 Decoupling a Template From its Component Class On Mon, 2007-07-02 at 11:03 +0200, Kristian Marinkovic

Re: Lehky_SPAM: Re: T5 Decoupling a Template From its Component Class

Hi Howard, I would like to ask, whether there is still possibility to have localized templates? eg. org/example/myapp/components/CClamp.html org/example/myapp/components/CClamp_en.html org/example/myapp/components/CClamp_en_US.html org/example/myapp/components/CClamp_de.html Thanks Howard

Re: Lehky_SPAM: Re: T5 Decoupling a Template From its Component Class

yes, that;s still supported and documented here: http://tapestry.apache.org/tapestry5/tapestry-core/guide/localization.html On 5/31/07, Jiri Mares [EMAIL PROTECTED] wrote: Hi Howard, I would like to ask, whether there is still possibility to have localized templates? eg.

T5 Decoupling a Template From its Component Class

I am a Tapestry newbie getting up to speed on Tap 5. I am working on an application with extensive co-branding requirements. As I understand things, there is - by default - a tight coupling between a component class name and its template path. For example - if a component has a FQCN of...

Re: T5 Decoupling a Template From its Component Class

There are internal services that can be overridden to handle those kinds of situations. The goal is to create something that works amazingly well for all the more typical cases, then start going after these others. Often it will involve moving a private interface out into the public space ...