value. You need label, image, and value.
> >>
> >> I think your best bet is to copy OptionModel and Select to new classes
> and
> >> and modify them suit your purposes. They aren’t long or complicated.
> >>
> >> HTH,
> >>
> >> Geo
r complicated.
HTH,
Geoff
On 15 Nov 2018, at 1:30 pm, D. R.
wrote:
Hi,
how can i get control of the option elements within a t:select?
I want to provide a unique data-icon property for each option.
t:model="literal:fa-globe=Globe,fa-flask=Flask,fa-user-tie=User-tie">
wi
, D. R.
> wrote:
> >
> > Hi,
> >
> > how can i get control of the option elements within a t:select?
> >
> > I want to provide a unique data-icon property for each option.
> >
> > t:model="literal:fa-globe=Globe,fa-flask=Flask,fa-us
value.
I think your best bet is to copy OptionModel and Select to new classes and and
modify them suit your purposes. They aren’t long or complicated.
HTH,
Geoff
> On 15 Nov 2018, at 1:30 pm, D. R. wrote:
>
> Hi,
>
> how can i get control of the option elements within a t:selec
Hi,
how can i get control of the option elements within a t:select?
I want to provide a unique data-icon property for each option.
t:model="literal:fa-globe=Globe,fa-flask=Flask,fa-user-tie=User-tie">
will render:
Globe
Flask
User-tie
i need something like
If you are generating a placeholder serverside and replacing it clientside,
there's no need to use a request parameter. You can just use the event
context.
You only need a request parameter when appending to the URL in javascript
rather than replacing a token.
Note that if you have ValueEncoders
});
Cheers,
Ben.
> Date: Wed, 21 Aug 2013 18:26:37 +0100
> Subject: RE: Submitting id & value of a t:select component onChange
> From: lance.j...@googlemail.com
> To: users@tapestry.apache.org
>
> You'll need to append a request parameter to a serverside generated event
> url and use @RequestParam serverside to get the value in the event
You'll need to append a request parameter to a serverside generated event
url and use @RequestParam serverside to get the value in the event
ComponentResourcesCommon.html#createEventLink%28java.lang.String,%20java.lang.Object...%29).
However at the time I would generate this link I don't have the value of the
field (the second context param) so how can I generate the whole URL like you
describe?
> Date: Wed,
1. You should not generate your URL's clientside. Instead, generate via
ComponentResources serverside and add a "data-url" attribute instead.
2. When I look at the tapestry-jquery page here
http://tapestry5-jquery.com/mixins/docsbind
I can see an include for bind.js (
http://tapestry5-jquery.com
request.done(function (response, textStatus, jqXHR){
$("#savingUpdate").hide();
});
});
> Date: Wed, 21 Aug 2013 15:55:06 +0100
> Subject: Re: Submitting id & value of a t:select component
tapestry-jquery has rewritten Tapestry's javascript and I'm not too
familiar with it. I'm sure there's a function in there to trigger a zone
update.
On 21 Aug 2013 15:26, "Lance Java" wrote:
> You could use data attributes and some clientside jquery just like a
> non-tapestry app.
>
> TML
>
>
: Re: Submitting id & value of a t:select component onChange
> From: lance.j...@googlemail.com
> To: users@tapestry.apache.org
>
> You could use data attributes and some clientside jquery just like a
> non-tapestry app.
>
> TML
>
> />
>
>
You could use data attributes and some clientside jquery just like a
non-tapestry app.
TML
JS
$("#myGrid").find("select").change(function() {
var select = $(this);
var foo = select.data("foo");
var bar = select.data("bar");
doStuff(foo, bar);
};
I have a Tapestry Grid component with three columns. Each cell contains a
select component that I want to submit their id and value via Ajax when the
value changes. The id isn't the client side component id but rather an id that
the server uses to lookup and save the value that has changed.
I
the example shown were loaded during onEvent, assume that i can get the
image loaded with inputstream and return as StreamResponse; upon changing
selection as this for my t:select component
@InjectComponent private Zone showPictureZone;
@OnEvent(value=EventConstants.VALUE_CHANGED,component
There's two options, both listed here
http://stackoverflow.com/questions/16914673/serve-images-outside-web-application
Be warned that using a local directory has issues with security,
portability, transactions, clustering and thread safety. You might want to
consider using a database or Amazon s3
hi,
currently i have a folder reside in C:\\mypic to store all the pictures.
my tapestry page has a t:select bound to the event and zone update. when
i select option in t:select, based on the value of the option i need to
load the picture from C:\\mypic directory. the problem is this pictures
hi,
currently i have a folder reside in C:\\mypic to store all the
pictures. my tapestry page has a t:select bound to the event and zone
update. when i select option in t:select, based on the value of the
option i need to load the picture from C:\\mypic directory. the
problem is this
It seams that your *add="descriptionCreator" + * is
right way.
Now is everything OK.
Thank you very much for help and for fast replay.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Forms-tp2427184p5713583.html
Sent from the Tapestry - User mailing list archive at Nabble.c
I do that in this way:
2012/6/1 stipenovi
> Can anyone help me:
>
> I have 2 entities: Description and Person with unidirectional ManyToOne
> mapped relationship.
> Every description must have descriptionCreator (Person).
>
> I have this code in tml:
>
>
>
Can anyone help me:
I have 2 entities: Description and Person with unidirectional ManyToOne
mapped relationship.
Every description must have descriptionCreator (Person).
I have this code in tml:
I injected SelectModelFactory, and have SelectModel as @Property in page
class. I also created Per
Ok, Vangel, thanks. Problem solved!
I`m going to move on to your proposition of using t:selectObject. In the
event of me getting stuck :] I`ll post the problems on a new thread.
Thank you for the help. I greatly appreciated it.
Eric Torti
On Sun, Aug 7, 2011 at 8:38 AM, Vangel V. Ajanovski wro
On 08/07/2011 06:31 AM, Eric Torti wrote:
...
You have to use the "add" parameter in beaneditform for each manytoone
property, and then use to wrap the select (or any other
custom html to be shown for this property.
Just copy the structure from my example and change selectobject wit
Thanks again, Vangel!
I`m trying the simplest approach as described on the docs page (the choosing
colors example). But when the page renders, the form is displayed without
the select element.
If you could please have a look at my code, I`ll provide it here. I`ve kept
the domain in portuguese (my
On 08/06/2011 04:46 PM, Eric Torti wrote:
The only doubt I still have is whether the tag is
supposed to work nested inside the tag.
The bean model does not automatically create fields for the ManyToOne
links, so they are not like standard part of the BeanEditForm, but I
"add" virtual fields f
, Aug 6, 2011 at 11:01 AM, Vangel V. Ajanovski wrote:
> On 08/06/2011 02:54 PM, Eric Torti wrote:
>
>> Thank you, based2.
>>
>> I am following the jumpstart examples. But in my case, the property I need
>> to choose from a t:select is not an enum. It`s a complex typ
On 08/06/2011 02:54 PM, Eric Torti wrote:
Thank you, based2.
I am following the jumpstart examples. But in my case, the property I need
to choose from a t:select is not an enum. It`s a complex type.
Official documentation has the easiest way if your situation is not very
complex.
https
Thank you, based2.
I am following the jumpstart examples. But in my case, the property I need
to choose from a t:select is not an enum. It`s a complex type.
The t:beaneditform should generate the select all by itself?
Thanks
Eric
On Sat, Aug 6, 2011 at 4:44 AM, based2 wrote:
>
>
http://jumpstart.doublenegative.com.au/jumpstart/examples/input/morecontroledit1/1
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-using-t-select-nested-inside-beaneditform-tp4671749p4671987.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
Hello, guys,
I`m struggling to get a beaneditform to show a t:select element.
I`ve accomplished the creation of the GenericSelectModel but I
don`t know if I`m on the right track. My template reads as follows:
The form is displayed but no is rendered.
Is this the right
Worked perfectly. Thanks
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/No-context-for-a-t-select-tp3398655p4556553.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe,
Here's mine:
@Log
void onChange(String primary, String secondary, String categoryName)
{
And what it does:
2011-07-05 16:52:07,899 [qtp1317701801-91] DEBUG -[ENTER]
onChange("e1718719-df6e-4bc4-a25d-4b7c83b0baae",
"7486318b-3f15-4735-be78-0d42ec778e1b", "category1")
--
View this message in
Hi lltyk, thanks for the reply.
I'm using your suggestion as followed and it only passes back the select
menu option id and ignors my context parameters. Any suggestions? Thanks.
Object onNewFundingChanged() {
String newFunding = request.getPara
I have something like that floating in my code. Doesn't have to be
selectobject and could be a plain select, but you need zoneupdater.
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/No-context-for-a-t-select-tp6060602p6551150.html
Sent from the Tapestry
Hi Richard, do you know if there has been any progress made on this feature?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/No-context-for-a-t-select-tp3398655p4553978.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
Hi Thiago. Do you know if this issue has been resolved? I have multiple
select menus in a grid using onValueChanged that all control a single ajax
popup form. I need to pass the row id into the form.
Thanks in advance!
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/No-co
see jira:
https://issues.apache.org/jira/browse/TAP5-1452
On 22/02/2011 9:51 PM, Thiago H. de Paula Figueiredo wrote:
On Tue, 22 Feb 2011 07:18:08 -0300, Paul Stanton
wrote:
thiago, is this how it's supposed to work?
What exactly?
---
;) ya sorry, I meant implementation !
On Feb 26, 2011 7:12 AM, "Thiago H. de Paula Figueiredo"
wrote:
> On Sat, 26 Feb 2011 10:12:40 -0300, Andreas Andreou
> wrote:
>
>> On Fri, Feb 25, 2011 at 20:23, Josh Canfield
>> wrote:
They wouldn't see the difference - they'd be using the component t
On Sat, 26 Feb 2011 10:12:40 -0300, Andreas Andreou
wrote:
On Fri, Feb 25, 2011 at 20:23, Josh Canfield
wrote:
They wouldn't see the difference - they'd be using the component that
would internally
use the mixin
Actually, I wasn't thinking of an internal mixin. Putting a "zone" on
the Se
On Fri, Feb 25, 2011 at 20:23, Josh Canfield wrote:
>> They wouldn't see the difference - they'd be using the component that
>> would internally
>> use the mixin
>
> Actually, I wasn't thinking of an internal mixin. Putting a "zone" on
> the Select seems random, making it an internal mixin doesn't
ou choose a value to be sent back to the
server.
Josh
On Fri, Feb 25, 2011 at 4:16 AM, Richard Hill wrote:
> On Thu, 2011-02-24 at 11:12 -0800, Josh Canfield wrote:
>> > Yes agreed - I think t:select should take an optional context parameter.
>>
>> I guess it's a
nt-mixins.html in the section
> "Implementation Mixins" for how this can work and why it's not *yet*
> possible to build this!
>
>
>>>
>>> Josh
>>>
>>> On Thu, Feb 24, 2011 at 8:49 AM, Richard Hill wrote:
>>> >
>>> >
n Mixins" for how this can work and why it's not *yet*
possible to build this!
>>
>> Josh
>>
>> On Thu, Feb 24, 2011 at 8:49 AM, Richard Hill wrote:
>> >
>> > Yes agreed - I think t:select should take an optional context parameter.
>> >
On Thu, 2011-02-24 at 11:12 -0800, Josh Canfield wrote:
> > Yes agreed - I think t:select should take an optional context parameter.
>
> I guess it's a little late to second guess the wisdom of adding a
> "zone" parameter to the Select component in the first place.
On Thu, 24 Feb 2011 18:19:39 -0300, Andreas Andreou
wrote:
That's exactly why i asked the question about implementation
mixins in the dev list ( http://markmail.org/thread/ft755d4vbkfaip4v )
Cool!
And there's no reason to restict it to onchange events - anyway, i'll
open some related jira
Canfield wrote:
>> Yes agreed - I think t:select should take an optional context parameter.
>
> I guess it's a little late to second guess the wisdom of adding a
> "zone" parameter to the Select component in the first place... I
> hadn't noticed it until now. Thi
On Thu, 24 Feb 2011 16:12:10 -0300, Josh Canfield
wrote:
Yes agreed - I think t:select should take an optional context parameter.
I guess it's a little late to second guess the wisdom of adding a
"zone" parameter to the Select component in the first place... I
hadn't
> Yes agreed - I think t:select should take an optional context parameter.
I guess it's a little late to second guess the wisdom of adding a
"zone" parameter to the Select component in the first place... I
hadn't noticed it until now. This functionality could have been
Yes agreed - I think t:select should take an optional context parameter.
I will file a JIRA.
As a work around I see two options:
1) In my case here I don't need to actually re-render a zone when the
user changes the selection. So I will probably just render the select
"manually"
On Thu, 24 Feb 2011 13:15:51 -0300, Richard Hill
wrote:
Thanks for this. I think I understand better what ValueEncoder does now.
However, this doesn't answer my question: when I say "context" I mean
the loop context - not the option value that was selected. This I know
how to get, but I don't
Feb 2011 11:58:26 -0300, Richard Hill
> wrote:
>
> > Hi - again :)
>
> Hi!
>
> > I am supplying select and option models, which seem to work fine. But
> > how how do I supply a context? The t:select component does not appear to
> > take one. Without this
> On Thu, 24 Feb 2011 11:58:26 -0300, Richard Hill
> wrote:
>
> > Hi - again :)
>
> Hi!
>
> > I am supplying select and option models, which seem to work fine. But
> > how how do I supply a context? The t:select component does not appear to
> > take on
On Thu, 24 Feb 2011 11:58:26 -0300, Richard Hill
wrote:
Hi - again :)
Hi!
I am supplying select and option models, which seem to work fine. But
how how do I supply a context? The t:select component does not appear to
take one. Without this I cannot know to what object my state change
context? The t:select component does not appear to
take one. Without this I cannot know to what object my state change
relates.
I've looked at valueencoders, but according to the docs, and from what
Thiago said yesterday, this seems to be alternative approach to using
models, which doesn
On Tue, 22 Feb 2011 07:18:08 -0300, Paul Stanton
wrote:
thiago, is this how it's supposed to work?
What exactly?
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
htt
Hi all,
Hi!
A hypothetical:
I have 2 separate entities, each with a 'Type' enum with different
options.
Both of these are used in multiple components by t:select input
fields.
How do I provide my 'translations' in my 'application message
catalog' so that they
urn messages.get(name);
return toUserPresentable(name.toLowerCase());
}
On 31/01/2011 11:38 AM, Thiago H. de Paula Figueiredo wrote:
On Sun, 30 Jan 2011 21:21:37 -0200, Paul Stanton
wrote:
Hi all,
Hi!
A hypothetical:
I have 2 separate entities, each with a 'Type' enum
Hi!
A hypothetical:
I have 2 separate entities, each with a 'Type' enum with different
options.
Both of these are used in multiple components by t:select input fields.
How do I provide my 'translations' in my 'application message
catalog' so that they do not conflict?
ul Stanton
wrote:
Hi all,
Hi!
A hypothetical:
I have 2 separate entities, each with a 'Type' enum with different
options.
Both of these are used in multiple components by t:select input fields.
How do I provide my 'translations' in my 'application message
catalog
On Sun, 30 Jan 2011 21:21:37 -0200, Paul Stanton
wrote:
Hi all,
Hi!
A hypothetical:
I have 2 separate entities, each with a 'Type' enum with different
options.
Both of these are used in multiple components by t:select input fields.
How do I provide my 'translations'
Hi all,
A hypothetical:
I have 2 separate entities, each with a 'Type' enum with different options.
Both of these are used in multiple components by t:select input fields.
How do I provide my 'translations' in my 'application message catalog'
A more general purpose way to trigger an AJAX zone update is to
include an empty t:form (with style="display:none") and the do $
('myFormId').submit() from any JavaScript method you'd create that
needs to trigger an event. Somewhat of a hack, but I've been using
this a lot for many different
I have saw the solutions but is not the same as
@EventListener
solution from chenillekit.org is not universal, need javascript
programming for every situation and not contain submitForm = "form",
validateForm = false
more universals
http://tinybits.blogspot.com/
with zone update but it much sim
This has been asked several times in the last weeks.
U can use chenillikit's onEvent mixin:
http://www.chenillekit.org/chenillekit-tapestry/ref/org/chenillekit/tapestry/core/mixins/OnEvent.html
or do something like: http://tinybits.blogspot.com/
2009/8/19 Sergey Kashin :
> Hello!
>
> In tapestry 4
Hello!
In tapestry 4.1 I can create ajax request from select component a very
simple way:
@EventListener(elements = "city", events = "onchange", submitForm = "form",
validateForm = false)
public void citySelected(IRequestCycle cycle) {
.
cycle.getResponseBuilder().updateComponent("zip");
On Thu, Jul 9, 2009 at 4:15 AM, Martin
Strand wrote:
> To fix your problem, put this in the message catalog (YourPage.properties):
You can also put them in the global message catalog (app.properties).
> oms = OMS
> payment = Payment
You can also use Team.oms (the class name before the enum value
, Balduran Bu wrote:
> Hello,
>
>
>
> When t:Select component generates option labels for enums, the
> toString() method is not honored at all. It currently generates both
> labels and values based on Enum.name() method. In my understanding, the
> labels shall be generated ba
Hello,
When t:Select component generates option labels for enums, the
toString() method is not honored at all. It currently generates both
labels and values based on Enum.name() method. In my understanding, the
labels shall be generated based on toString() method instead.
Here is a piece
Em Tue, 20 Jan 2009 12:20:00 -0300, luther.baker
escreveu:
Is there also a way to apply unique CSS to this first option as well?
That's why the OptionModel.getAttributes() method exists
(http://tapestry.apache.org/tapestry5/tapestry-core/apidocs/org/apache/tapestry/OptionModel.html#getAtt
Is there also a way to apply unique CSS to this first option as well?
-Luther
Thiago HP wrote:
>
> Em Mon, 19 Jan 2009 21:23:45 -0300, luther.baker
> escreveu:
>
>> Now concerning, the first or *blank*value - I'd like to replace it with
>> some text like "... choose one".
>
> Try the
Whoa nice. I missed the blankLabel parameter.
Gracias Thiago - thanks for being such an active member here.
-Luther
On Jan 19, 2009, at 7:41 PM, Thiago H. de Paula Figueiredo wrote:
Em Mon, 19 Jan 2009 21:23:45 -0300, luther.baker > escreveu:
Now concerning, the first or *blank*value - I'd
Em Mon, 19 Jan 2009 21:23:45 -0300, luther.baker
escreveu:
Now concerning, the first or *blank*value - I'd like to replace it with
some text like "... choose one".
Try the blankLabel parameter:
http://tapestry.apache.org/tapestry5/tapestry-core/ref/org/apache/tapestry5/corelib/components
I would like to display an html select drop down based on an enum ... works
perfectly.
Now concerning, the first or *blank*value - I'd like to replace it with some
text like "... choose one".
So, if using , is there a way I can add an option
... and make sure it shows up at the top of the select
so that I don't feel like I am being made to suffer (just
> like I used to in struts)
>
> Cheers
> Russell
>
> -Original Message-
> From: Kristian Marinkovic [mailto:[EMAIL PROTECTED]
> Sent: Tue 9/30/2008 2:55 PM
> To: Tapestry users
> Subject: Re: T5: t:s
ng made to suffer (just like I used to in struts)
Cheers
Russell
-Original Message-
From: Kristian Marinkovic [mailto:[EMAIL PROTECTED]
Sent: Tue 9/30/2008 2:55 PM
To: Tapestry users
Subject: Re: T5: t:select how to disable and re-enable
it is not enough to enable the select box only on
g,
kris
Andy Pahne <[EMAIL PROTECTED]>
30.09.2008 15:45
Bitte antworten an
"Tapestry users"
An
Tapestry users
Kopie
Thema
Re: T5: t:select how to disable and re-enable
Maybe it's possible that you disable your select only clientside?
If you do so there won
>Maybe it's possible that you disable your select only clientside?
>If you do so there won't be any problems if you later on enable it again.
.
>Andy
Thanks Andy: like I said
>> Thanks in advance for your ideas, I have resorted to adding a little
>> javascript that sets it so on load but tha
Maybe it's possible that you disable your select only clientside?
If you do so there won't be any problems if you later on enable it again.
Andy
Russell Brown schrieb:
Hi,
I am using a T5 select component. When the form renders I wish the select to be disabled so I use disabled="true" paramet
Hi,
I am using a T5 select component. When the form renders I wish the select to be
disabled so I use disabled="true" parameter. However, some javascript causes
the field to become enabled. If this happens however the value selected does
not get sent into the property of the component. I am ass
80 matches
Mail list logo