Attribute sortable in grid

2010-09-27 Thread Cucchietti Denis
Hello everybody ! I have a little problem in my grid component. I want to offer the possibility to sort a column in my grid. The problem is that this column is not an attribute of my object. I have created a new attribute in my grid component like this : TML : table

Re: Attribute sortable in grid

2010-09-27 Thread Massimo Lusetti
On Mon, Sep 27, 2010 at 10:33 AM, Cucchietti Denis denis.cucchie...@atosorigin.com wrote: So, I've the icon that indicate that the column can be sort but it's don't work ! I would like can sort by Belong to or Combines. You should dig a little more, have a look at the griddatasource and start

Re: Attribute sortable in grid

2010-09-27 Thread Thiago H. de Paula Figueiredo
On Mon, 27 Sep 2010 05:33:35 -0300, Cucchietti Denis denis.cucchie...@atosorigin.com wrote: Hello everybody ! Hi! I have a little problem in my grid component. I want to offer the possibility to sort a column in my grid. The problem is that this column is not an attribute of my object.

RE: Attribute sortable in grid

2010-09-27 Thread Cucchietti Denis
Hi Thiago. First of all thanks for your response. I have tried with a property conduit but the problem is my new column is not an attribute of my object Structure so I don't know how to use it : PropertyConduit propCdtAttribute = this.propertyConduitSource.create(String.class, relation);

Re: Attribute sortable in grid

2010-09-27 Thread Thiago H. de Paula Figueiredo
On Mon, 27 Sep 2010 10:38:38 -0300, Cucchietti Denis denis.cucchie...@atosorigin.com wrote: Hi Thiago. Hi! I have tried with a property conduit but the problem is my new column is not an attribute of my object Structure so I don't know how to use it : PropertyConduit propCdtAttribute =

RE: Attribute sortable in grid

2010-09-27 Thread Cucchietti Denis
Thanks a lot Thiago its works Here the solution : In JAVA : @Property private ListStructure listOfParentStructures; private RelationPropertyConduit relationPropertyConduit; public BeanModelStructure getGridModel() { BeanModelStructure model =

Re: Attribute sortable in grid

2010-09-27 Thread Thiago H. de Paula Figueiredo
On Mon, 27 Sep 2010 11:35:00 -0300, Cucchietti Denis denis.cucchie...@atosorigin.com wrote: Thanks a lot Thiago its works You're welcome! model.add(relation, this.relationPropertyConduit).sortable(true); } I don't think you need to set it as sortable, as BeanModel

Dynamically setting tabindex for input elements in a component

2010-09-27 Thread Denis McCarthy
Hi I have a pretty large component that needs to appear in one of two places in a large form, depending on who's using the form. The dynamic placement I can do pretty easily using delegates. However, I'm struggling with the tabindex of the various input elements in the component. I want them to

Re: Dynamically setting tabindex for input elements in a component

2010-09-27 Thread Andreas Andreou
So, your component contains 70+ inputs and I guess it's included in pages more than once... If you're happy with the default taborder within one render of your component (and you don't need to manually tweak it), then just set the taborder in all your inputs to be the same number. And then, on the

Re: Dynamically setting tabindex for input elements in a component

2010-09-27 Thread Thiago H. de Paula Figueiredo
On Mon, 27 Sep 2010 14:09:18 -0300, Denis McCarthy dmccar...@annadaletech.com wrote: t:select t:id=country t:model=dummyModel t:value=country t:label=message:COUNTRY tabindex=${tabIndexStart + 1} / t:select t:id=country t:model=dummyModel t:value=country t:label=message:COUNTRY

Tapestry 5.2 bug?

2010-09-27 Thread Yunhua Sang
Hi everyone, I am using 5.2.1-SNAPSHOT. I found a new thread in page class has problem to access the persisted fields, for example: @Persist @Property private String field; public void onSubmit() { try { Thread thread = new Thread() { public

Re: Tapestry 5.2 bug?

2010-09-27 Thread Thiago H. de Paula Figueiredo
On Mon, 27 Sep 2010 16:47:38 -0300, Yunhua Sang yunhua.s...@gmail.com wrote: Hi everyone, Hi! The field is always null when printing it out within run method; a workaround is to define a local variable then access this variable in new thread.I am wondering whether it's an expected

Re: Tapestry 5.2 bug?

2010-09-27 Thread Yunhua Sang
Hi Thiago, Thanks for your response. Yes, the code looks not nice, however, there is nothing wrong with it. I knew there was a refactoring of changing pool to singleton recently, so I was able to come up with a workaround quickly, but for a Tapestry newbie, he/she might not know what's going on,

Re: Tapestry 5.2 bug?

2010-09-27 Thread Howard Lewis Ship
True, there are some leaky abstractions related to the new approach; there was a different set in the 5.1 version of the page lifecycle. I've never felt the need to start up a thread from the middle of a page. I'm curious what your use case is, and whether it wouldn't be better handled using

Re: Tapestry 5.2 bug?

2010-09-27 Thread Yunhua Sang
I am using PipedInputStream and PipedOutputStream to convert a large OutputStream to StreamResponse, that needs a new thread. For me, there is no problem with the new approach, just want framework which is already very great to be perfect. Yunhua On Mon, Sep 27, 2010 at 4:57 PM, Howard Lewis