Re: button values

2006-11-22 Thread Peter Beshai
To: users@tapestry.apache.org Subject: Re: button values Date: Wed, 22 Nov 2006 14:01:15 + (UTC) any ideas why this would not work and I have to use ognl:messages. instead? TIA John - To unsubscribe, e-mail: [EMAIL PROTEC

Re: button values

2006-11-22 Thread John Coleman
any ideas why this would not work and I have to use ognl:messages. instead? TIA John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: button values

2006-11-22 Thread Ron Piterman
yes it is much better (faster) , and you can use it on each binding (formal and informal parameters). Cheers, Ron John Coleman wrote: > D&J Gredler gmail.com> writes: > I used the label attribute to supply i.e. label="ognl:messages.getMessage...". > > Can I use messages: anywhere,and drop ognl,

Re: button values

2006-11-22 Thread John Coleman
D&J Gredler gmail.com> writes: I used the label attribute to supply i.e. label="ognl:messages.getMessage...". Can I use messages: anywhere,and drop ognl, is that better? We use Tapestry 4.0 I think. regards, John - To unsubsc

Re: button values

2006-11-21 Thread D&J Gredler
value="message:display-summary-button" is a little better (shorter, no OGNL overhead), but still not what you're looking for... Maybe you could try to specify the binding in both the page spec and the page template, make the page spec the dynamic one, make the page template the static one, and ho

Re: Button values dont print

2006-09-28 Thread Jesse Kuhnert
AhSounds like a "browser" issue then ? ;) On 9/29/06, Peter Dawn <[EMAIL PROTECTED]> wrote: guys, the label bit works for tap3, i have used it in many places. and my HTML looks like this, but inspite of having the value bit, it doesnt print. i mean i can visually see it, but when i print

Re: Button values dont print

2006-09-28 Thread Peter Dawn
guys, the label bit works for tap3, i have used it in many places. and my HTML looks like this, but inspite of having the value bit, it doesnt print. i mean i can visually see it, but when i print it it doesnt work. will try and spend some more time on it over the weekend. ---

Re: Button values dont print

2006-09-28 Thread Jesse Kuhnert
You are missing a value="" attribute for some reason. Are you sure that the label="message:something" works for Tap3? I thought that was a hivemind only kind of feature in t4 > (not sure what it looks like in T5 exactly yet) On 9/28/06, Steve Shucker <[EMAIL PROTECTED]> wrote: I don't know if

Re: Button values dont print

2006-09-28 Thread Steve Shucker
I don't know if this will work, but you can try adding another stylesheet just for printing that will override the button's style. type="text/css" /> Then set the color or other attributes for buttonSpecial to be something different. It could be something as simple as the printer thinking it

Re: Button values dont print

2006-09-28 Thread Peter Dawn
dunno. i have done the right thing in tapestry, in the css and its still not working. if nobody else has this issue, then it must be my implementation, though i cant understand how difficult it could be. thanks anyways. - To uns

Re: Button values dont print

2006-09-28 Thread andyhot
so, it's not a tapestry issue, is it? Peter Dawn wrote: > the html is and in my css > I have, > .buttonSpecial { > font: #FF; > and the rest > } > > any ideas. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For addit

Re: Button values dont print

2006-09-28 Thread Peter Dawn
sorry i meant color: #FF; - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Button values dont print

2006-09-28 Thread Peter Dawn
the html is and in my css I have, .buttonSpecial { font: #FF; and the rest } any ideas. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Button values dont print

2006-09-28 Thread andyhot
What's the generated html? Perhaps its a css issue ? Peter Dawn wrote: > guys, > > i am using tap3. has anybody else noticed this, but everytime i print > a page which has a button on it, the buttons value does not print. the > button is a tap component with the value set as label="message:text" >