Re: Jquery Tooltip on production mode
Looks very similar to this: http://tapestry.1045711.n5.nabble.com/Problem-in-Production-mode-td5718120.html -- View this message in context: http://tapestry.1045711.n5.nabble.com/Jquery-Tooltip-on-production-mode-tp5718174p5718183.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Which phase of page lifecycle will not occur when we access page 2nd time?
I seem to be explaining this concept a bit lately... perhaps the tapestry docs need to include an explanation. Tapestry pages are singletons. Tapestry does a bit of byte code magic on your pages and components to transform them so that any request specific state is stored in a thread local map. In production mode, the member variables in your component classes are not used. In development mode, tapestry mirrors the thread local values to the component class fields to make debugging easier. http://tapestryjava.blogspot.co.uk/2010/07/everyone-out-of-pool-tapestry-goes.html -- View this message in context: http://tapestry.1045711.n5.nabble.com/Which-phase-of-page-lifecycle-will-not-occur-when-we-access-page-2nd-time-tp5718142p5718184.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Which phase of page lifecycle will not occur when we access page 2nd time?
On Thu, 22 Nov 2012 05:45:10 -0200, Muhammad Gelbana m.gelb...@gmail.com wrote: So now with 5.3.6, since pooling is disabled, is it a single page instance for each request? Yes. And how does it differ from the activation context event if they are both executed when the page is first loaded ? That's a completely different thing. The singletonness of Tapestry 5.2+ is about fields and the activation context is about invoking an event handler method. My *guess* is that tapestry loads the page for the first time (@PageLoaded), Correct. attaches it to the client's session (that is created by default) That's not correct. Tapestry doesn't create an user session by default. It's created when needed (a write to the session). In addition, page instances aren't attached to sessions. I guess you're talking about the per-thread map used to store the field values. If yes, then you were correct, just used the wrong words. :) and then executes the ActivationContext even whenever a request is made to the page, am I correct ? Correct. -- Thiago H. de Paula Figueiredo - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Which phase of page lifecycle will not occur when we access page 2nd time?
onActivate() is NOT always called. See http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/whatiscalledandwhen . Geoff On 22/11/2012, at 9:36 PM, Thiago H de Paula Figueiredo wrote: On Thu, 22 Nov 2012 05:45:10 -0200, Muhammad Gelbana m.gelb...@gmail.com wrote: So now with 5.3.6, since pooling is disabled, is it a single page instance for each request? Yes. And how does it differ from the activation context event if they are both executed when the page is first loaded ? That's a completely different thing. The singletonness of Tapestry 5.2+ is about fields and the activation context is about invoking an event handler method. My *guess* is that tapestry loads the page for the first time (@PageLoaded), Correct. attaches it to the client's session (that is created by default) That's not correct. Tapestry doesn't create an user session by default. It's created when needed (a write to the session). In addition, page instances aren't attached to sessions. I guess you're talking about the per-thread map used to store the field values. If yes, then you were correct, just used the wrong words. :) and then executes the ActivationContext even whenever a request is made to the page, am I correct ? Correct. -- Thiago H. de Paula Figueiredo - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: How to reuse a form?
So am I doing it this way? t:if test=isSelectDrowdownToBeShown t:delegate to=selectBlock / /t:if t:block t:id=selectBlock t:select .../ /t:block Is this the proper way of using blocks for my need in Q2? -- View this message in context: http://tapestry.1045711.n5.nabble.com/How-to-reuse-a-form-tp5718166p5718187.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: How to reuse a form?
On Thu, 22 Nov 2012 09:09:53 -0200, membersound memberso...@web.de wrote: So am I doing it this way? t:if test=isSelectDrowdownToBeShown t:delegate to=selectBlock / /t:if t:block t:id=selectBlock t:select .../ /t:block Is this the proper way of using blocks for my need in Q2? Nope if you want to add stuff to your form when using the component your created. You don't need blocks for just using the If component in the way you used above. One example, not tested: In the component class: @Parameter(defaultPrefix = BindingConstants.LITERAL) @Property private Block additionalStuff; In the component template: t:form ... t:delegate to=additionalStuff/ ... /t:form Usage: t:thecomponentyoucreatedwiththeforminside p:additionalStuff anything you want /p:additionalStuff /t:thecomponentyoucreatedwiththeforminside -- Thiago H. de Paula Figueiredo - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: How to reuse a form?
In addition to Thiago's suggestion, I often set a default for the block: @Parameter(value=block:defaultAdditionalStuff, defaultPrefix = BindingConstants.LITERAL) @Property private Block additionalStuff; t:form ... t:delegate to=additionalStuff/ ... /t:form t:block t:id=defaultAdditionalStuff Only show this when an additionalStuff parameter has not been supplied /t:block -- View this message in context: http://tapestry.1045711.n5.nabble.com/How-to-reuse-a-form-tp5718166p5718189.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Jquery Tooltip on production mode
Hi Ernesto, Are you developing a full jQuery Application or a Prototype+jQuery one ? Manu 2012/11/22 ICE Ernesto Arteaga Zavala arterza...@gmail.com Hi, Seems to be other problem. I disabled the YUI and doesn't work.. 2012/11/22 Lance Java lance.j...@googlemail.com Looks very similar to this: http://tapestry.1045711.n5.nabble.com/Problem-in-Production-mode-td5718120.html -- View this message in context: http://tapestry.1045711.n5.nabble.com/Jquery-Tooltip-on-production-mode-tp5718174p5718183.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Saludos, --- Nada que se consiga sin pena y sin trabajo es verdaderamente valioso. Joseph Addison --- ICE Ernesto Arteaga Zavala Ingeniero de Desarrollo -- Emmanuel DEMEY Ingénieur Etude et Développement ATOS Worldline +33 (0)6 47 47 42 02 demey.emman...@gmail.com http://emmanueldemey.fr/ Twitter : @EmmanuelDemey
Re: Which phase of page lifecycle will not occur when we access page 2nd time?
Hmm... When does it not get called? I always see onActivate in the JumpStart link On Nov 22, 2012, at 5:47 AM, Geoff Callender wrote: onActivate() is NOT always called. See http://jumpstart.doublenegative.com.au/jumpstart/examples/navigation/whatiscalledandwhen . Geoff On 22/11/2012, at 9:36 PM, Thiago H de Paula Figueiredo wrote: On Thu, 22 Nov 2012 05:45:10 -0200, Muhammad Gelbana m.gelb...@gmail.com wrote: So now with 5.3.6, since pooling is disabled, is it a single page instance for each request? Yes. And how does it differ from the activation context event if they are both executed when the page is first loaded ? That's a completely different thing. The singletonness of Tapestry 5.2+ is about fields and the activation context is about invoking an event handler method. My *guess* is that tapestry loads the page for the first time (@PageLoaded), Correct. attaches it to the client's session (that is created by default) That's not correct. Tapestry doesn't create an user session by default. It's created when needed (a write to the session). In addition, page instances aren't attached to sessions. I guess you're talking about the per-thread map used to store the field values. If yes, then you were correct, just used the wrong words. :) and then executes the ActivationContext even whenever a request is made to the page, am I correct ? Correct. -- Thiago H. de Paula Figueiredo - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Tapestry-JQuery: use of GoogleMap component
I found the same problem with the component, so what I did, I changed the scripts by this ones on Tapestry-Jquery Project http://gmap.nurtext.de/ And this is what I got: http://tapestry.1045711.n5.nabble.com/file/n5718196/maps.png -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-JQuery-use-of-GoogleMap-component-tp5718195p5718196.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Adding a progress listener to UploadedFile
Hi there. I would like to add a progress listener to UploadedFile to track progress up the file being uploaded. I know that it's possible to do this with apache commons file upload. Is there an easy way to do it with the T5 UploadedFile class? Cheers, Dave. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Adding-a-progress-listener-to-UploadedFile-tp5718197.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Adding a progress listener to UploadedFile
you are referring to: http://commons.apache.org/fileupload/using.html#Watching_progress ? On 23/11/2012 8:49 AM, dkeenan wrote: Hi there. I would like to add a progress listener to UploadedFile to track progress up the file being uploaded. I know that it's possible to do this with apache commons file upload. Is there an easy way to do it with the T5 UploadedFile class? Cheers, Dave. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Adding-a-progress-listener-to-UploadedFile-tp5718197.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Adding a progress listener to UploadedFile
Yes. Is there a way to set the listener from within Tapestry? -- View this message in context: http://tapestry.1045711.n5.nabble.com/Adding-a-progress-listener-to-UploadedFile-tp5718197p5718199.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
