Sorry people, the trunk may be a bit unstable for some time. Why? Alejandro has started a furious effort of coding Trails 2.0 and merging in T5! In the meantime, I've been enjoying development with the superb ajax features of T4.x series (eventlisteners, async forms etc.) With that said, we had an interesting discussion on #trails over IRC, here's an excerpt (Alejandro aka billy):
(5:00:25 PM) continuum: BUILD FAILURE: Trails Modules...
(5:02:01 PM) kaosko: uh huh. suppose I need to stop the ci builds
(5:04:42 PM) kaosko: done
(5:07:38 PM) billy: hey
(5:07:46 PM) billy: sorry about that ![]()
(5:07:53 PM) kaosko: hey Alejandro
(5:08:09 PM) kaosko: no problem, it's very cool news you started working on T5 integration
(5:08:26 PM) kaosko: I really thought you'd be in bed by now
(5:08:39 PM) kaosko: you got a min or two?
<snip>
(5:10:11 PM) kaosko: you know, for a long time I've been thinking about the long conversation support
(5:11:42 PM) kaosko: I've evaluated Spring webflow, seam and all the others. the problem is always the same, they are configuration heavy
(5:12:32 PM) billy: yeap, I know
(5:14:06 PM) kaosko: at the same time, ajaxifying the web has changed at least how I view or build the web pages. so, my new thing is that a conversation should normally always happen on a single url. that'd make it so much easier to support conversations
(5:15:27 PM) billy: hmmm op
(5:15:41 PM) billy: interesting....
(5:15:49 PM) kaosko: just wondering if you are planning on making good use of ajax in the next version of Trails, and perhaps we can align the goals so the conversations would right in
(5:16:16 PM) billy: I was about to ask you something similar
(5:16:39 PM) billy: could we drop non-AJAX support?
(5:17:18 PM) kaosko: the simple urls you added in trails 1.2 look nice and of course T5 has a built-in rest-like urls. yes, I think dropping non-ajax support would make sense
(5:18:17 PM) billy: ok
(5:18:18 PM) kaosko: I see absolutely no need to refresh the whole edit page, or list or whatever until you are done
(5:18:51 PM) billy: excellent!! AJAX ON !!
(5:19:33 PM) kaosko: obviously, urls are still very useful for bookmarking and breadcrumb etc.. I don't want to go for whole GWT approach either.
(5:20:02 PM) billy: no, no, I know
(5:21:00 PM) billy: are you already using T5?
(5:21:23 PM) kaosko: just evaluated, not using it for anything real
(5:21:49 PM) kaosko: ok very cool. If I could just get this last project I've been working on done, I could join you a bit on Trails dev
(5:23:31 PM) kaosko: how about entity manager, jpa.. have you used glassfish?
(5:24:06 PM) billy: nop, I haven't used glassfish
(5:24:40 PM) billy: I thought about entitymanager
(5:25:37 PM) billy: I think we should include it , to allow an easier migration to full JPA
(5:26:03 PM) kaosko: k. the new re-architected container is just completely modular; it's really getting to a point that it's just as fast to start up as tomcat.
(5:26:35 PM) billy: good
