Re: Tapestry 5.3-beta-9
Hi Howard, Just to say I've not been able to replicate the lock-up I had with beta-8 when working with beta-9. Steve. On 17 September 2011 08:09, Howard Lewis Ship wrote: > I've just uploaded 5.3-beta-9. This corrects (hopefully) the deadlock > problems in beta-8, and adds a few minor fixes beyond that. > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Datefield update causes PageAttached TAP 5.2.6
I'm not sure you can, for when you use the calendar selector, it makes an ajax call back to the page component for parsing and formatting. Of course, this means attaching a page to find the component! From the DateField docs: * One wierd aspect here is that, because client-side JavaScript formatting and parsing is so limited, we (currently) * use Ajax to send the user's input to the server for parsing (before raising the popup) and formatting (after closing * the popup). Weird and inefficient, but easier than writing client-side JavaScript for that purpose. There's another DateField component in TapX, but not having used it, I don't know how it works. http://tapestry.formos.com/nightly/tapx/tapx-datefield/ Steve. On 17 September 2011 14:29, Koka Kiknadze <226...@gmail.com> wrote: > I have noticed that pageattached is called each time I change value in > DateField using calendar selector but not if I manually type in the value. > > What is the purpose of such behaviour and how can I avoid > calling pageattached ? > > TIA > Nicholoz > > TAP 5.2.6 > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Datefield update causes PageAttached TAP 5.2.6
I have noticed that pageattached is called each time I change value in DateField using calendar selector but not if I manually type in the value. What is the purpose of such behaviour and how can I avoid calling pageattached ? TIA Nicholoz TAP 5.2.6
Re: dereferencing
This is a good question (if I understood you correctly!) for it often
confuses people.
A good rule of thumb (and the short answer) is never use
${expressions} in ="attributes", only use them to print out text in
your HTML.
The longer answer involves understanding what's going on; you'll see
you don't really need ${expressions} at all - they exist largely for
your convenience...
If, in your .tml, you want to output a title given by getTitle() in
your java class then you can use the core output component:
public String getTitle() { return "Mr Cool"; }
Note the prefix of "prop:", this tells T5 how to interpret the rest of
the string and is called a expression binding. There a number of
default expression bindings provided by T5 and, of course, you can
contribute your own. The default bindings are listed here:
http://tapestry.apache.org/component-parameters.html
By far the most common bindings are 'prop:', 'literal:' and 'asset:'.
In fact, 'prop' is so common it is the default binding, meaning if
you don't supply a binding it is implicitly assumed to be 'prop'.
Therefore you could write:
And T5 will know what you mean. But what does 'prop' do?
It is helpful to think of 'prop' as providing a pointer to your getter
/ setter (and you'll see why in a minute), so above we provide a
pointer to the property 'title'. The output component uses the pointer
to 'get' the property and prints it.
So what does ${title} do then? Well, ${expressions} are evaluated,
much in the same way as 'prop' bindings, but the *result* is passed
on, and not the pointer reference. So if we were to do:
the expression ${title} is evaluated to "Mr Cool" and it is this
string which is passed to the output component, which simply prints it
out.
That worked, but here is where it fails. Lets say we have a list of
Strings called books, a String book property and the following in the
.tml:
...
${books} would be evaluated and passed to the loop's source parameter.
But when loop wants to set the parameter 'value', ${book} is evaluated
to a (presumably null or empty) String and is passed to loop. But loop
can't set change this String to anything, because it's, well, a final
immutable String! So instead it throws an exception saying 'book' is
read only.
Compare to:
...
Here we're back to passing pointers. So 'loop', again, happily reads
the books source property. But loop tries to set the book value, it
has a pointer to the getter / setter and simply uses it to set a new
value for book. It works and everyone is happy!
If unsure, it is good practice to always explicitly provide bindings
in your attributes - that way you're sure to know what is being
passing around and it should help avoid confusion.
Hope it helps,
Steve.
On 17 September 2011 10:42, Ken in Nashua wrote:
>
> Hi All,
>
> Under what conditions would I operate the ${} for a property... or not...
>
> Just trying to understand the scope and range of when to de-reference a
> property.
>
> I look at tml code and sometimes I see properties referenced directly and
> other times with ${...}
>
> Thanks for any clarification.
> Ken
>
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
dereferencing
Hi All,
Under what conditions would I operate the ${} for a property... or not...
Just trying to understand the scope and range of when to de-reference a
property.
I look at tml code and sometimes I see properties referenced directly and other
times with ${...}
Thanks for any clarification.
Ken
Tapestry 5.3-beta-9
I've just uploaded 5.3-beta-9. This corrects (hopefully) the deadlock problems in beta-8, and adds a few minor fixes beyond that. -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: PageRenderLinkTransformer, SessionState and InjectPage
On Fri, 16 Sep 2011 17:14:58 -0300, Dimitri wrote: Hi all, Hi! I m using the new PageRenderLinkTransformer thing, very helpful but, in the decodePageRenderRequest i would like to set up some things for others pages. I can do it either by injecting page and call the appropriate methods one those, or use a session state object. You could also set data in a per thread service and make your pages use it to read this data, avoiding using the session for something that is just for a request. That's what I'd do. Unfortunately, the SessionState object does always result as null in the next pages. Injected pages are not injected as well, and throw NPE when calling the appropriate method on those. @SessionState only works in pages, component and mixin classes. To read or set session state objects in other classes, use the ApplicationStateManager service. Looks like i have to use the context, yes, that is why the EventContext stands for, but i don't understand why such a mechanism Are you asking why the page event context exists? and why i can't use SessionState You can, but there are better alternatives. or page injection. I'm not following you. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
PageRenderLinkTransformer, SessionState and InjectPage
Hi all, I m using the new PageRenderLinkTransformer thing, very helpful but, in the decodePageRenderRequest i would like to set up some things for others pages. I can do it either by injecting page and call the appropriate methods one those, or use a session state object. Unfortunately, the SessionState object does always result as null in the next pages. Injected pages are not injected as well, and throw NPE when calling the appropriate method on those. Looks like i have to use the context, yes, that is why the EventContext stands for, but i don't understand why such a mechanism and why i can't use SessionState or page injection. Thank you for you help. -- View this message in context: http://tapestry.1045711.n5.nabble.com/PageRenderLinkTransformer-SessionState-and-InjectPage-tp4811846p4811846.html Sent from the Tapestry - User 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
Re: Free Tapestry Laptop Stickers
Looks like they can be used on non-laptops, too ... :-) mrg On Thu, Sep 15, 2011 at 6:20 PM, Howard Lewis Ship wrote: > I just got in the second batch of Tapestry laptop stickers. Do you > want one? They're free --- all I ask is that you share your Tapestry > story (or tell me not too). Details on my blog: > > http://tapestryjava.blogspot.com/2011/08/tapestry-5-laptop-stickers.html > > For those who previously responded and are still waiting for them ... > I'll be getting a big batch of them out shortly! > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com > > - > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Alert box
That was a cut-and-paste from the component registry app I'm working
on (which I'm calling Unicorn). Otherwise it would have taken forever
to find all those. There are something like 275 components in the
database now. Need to get the darn thing done.
On Fri, Sep 16, 2011 at 1:26 PM, Kalle Korhonen
wrote:
> 10 points to Bob for a rather exhaustive answer!
>
> Kalle
>
>
> On Fri, Sep 16, 2011 at 3:41 AM, Bob Harner wrote:
>> There are a number of modal dialog components & mixins:
>>
>> Confirm, from Lombok, a JavaScript "confirm" pop-up prompt,
>> implemented as a mixin that you can attach to a PageLink or ActionLink
>> component. (docs:
>> http://wiki.apache.org/tapestry/Tapestry5AndJavaScriptExplained, demo:
>> http://lombok.demon.co.uk/tapestry5Demo/test/mixins/confirmdemo)
>>
>> Dialog, from Tapestry5-jQuery, a modal dialog box using jQuery Dialog.
>> The dialog window can be moved, resized and closed with the 'x' icon
>> (docs: http://tapestry5-jquery.com/docs/components/jquerydialog, demo:
>> http://jqueryui.com/demos/dialog/)
>>
>> Dialog, from Exanpe, a mixin that, when attached to an ActionLink or
>> PageLink, pops up a modal dialog box, with user interaction with the
>> rest of the page blocked until a choice is made (OK, OK/Cancel or
>> Yes/No). (docs:
>> http://exanpe.github.com/exanpe-t5-lib/reference.html#dialog, demo:
>> http://exanpe-t5-lib.appspot.com/components/dialog/example1)
>>
>> ModalBox, from Weaves, a modal dialog box based on the ModalBox
>> JavaScript library (docs:
>> http://intercommitweavesdemo.intercommit.cloudbees.net/modalboxdemo)
>>
>> ModalDialog, from Tapestry Magic, a modal dialog box using ModalBox
>> (from http://okonet.ru) (docs:
>> http://tawus.wordpress.com/2011/07/02/a-modal-dialog-for-tapestry/)
>>
>> Overlay, from Ioko-tapestry-commons, a pop-up div with shaded
>> background (docs: http://tapestry.ioko.com/tapestry-mixins/)
>>
>> PopupWindow, from Weaves, a modal dialog box based on the ModalBox
>> JavaScript library. (docs:
>> http://intercommitweavesdemo.intercommit.cloudbees.net/popupwindowdemo)
>>
>> Window, from Chenillekit, a modal (pop-up) window based on the
>> http://prototype-window.xilinus.com JavaScript window library. (docs:
>> http://www.chenillekit.org/chenillekit-tapestry/ref/org/chenillekit/tapestry/core/components/Window.html,
>> demo: http://www.chenillekit.org/demo/tapcomp/windowdemo)
>>
>> On Fri, Sep 16, 2011 at 6:08 AM, Steve Eynon
>> wrote:
>>> What extra functionality are looking for, above and beyond ye olde
>>> default JavaScript alert("!") ?
>>>
>>> There are alerts in T5.3 which render extra lines in your code (like
>>> validation errors but more generalised).
>>>
>>> Steve.
>>>
>>> On 16 September 2011 17:25, csckid wrote:
Is there any alert box(Pop up box) in tapestry? Can anyone please name one
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Alert-box-tp4810081p4810081.html
Sent from the Tapestry - User 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
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Alert box
10 points to Bob for a rather exhaustive answer!
Kalle
On Fri, Sep 16, 2011 at 3:41 AM, Bob Harner wrote:
> There are a number of modal dialog components & mixins:
>
> Confirm, from Lombok, a JavaScript "confirm" pop-up prompt,
> implemented as a mixin that you can attach to a PageLink or ActionLink
> component. (docs:
> http://wiki.apache.org/tapestry/Tapestry5AndJavaScriptExplained, demo:
> http://lombok.demon.co.uk/tapestry5Demo/test/mixins/confirmdemo)
>
> Dialog, from Tapestry5-jQuery, a modal dialog box using jQuery Dialog.
> The dialog window can be moved, resized and closed with the 'x' icon
> (docs: http://tapestry5-jquery.com/docs/components/jquerydialog, demo:
> http://jqueryui.com/demos/dialog/)
>
> Dialog, from Exanpe, a mixin that, when attached to an ActionLink or
> PageLink, pops up a modal dialog box, with user interaction with the
> rest of the page blocked until a choice is made (OK, OK/Cancel or
> Yes/No). (docs:
> http://exanpe.github.com/exanpe-t5-lib/reference.html#dialog, demo:
> http://exanpe-t5-lib.appspot.com/components/dialog/example1)
>
> ModalBox, from Weaves, a modal dialog box based on the ModalBox
> JavaScript library (docs:
> http://intercommitweavesdemo.intercommit.cloudbees.net/modalboxdemo)
>
> ModalDialog, from Tapestry Magic, a modal dialog box using ModalBox
> (from http://okonet.ru) (docs:
> http://tawus.wordpress.com/2011/07/02/a-modal-dialog-for-tapestry/)
>
> Overlay, from Ioko-tapestry-commons, a pop-up div with shaded
> background (docs: http://tapestry.ioko.com/tapestry-mixins/)
>
> PopupWindow, from Weaves, a modal dialog box based on the ModalBox
> JavaScript library. (docs:
> http://intercommitweavesdemo.intercommit.cloudbees.net/popupwindowdemo)
>
> Window, from Chenillekit, a modal (pop-up) window based on the
> http://prototype-window.xilinus.com JavaScript window library. (docs:
> http://www.chenillekit.org/chenillekit-tapestry/ref/org/chenillekit/tapestry/core/components/Window.html,
> demo: http://www.chenillekit.org/demo/tapcomp/windowdemo)
>
> On Fri, Sep 16, 2011 at 6:08 AM, Steve Eynon
> wrote:
>> What extra functionality are looking for, above and beyond ye olde
>> default JavaScript alert("!") ?
>>
>> There are alerts in T5.3 which render extra lines in your code (like
>> validation errors but more generalised).
>>
>> Steve.
>>
>> On 16 September 2011 17:25, csckid wrote:
>>> Is there any alert box(Pop up box) in tapestry? Can anyone please name one
>>>
>>> --
>>> View this message in context:
>>> http://tapestry.1045711.n5.nabble.com/Alert-box-tp4810081p4810081.html
>>> Sent from the Tapestry - User 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
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Grid "overrides" question
Hmm...so publishParameters in the container component? I'll give that a shot later today. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Grid-overrides-question-tp4807689p4811311.html Sent from the Tapestry - User 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
RE: outputting expression logic
Thanks Thiago... logically it makes sense... just trying to avoid code bloat in the java module and going for the short cut drill into the object at the tml level. I do think moving the logic to java will prompt the developer to make things more reasonably understandable by working in realistic operations that will be understood better in the tml file... anyway... getting closer... gallery widget pending ciao > To: users@tapestry.apache.org; kcola...@live.com > Subject: Re: outputting expression logic > Date: Fri, 16 Sep 2011 07:48:41 -0300 > From: thiag...@gmail.com > > On Thu, 15 Sep 2011 23:53:18 -0300, Ken in Nashua > wrote: > > > I guess I am asking for an ognl engine... to do these calculations > > within tml files > > Are you really sure you want to have logic in your template and make it > look like JSP (which sucks), as Steve said? Mixing output generation and > logic is a recipe for confusion. When I started working with T5 I've also > missed OGNL, but later I got used to it and I use almost just property > expressions exclusively since then. > > ChenilleKit has an OGNL binding. > > > be nice if there were an expression operator in T5 to do these... > > That's not going to happen. This was dropped from T5 on purpose. > > > guess I will have to make a java method... > > This is the canonical approach. Logic belongs in Java classes. > > It does seem to me that you're trying to write T5 thinking in T4 terms. I > don't advise you to do that. The main concepts are mostly the same, but > the implementation is very, very different. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br
Re: outputting expression logic
On Thu, 15 Sep 2011 23:53:18 -0300, Ken in Nashua wrote: I guess I am asking for an ognl engine... to do these calculations within tml files Are you really sure you want to have logic in your template and make it look like JSP (which sucks), as Steve said? Mixing output generation and logic is a recipe for confusion. When I started working with T5 I've also missed OGNL, but later I got used to it and I use almost just property expressions exclusively since then. ChenilleKit has an OGNL binding. be nice if there were an expression operator in T5 to do these... That's not going to happen. This was dropped from T5 on purpose. guess I will have to make a java method... This is the canonical approach. Logic belongs in Java classes. It does seem to me that you're trying to write T5 thinking in T4 terms. I don't advise you to do that. The main concepts are mostly the same, but the implementation is very, very different. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Alert box
There are a number of modal dialog components & mixins:
Confirm, from Lombok, a JavaScript "confirm" pop-up prompt,
implemented as a mixin that you can attach to a PageLink or ActionLink
component. (docs:
http://wiki.apache.org/tapestry/Tapestry5AndJavaScriptExplained, demo:
http://lombok.demon.co.uk/tapestry5Demo/test/mixins/confirmdemo)
Dialog, from Tapestry5-jQuery, a modal dialog box using jQuery Dialog.
The dialog window can be moved, resized and closed with the 'x' icon
(docs: http://tapestry5-jquery.com/docs/components/jquerydialog, demo:
http://jqueryui.com/demos/dialog/)
Dialog, from Exanpe, a mixin that, when attached to an ActionLink or
PageLink, pops up a modal dialog box, with user interaction with the
rest of the page blocked until a choice is made (OK, OK/Cancel or
Yes/No). (docs:
http://exanpe.github.com/exanpe-t5-lib/reference.html#dialog, demo:
http://exanpe-t5-lib.appspot.com/components/dialog/example1)
ModalBox, from Weaves, a modal dialog box based on the ModalBox
JavaScript library (docs:
http://intercommitweavesdemo.intercommit.cloudbees.net/modalboxdemo)
ModalDialog, from Tapestry Magic, a modal dialog box using ModalBox
(from http://okonet.ru) (docs:
http://tawus.wordpress.com/2011/07/02/a-modal-dialog-for-tapestry/)
Overlay, from Ioko-tapestry-commons, a pop-up div with shaded
background (docs: http://tapestry.ioko.com/tapestry-mixins/)
PopupWindow, from Weaves, a modal dialog box based on the ModalBox
JavaScript library. (docs:
http://intercommitweavesdemo.intercommit.cloudbees.net/popupwindowdemo)
Window, from Chenillekit, a modal (pop-up) window based on the
http://prototype-window.xilinus.com JavaScript window library. (docs:
http://www.chenillekit.org/chenillekit-tapestry/ref/org/chenillekit/tapestry/core/components/Window.html,
demo: http://www.chenillekit.org/demo/tapcomp/windowdemo)
On Fri, Sep 16, 2011 at 6:08 AM, Steve Eynon
wrote:
> What extra functionality are looking for, above and beyond ye olde
> default JavaScript alert("!") ?
>
> There are alerts in T5.3 which render extra lines in your code (like
> validation errors but more generalised).
>
> Steve.
>
> On 16 September 2011 17:25, csckid wrote:
>> Is there any alert box(Pop up box) in tapestry? Can anyone please name one
>>
>> --
>> View this message in context:
>> http://tapestry.1045711.n5.nabble.com/Alert-box-tp4810081p4810081.html
>> Sent from the Tapestry - User 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
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Alert box
What extra functionality are looking for, above and beyond ye olde
default JavaScript alert("!") ?
There are alerts in T5.3 which render extra lines in your code (like
validation errors but more generalised).
Steve.
On 16 September 2011 17:25, csckid wrote:
> Is there any alert box(Pop up box) in tapestry? Can anyone please name one
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Alert-box-tp4810081p4810081.html
> Sent from the Tapestry - User 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
>
>
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Grid "overrides" question
I'm not really sure, but I wonder if
@Component(publishParameters="...") would help anywhere?
Steve.
On 16 September 2011 01:43, cqasker wrote:
> So say I have a component that wraps a grid like:
>
> SomeGrid.tml
> http://tapestry.apache.org/schema/tapestry_5_1_0.xsd";
> xmlns:p="tapestry:parameter">
>
>
>
>
>
>
> SomeGrid.java
> @SuppressWarnings("unused")
> @Component(parameters={"overrides=prop:overrides", ...other params...})
> private Grid grid;
>
> @Parameter(value = "this", allowNull = false)
> @Property(write = false)
> private PropertyOverrides overrides;
>
> A component that contains SomeGrid.tml and it overrides a column:
> SomeGridContainer.tml
> http://tapestry.apache.org/schema/tapestry_5_1_0.xsd";
> xmlns:p="tapestry:parameter">
>
> test Some Grid Container
>
>
>
> SomeGridContainer.java
> @SuppressWarnings("unused")
> @Component(parameters={"overrides=prop:overrides", ...other params...})
> private SomeGrid grid;
>
> @Parameter(value = "this", allowNull = false)
> @Property(write = false)
> private PropertyOverrides overrides;
>
> A page that contains SomeGridContainer
> MyPage.tml
>
> test Page
>
>
>
> In SomeGrid and SomeGridContainer I have @SupportsInformalParameters and
> inject ComponentResources and pass in the overrides.
>
> in the Name column, "test Page" always shows. I then tried and removed
> p:nameCell from myPage.tml and column displayed whatever was in the name
> property of the current row. So it seems p:nameCell in SomeGridContainer is
> always ignored. Is this the right behavior? It would be nice if I can get
> around this since I can define column parameters in the container component
> and not have to redefine them in every page I use. And for cases where I
> want to override the ones in the container I can define them in the page.
> Anyways interesting behavior.
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Grid-overrides-question-tp4807689p4807689.html
> Sent from the Tapestry - User 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
>
>
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
