I'd love to see tapestry support websockets out of the box, perhaps with a
swappable implementation (atmosphere, socksjs, cometd etc)
I've tried to uphold the "tapestry philosophy" in both implementations
using event-handlers, blocks and zones (they're actually a pushTarget
rather than a zone). If
That sort of swappable implementation would fit right in with the swappable
JavaScript framework for sure!
I saw some discussion related to whether Prototype support should be
dropped as a default as per Howard's past wishes on the dev boards. It made
me think that perhaps the different js framewo
Agreed Dimitris - upon build is indeed best!
There shouldn't be any inconsistencies provided I make sure both
tapestry-webresources and wro4j are using the same less4j version.
I imagine this will be a very standard pattern so I will aim to share the
working wro4j maven plugin configuration I end
I'll try tapestry-atmosphere, I had a quick look over demo code and it looks
slick.
I think this or similar ought to be a core feature or at least a proper
tapestry sub project. It would definitely make tapestry more appealing for
today's SPAs and mobile apps.
John
Sent from my iPhone
> On
I wanted to create a web chat application. I based it off of Atmosphere
(http://async-io.org). I made a small contribution to that project to make
integration with Tapestry easier (primarily for IoC.) It was enough to get it
working for me. Atmosphere provides a nice JavaScript API for the clien
I'm guessing it's similar to this?
https://github.com/uklance/tapestry-atmosphere/blob/master/tapestry-atmosphere/src/main/java/org/lazan/t5/atmosphere/services/TapestryAtmosphereObjectFactory.java
On 27 Oct 2016 9:12 p.m., "Norman Franke" wrote:
> I wanted to create a web chat application. I ba
