Re: Component factory producing components

["F. Da Costa Gomez" <dc...@fixed.com>]

It looks like the 'thing' that goes through the different columns does 
NOT switch to the oovCode columns for whatever reason.
Even after changing the columnNames of the oovCode cols there is no change.

Which part is responsible for walking through the cells/ rows and 
columns? Or maybe I have to look into something else??

Cheers,
Fermin


F. Da Costa Gomez wrote:

> I saw some html files were not accepted (???) but they basically are ok.
> I noticed that for 1 reason or another all the evaluators for the 
> oovCode columns are *replaced* by the units evaluator.
> In my test there are 19 rows and after 19 times the units evaluator it 
> just continued (that explains the stuff up whilst using multiple 
> different columns).
>
> Now just to track that 1 down.
>
> Just letting u know.
>
> Cheers,
> Fermin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
>

Re: Component factory producing components (beta1 is done)

["F. Da Costa Gomez" <dc...@fixed.com>]

Done!!!

It looks like the columnFactory is finally nearing its end.
The naming of the TableColumn and its relation to TableValues had me 
wrong-footed for quite a while.
Whilst working with the TableColumn I automatically assumed I also had a 
handle on the date. Wrrrongg.

I appreciate the two being segregated, no worries there but something 
like TableHeader/Definition might be more intuitive.

Never mind 4 now. It works & I'll clean up and do some more doccing and 
stick it on a post.
Have a look and lemme know.

Cheers,
Fermin DCG

Re: Component factory producing components (nearing conclusion?)

["F. Da Costa Gomez" <dc...@fixed.com>]

It goes through the proper column & cell count alright, it just does not 
change form the last column added to the model.
Its almost as if there is no "reset" of the columnModel. Could this be 
correct and if so how and where does one rectify this?

Cheers,
Fermin