Re: Making select component for the language

2013-08-16 Thread Geoff Callender
I expect the solution is to combine the techniques from the following links, but maybe I am missing the point - what issues are you anticipating? http://jumpstart.doublenegative.com.au/jumpstart/examples/localization/bymessagecatalog http://jumpstart.doublenegative.com.au/jumpst

Re: Weaves library

2013-08-16 Thread David Canteros
Sorry, I forgot the code. There is nothing special, I have only included a component called "PagedGrid" in the TML(instead of the classic Grid) file and a code for specific GridDataSource in java file. The component works fine, but the ajax actionlink throw the mentioned exception. This only happ

Re: Weaves library

2013-08-16 Thread David Canteros
The link: https://github.com/intercommit/Weaves I'm pretty sure that "weaves" uses jquery (in the repository I saw the files jquery-1.9.1.min.js and jquery_init.js), can we have a conflict between jquery from weaves and jquery from tapestry5-jquery? ---

Re: Weaves library

2013-08-16 Thread Emmanuel DEMEY
I do not think tapestry jquery is the problem. I am maybe wrong. Does Weaves use tapestry jquery? Can you give a link to this library and some codes. Manu Le 16 août 2013 17:40, "David Canteros" a écrit : > Hi! > I'm improving my T5 app interface and during this process I found the > excellent li

Re: changing t:type binding prefix

2013-08-16 Thread Thiago H de Paula Figueiredo
On Fri, 16 Aug 2013 14:06:36 -0300, Nicolas Barrera wrote: Thank you Lance and Thiago, I was trying to avoid doing this, or the equivalent blocks and delegate structure. For the love of everything sacred, please don't use the else block of If. It's way confusing.

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Martin Kersten
Right noticed that. The TapestryFilter is all about final methods. I currently use a request handler and borrow ideas from cometd implementation :) 2013/8/16 Thiago H de Paula Figueiredo > On Fri, 16 Aug 2013 12:22:57 -0300, Martin Kersten < > martin.kersten...@gmail.com> wrote: > > Lance curr

Re: changing t:type binding prefix

2013-08-16 Thread Nicolas Barrera
Thank you Lance and Thiago, I was trying to avoid doing this, or the equivalent blocks and delegate structure. But now I 've learnt that the t:type parameter uses always LITERAL prefix and that can't be changed. thank you. Nicolás.- On Fri, Aug 16, 2013 at 1:46 PM, Thiago H

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Thiago H de Paula Figueiredo
On Fri, 16 Aug 2013 12:22:57 -0300, Martin Kersten wrote: Lance currently I go with extending the TapestryFilter and bend it together with AtmosphereServlet30. If I get some results I post it here. If it is working I will make a blog post and donate the code. Maybe we find a more transpar

Re: changing t:type binding prefix

2013-08-16 Thread Thiago H de Paula Figueiredo
On Fri, 16 Aug 2013 12:05:18 -0300, Nicolas Barrera wrote: Hi, Hi! I 've tried to dynamically change the t:type attribute of an input textfield by doing this: As Lance said, t:type is the Tapestry component type. This is completely unrelated to bindings. The HTML attribute can be se

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Lance Java
As I've said, I wouldn't extend TapestryFilter, you should do one of the following: 1. Configure AtmosphereServlet in web.xml and tell tapestry to ignore the atmosphere URL 2. Contribute a HttpServletRequestFilter via tapestry IOC. The filter delegates through to a AtmosphereServlet instance

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Martin Kersten
Lance you are right. Also I noticed that you are still maintaining the cometd implementation. Nice work. I failed using the tapestry filter. Obviously this isnt the Tapestry way I was trying to do things. I will mimic the way you did with cometd. Thanks for your help, Cheers, Martin (Kersten)

Weaves library

2013-08-16 Thread David Canteros
Hi! I'm improving my T5 app interface and during this process I found the excellent library called "Weaves". I want to test the "PagedGrid" component, it looks great! But I have a little problem: when I replace the standard grid by the pagedgrid then all of the ajax actionlinks stop working. The pa

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Martin Kersten
Lance currently I go with extending the TapestryFilter and bend it together with AtmosphereServlet30. If I get some results I post it here. If it is working I will make a blog post and donate the code. Maybe we find a more transparent way, then. Fingers crossed. 2013/8/16 Lance Java > Currently

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Martin Kersten
I am restricted to Java at the backend. I might have evaluated something like node.js+redis for the socket.io. That would be good. And before switching to node.js I would also evaluate the PlayFramework since they have session.io support out of the box and also allow me to stick to the Java way. Bu

Re: changing t:type binding prefix

2013-08-16 Thread Lance Java
In tapestry, the "t:type" attribute refers to the component type, and not the "type" attribute that is rendered in the HTML. One of Tapestry's principles is static structure, dynamic behaviour so the "t:type" can not be a runtime value (http://tapestry.apache.org/principles.html) Tapestry has sepa

changing t:type binding prefix

2013-08-16 Thread Nicolas Barrera
Hi, I 've tried to dynamically change the t:type attribute of an input textfield by doing this:

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Alejandro Scandroli
Hi Martin Are you restricted to a Java application server? can you use things like NodeJS or Redis? A couple of years ago, I used Tapestry+NodeJS+Redis to push location information to a mobile webapp. As a starting point I used this example by Robin Komiwes: http://spreadthesource.com/2010/11/brin

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Lance Java
Currently, the only integrated push is tapestry-cometd. Howard has mentioned a few times that he'd like to include a push implementation in tapestry core but that hasn't happened yet. As has been mentioned, there's nothing stopping you from using Atmosphere and Tapestry side by side. If you decla

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Martin Kersten
That is very useful. Sadly my task at hand needs some server push data. What you suggested is like a lazy init. So after the page loaded go and get some content. (If I understood you correctly) I am comming form the GWT world and there is a need to drop GWT for this project. So I need to learn it

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Lance Java
I agree it's not easy, but just wanted to put it up for discussion. I think that having a clientside function could simplify many components. Generating a serverside link then passing it through as javascript initializer on the client adds extra code each time. I've done this many times in many co

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Thiago H de Paula Figueiredo
On Fri, 16 Aug 2013 09:01:37 -0300, Lance Java wrote: It would be nice to have a javascript function to generate event URL's. That would need a JavaScript implementation of UrlEncoder, which is an overridable service. Validators have both a clientside and a serverside implementation. P

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Lance Java
>> It would be nice to have a javascript function to generate event URL's. > That would need a JavaScript implementation of UrlEncoder, which is an overridable service. Validators have both a clientside and a serverside implementation. Perhaps UrlEncoders could do the same?

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Dmitry Gusev
Yes, but you mentioned it here first ;) On Fri, Aug 16, 2013 at 3:37 PM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Fri, 16 Aug 2013 07:55:54 -0300, Dmitry Gusev > wrote: > > +1 for Thiago's approach -- it is also widely used, especially if you >> want to render markup or u

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Thiago H de Paula Figueiredo
On Fri, 16 Aug 2013 08:04:44 -0300, Lance Java wrote: Thiago's approach works well when the event context is known on the server when the Link is generated. When you want to pass dynamic clientside values (mouse location, field values etc) you either need to use request parameters or do

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Thiago H de Paula Figueiredo
On Fri, 16 Aug 2013 07:55:54 -0300, Dmitry Gusev wrote: +1 for Thiago's approach -- it is also widely used, especially if you want to render markup or update some zones in response. It's not my approach, it's the one used by Tapestry itself in its AJAX-powered components. :) -- Thiago

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Lance Java
Thiago's approach works well when the event context is known on the server when the Link is generated. When you want to pass dynamic clientside values (mouse location, field values etc) you either need to use request parameters or do some token replacement on the URL generated serverside. It would

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Dmitry Gusev
+1 for Thiago's approach -- it is also widely used, especially if you want to render markup or update some zones in response. On Fri, Aug 16, 2013 at 2:52 PM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Fri, 16 Aug 2013 06:46:28 -0300, Martin Kersten < > martin.kersten...@gmai

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Thiago H de Paula Figueiredo
On Fri, 16 Aug 2013 06:46:28 -0300, Martin Kersten wrote: I investigated the cometd yesterday and today. The maven repository was broken for this one. Since the last commit is half a year old, I think it is not maintained anymore. I currently at the moment try to do the same but using atmo

Re: Quartz for Tapestry5

2013-08-16 Thread Dmitry Gusev
FYI: This module and others from anjlab-tapestry-commons are now available from bintray maven repository. See github readme for details. On Tue, Aug 13, 2013 at 10:45 AM, Stephan Windmüller < stephan.windmuel...@tu-dortmund.de> wrote: > On 12.08.2013 23:16, Dmitry Gusev wrote: > > > Just applied

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Lance Java
I really like DWR's approach to AJAX where it creates a clientside representation of your serverside services and marshals between javascript and java. DWR has built in spring integration but it wouldn't be difficult to create a TapestryCreator (using SpringCreator as a reference) to lookup service

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Dmitry Gusev
I've successfully used Atmosphere with tapestry, though I remember that setup wasn't trivial, but once you do it -- it works well. Atmosphere provides access to its broadcasters using static factory methods, so you can get them from whenever you need. Also I used atmosphere requests interceptors by

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Martin Kersten
I investigated the cometd yesterday and today. The maven repository was broken for this one. Since the last commit is half a year old, I think it is not maintained anymore. I currently at the moment try to do the same but using atmosphere instead if this is not working I will try to redo the cometd

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Lance Java
FYI, there's no need to wrap the tapestry servlet (it's actually a filter). tapestry-cometd works by contributing a HttpServletRequestFilter to tapestry. The filter instantiates / delegates through to a CometdServlet instance. http://tapestry.apache.org/request-processing.html https://github.com/

Re: Best way to communicate with JS using Tapestry as BackEnd

2013-08-16 Thread Lance Java
Take a look at tapestry-cometd. It's built on top of Atmosphere's CometD support https://github.com/uklance/tapestry-cometd On 16 Aug 2013 06:09, "Martin Kersten" wrote: > Hi there, > > back in the old days I used to use GWT alot in conjunction with > Tapestry. Nowadays it would be fine to