is for making this simpler, it'd be nice if it came
> with Tapestry by default.
>
> --
> View this message in context:
> http://tapestry-users.832.n2.nabble.com/Simpler-Select-configuration-tp6421890p6444986.html
> Sent from the Tapestry User
Whatever the solution is for making this simpler, it'd be nice if it came
with Tapestry by default.
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/Simpler-Select-configuration-tp6421890p6444986.html
Sent from the Tapestry Users mailing list archive at Nabbl
Followed your lead
http://tawus.wordpress.com/2011/06/06/a-simpler-select-for-tapestry/
regards
Taha
On Sat, Jun 4, 2011 at 5:56 AM, Howard Lewis Ship wrote:
> A reminder: org.apache.tapestry5.components.Select is not the only
> class allowed to render a or tag. Rather than
> bending code me
A reminder: org.apache.tapestry5.components.Select is not the only
class allowed to render a or tag. Rather than
bending code ment for one purpose too far, why not think in terms of a
family of components that do similar things, but are applicable to
different situations?
On Fri, Jun 3, 2011 at
Wrote a post about it.
http://tawus.wordpress.com/2011/06/04/tapestry-magic-14-easy-selection/
and if you find it useful I can add it to the wiki.
regards
Taha
On Fri, Jun 3, 2011 at 8:54 PM, Taha Hafeez wrote:
> I use a configuration, which is similar to the one suggested by inge. The
> usag
I use a configuration, which is similar to the one suggested by inge. The
usage is
@InjectSelectSupport(type = User.class, label = "${name}(${address})", index
= "id")
private List users;
Using a class transformation, it introduces a method
public SelectSupport getUsersSupport();
in the compon
I would prefer to see something more familiar-looking:
${oneItem.name}
Not sure how possible that is. But it sure would be a lot more
flexible, and a lot easier for newbies to understand.
On Fri, Jun 3, 2011 at 7:38 AM, Thiago H. de Paula Figueiredo
wrote:
> On Fri, 03 Jun 2011 08:22:13
On Fri, 03 Jun 2011 08:22:13 -0300, LLTYK wrote:
How about a shorthand for selectmodelfactory calls. Something like
This could (or should) be implemented as a binding prefix.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and ins
How about a shorthand for selectmodelfactory calls. Something like
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/Simpler-Select-configuration-tp6421890p6434883.html
Sent from the Tapestry Users mailing list archive at Nabble.com
> That is, if you provide a property of type List for the "model"
You can also return a map with label and value which is much more useful for
database objects.
On Jun 1, 2011 6:08 PM, "Bob Harner" wrote:
> Inge,
>
> Interesting ideas. I agree that it would be nice to have a SelectModel
> created
Inge,
Interesting ideas. I agree that it would be nice to have a SelectModel
created automatically from the parameters passed to the Select
component. In fact, Select can do this already, with some limitations.
That is, if you provide a property of type List for the "model"
parameter (and don't pr
Hi!
In my new job I've worked a lot with Swing GUI code. I immediately saw the
strong need for a framework, in order to provide better abstractions, events
and data binding between GUI and the model layer. The framework market for
Swing applications is very close to dead, but I found a decent dead
12 matches
Mail list logo
