Re: First Custom Component -> Confused; source = null, but values populated mysteriously
Are you sure you're not him? You do have pity on us fools though ;-) Look at all that Tapestry 'bling'. Sorry for off topic, but just to also say Thanks to Mr T for answering everyone's questions and generally being helpful. I'm still learning lots of stuff and more so from other users' questions. " If you have a problem...if no one else can help...and if you can find them...maybe you can hire...The T- Team." Regards Az On Tue, Apr 3, 2012 at 2:57 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > On Tue, 03 Apr 2012 10:06:38 -0300, Chris Mylonas > wrote: > > thanks again Mr T >> > > heheheh I don't look like him much, but I sometimes read some questions in > this mailing lists (fortunately, just a few) and think "what's this > jibber-jabber you're talking?", hehehe > > > tapestry could benefit from a "rosetta stone" of the equivalent methods >> of doing the same thing. >> > > That's a good documentation suggestions . . . JIRA please? :) Usually, > Tapestry avoids to provide more than one way of doing the same thing. On > the other hand, sometimes the Tapestry flexibility and architecture ends up > providing alternatives. > > > i've spent a few hours today templating my first component with >> MarkupWriter.element()/end(), writeRaw() and .tml files. >> Each have their strengths. >> > > Yep. Templates are generally easier to read and write, but MarkupWriter is > better when you have more complex logic and attributes that may or may not > be added. In addition, MarkupWriter supports recursion (it's just Java > code, after all), while templates don't. > > > -- > 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 > > --**--**- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
Re: First Custom Component -> Confused; source = null, but values populated mysteriously
>> tapestry could benefit from a "rosetta stone" of the equivalent methods of >> doing the same thing. > > That's a good documentation suggestions . . . JIRA please? :) Usually, > Tapestry avoids to provide more than one way of doing the same thing. On the > other hand, sometimes the Tapestry flexibility and architecture ends up > providing alternatives. Created fool! (MR T reference of course) https://issues.apache.org/jira/browse/TAP5-1894
Re: First Custom Component -> Confused; source = null, but values populated mysteriously
On Tue, 03 Apr 2012 10:06:38 -0300, Chris Mylonas wrote: thanks again Mr T heheheh I don't look like him much, but I sometimes read some questions in this mailing lists (fortunately, just a few) and think "what's this jibber-jabber you're talking?", hehehe tapestry could benefit from a "rosetta stone" of the equivalent methods of doing the same thing. That's a good documentation suggestions . . . JIRA please? :) Usually, Tapestry avoids to provide more than one way of doing the same thing. On the other hand, sometimes the Tapestry flexibility and architecture ends up providing alternatives. i've spent a few hours today templating my first component with MarkupWriter.element()/end(), writeRaw() and .tml files. Each have their strengths. Yep. Templates are generally easier to read and write, but MarkupWriter is better when you have more complex logic and attributes that may or may not be added. In addition, MarkupWriter supports recursion (it's just Java code, after all), while templates don't. -- 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 - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: First Custom Component -> Confused; source = null, but values populated mysteriously
thanks again Mr T
tapestry could benefit from a "rosetta stone" of the equivalent methods of
doing the same thing.
i've spent a few hours today templating my first component with
MarkupWriter.element()/end(), writeRaw() and .tml files.
Each have their strengths.
In this case
e.g.
VM arguments
-Dtapestry.production-mode=false -Dtapestry.compress-whitespace=false
VS
AppModule.contributeApplicationDefaults()
configuration.add("tapestry.production-mode", false);
configuration.add("tapestry.compress-whitespace", false) ;
I guess more of the same from here http://tapestry.apache.org/configuration.html
> On Tue, 03 Apr 2012 00:02:36 -0300, Chris Mylonas wrote:
>
>> That's awesome!!! Thanks a lot Thiago
>>
>> VM arguments for the unwashed are:
>> -Dtapestry.production-mode=false -Dtapestry.compress-whitespace=false
>
> You can use contributeApplicationDefaults() in your AppModule instead if you
> want.
>
Re: First Custom Component -> Confused; source = null, but values populated mysteriously
On Tue, 03 Apr 2012 00:02:36 -0300, Chris Mylonas wrote: That's awesome!!! Thanks a lot Thiago VM arguments for the unwashed are: -Dtapestry.production-mode=false -Dtapestry.compress-whitespace=false You can use contributeApplicationDefaults() in your AppModule instead if you want. -- 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 - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: First Custom Component -> Confused; source = null, but values populated mysteriously
That's awesome!!! Thanks a lot Thiago VM arguments for the unwashed are: -Dtapestry.production-mode=false -Dtapestry.compress-whitespace=false On 03/04/2012, at 12:36 PM, Thiago H. de Paula Figueiredo wrote: > On Mon, 02 Apr 2012 23:02:17 -0300, Chris Mylonas wrote: > >> Hello List, > > Hi! > >> When I changed my component's beginRender() on a whim to see if I get an >> exception, I was surprised to see the value that the Grid prints to the >> screen was available to my component - yet everything about it in the >> debugger says null - i.e. source = null, currentItem = null. > > Which version are you using? What's the value of the configuration symbol > tapestry.production-mode? Since some not-so-recent version, when not in > production mode, Tapestry updates the field values so they can be seen in the > debugger. > > -- > 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 - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: First Custom Component -> Confused; source = null, but values populated mysteriously
oh! sounds good. I'm using 5.3.2 and my production mode symbol is the default because I've been ignorant to all that sort of stuff in the past, now it's biting me back. On 03/04/2012, at 12:36 PM, Thiago H. de Paula Figueiredo wrote: > On Mon, 02 Apr 2012 23:02:17 -0300, Chris Mylonas wrote: > >> Hello List, > > Hi! > >> When I changed my component's beginRender() on a whim to see if I get an >> exception, I was surprised to see the value that the Grid prints to the >> screen was available to my component - yet everything about it in the >> debugger says null - i.e. source = null, currentItem = null. > > Which version are you using? What's the value of the configuration symbol > tapestry.production-mode? Since some not-so-recent version, when not in > production mode, Tapestry updates the field values so they can be seen in the > debugger. > > -- > 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 - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: First Custom Component -> Confused; source = null, but values populated mysteriously
On Mon, 02 Apr 2012 23:02:17 -0300, Chris Mylonas wrote: Hello List, Hi! When I changed my component's beginRender() on a whim to see if I get an exception, I was surprised to see the value that the Grid prints to the screen was available to my component - yet everything about it in the debugger says null - i.e. source = null, currentItem = null. Which version are you using? What's the value of the configuration symbol tapestry.production-mode? Since some not-so-recent version, when not in production mode, Tapestry updates the field values so they can be seen in the debugger. -- 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 - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
