(Sh... I didn't reply to the list - Sorry T, inbox flooding)
HI Lance & Thiago,
>
Guys - thanks for sorting out my train of thought. It's now a shame that
I'm driving 1000km to get somewhere for some hands on work on a boat I'm
refitting getting my amateur boat building skills up and won't be able to
muck around with tapestry for a few days to see my programming project
move along :(
>
As an aside, I was thinking to put the tapestry unicorn on the bow on both
port and starboard, but the stickers aren't big enough! Howard, I need a 2
foot-by-2-foot waterproof sticker! 2 of them! It would be a great
insignia for *Arakis*.
>
The problem was:
>
1) I totally forgot about the static structure principal. And the way I'd
summarise it is that if you think of the components as being atomic (in the
chemistry sense), when it comes time to build the page you are given the
logical constructs (e.g. If, Loop) to build your page (again, like
chemistry in the real world).
>
2) A bit of a problem of "wow, this is new and even handier" - I'd
already built my component earlier in the week and was exploring other
methods of doing the stuff - i.e. the javascript stuff. It appears that
tapestry5-jquery has (totally) done all of the "javascript" lifting for me
- e.g. draggable/droppable and other notifications. WIth this discovery, I
wasn't thinking like a seasoned tapestry progammer :)
>
The Loop is what I want for the list of stuff in relation to the way
tapestry5-jquery already has a "draggable" component available and is
easily used in a template (.tml) - I was again not thinking as a web dev -
i.e. imagining a list of 100 items rather than 6 - but this is something to
muck around with CSS classes for the layout :)
>
Gratefully,
> Chris
>
>
> On Thu, Apr 5, 2012 at 9:11 PM, Thiago H. de Paula Figueiredo <
> thiag...@gmail.com> wrote:
>
>> On Wed, 04 Apr 2012 23:38:47 -0300, Chris Mylonas <ch...@opencsta.org>
>> wrote:
>>
>> Hi All,
>>>
>>
>> Hi!
>>
>> Why don't you just write a component for rendering that part? In
>> addition, think of blocks and the Delegate component. Better yet, take a
>> look at how BeanEditor and the other BeanModel-based components.
>>
>>
>> for( int i = 0 ; i < listOfDraggables.length ; i++){
>>> writer.element(org.got5.**tapestry5-jquery.components.**Draggable,
>>> "t:id", "chris");
>>>
>>
>> This would be dynamic structure and Tapestry doesn't support that nor it
>> ever will.
>>
>> --
>> Thiago H. de Paula Figueiredo
>> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
>> and instructor
>> Owner, Ars Machina Tecnologia da Informação Ltda.
>> http://www.arsmachina.com.br
>>
>
>
