Thanks for the quick response. Unfortunately I’m really tied up at the moment, so even JumpStart for Tapestry 5.4 has to wait for a bit.
> On 30 Dec 2015, at 3:30 PM, Jochen Kemnade <jochen.kemn...@eddyson.de> wrote: > > Hi Geoff, > > thanks for sharing your thoughts. > > ----- On Dec 30, 2015, at 3:04 AM, JumpStart > geoff.callender.jumpst...@gmail.com wrote: >> - Grid needs a context to properly participate in AJAX pages >> https://issues.apache.org/jira/browse/TAP5-2297 >> Please note that the issue has a link to a working solution. > > I haven't had the chance to look into this issue. I'd appreciate a patch or > some code snippets that demonstrate the problem. > >> - type="number" fails when decimal separator isn't "." >> https://issues.apache.org/jira/browse/TAP5-2409 > > I'll have another look at that one. > >> - Form and BeanEditForm differ in JSR-303 detection >> https://issues.apache.org/jira/browse/TAP5-2255 > > That one's actually waiting for a comment from you, Geoff. ;-) Can you find a > simpler example that doesn't need Joda-Time? > >> - Checkbox doesn't trigger VALIDATE event >> https://issues.apache.org/jira/browse/TAP5-2075 > > That one has a patch but no test. I really like tests. ;-) > >> - Tree's standard use case needs to be documented >> https://issues.apache.org/jira/browse/TAP5-1921 > > Everyone's invited to help out with that one. There are some sources linked > that can provide some inspiration. > >> For 5.5: >> >> I like your 5.5 list, and I like that it’s short and very quickly achievable, >> but I’d also like people to consider the following item. Without it, we’re >> holding back AJAX users or sending them off to client-side frameworks. >> >> - Client-side publish/subscribe mechanism >> https://issues.apache.org/jira/browse/TAP5-2416 > > I have outlined a solution on the issue. If we agree on a solution, we can > probably wrap it into an API. > > Jochen > > >>> On 29 Dec 2015, at 11:41 PM, Jochen Kemnade <jochen.kemn...@eddyson.de> >>> wrote: >>> >>> Hi, >>> >>> I'd like to hear some opinions about how we should proceed with the Tapestry >>> development. >>> >>> Which are the things we want to do for 5.5? >>> What are the things we want to do for 5.4.x? >>> Do we want to create a 5.4 branch and start progress on 5.5 right away? >>> >>> I'll go ahead and open the discussion with this proposal: >>> >>> I'd like to start working toward 5.5 pretty soon and I'd like it to take >>> much >>> less time than 5.4 did. >>> For 5.5, I'd like to require Java 8, update some libraries, maybe add >>> support >>> for Geb tests, and remove some deprecated code. That's basically it. >>> As Java 8 and some library updates can't be done for 5.4.x, I'd create a 5.4 >>> branch right now and do the updates in master. >>> I'd prefer if we concentrated on the 5.5 release and only backport bug >>> fixes to >>> the 5.4 branch. I hope we can get 5.5.0 out soon so we won't need to do too >>> many 5.4.x releases. >>> >>> Now let's hear some other opinions. :-) >>> >>> Jochen >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org >>> For additional commands, e-mail: dev-h...@tapestry.apache.org >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: dev-h...@tapestry.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
