Re: T 5.1 vs 5.0 JSON encoding - breaks IE8
No worries, glad I could help! Ciaran On 18/11/2009 5:36pm, Thiago H. de Paula Figueiredo thiag...@gmail.com wrote: Em Tue, 17 Nov 2009 16:50:52 -0200, Kalle Korhonen kalle.o.korho...@gmail.com escreveu: Thanks Ciaran, voted. Thiago, would you mind doing the honors? (Since I know you read this anyway :) How do you know I'd read your message? :P It's been months since my last commit, unfortunately. I've just applied the patch, ran the tests, everything ok, commited the code. Thanks Ciaran! :) - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T 5.1 vs 5.0 JSON encoding - breaks IE8
On Tue, Nov 17, 2009 at 11:56 AM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: On Tue, Nov 17, 2009 at 11:01 AM, David Rees dree...@gmail.com wrote: On Tue, Nov 17, 2009 at 2:00 AM, Ciaran Wood ciar...@gamesys.co.uk wrote: The issue you were thinking of is https://issues.apache.org/jira/browse/TAP5-714 - there is a patch w/tests attached to the issue so a committer can probably fix this one! Thanks, voted. BTW, it affects all versions of IE that I tested. It's a show-stopper, not a minor issue - should raise the priority, especially since it has a patch. Agree, maybe not a showstopper, but not a minor either. How can we encourage the developers to get a release out with some of these issues? Are people building their own local version with patches applied? Starting to veer off-topic, but I think the issue there is that Howard has traditionally done all the releases, but he hasn't been actively involved in bug fixing lately (and probably shouldn't need to be). Howard's also been complaining about some difficulties with releasing but I don't know the details. I know though that setting up a fully automated release process with Maven can sometimes be taxing but the efforts are well worth it. Especially for bug fix releases, confidently being able to roll up yet another point release is great (at times, I release my projects a few times a week since it's so simple). I fully agree with you that more frequent point releases for T5 are badly needed. Actually, my intent has been to let T5 stabilize with 5.1 for a bit. In addition, as some of my postings have mentioned, I feel that if I start coding 5.2 features and bug fixes, I'll be less likely to start on a book. Doing releases is merely time consuming; Maven isn't an overwhelming factor in that ... it's more about the constraints of getting releases out, voted and mirrored that can take several days from start to finish. However, Andreas has been working on a new approach based on the Nexus tool for Maven ... we'll have to see what the new process looks like. I'd avoid building your own versions if at all possible. Not because building would be too difficult, but with local versions, you need to deal with everything else included - deploying, maintaining, distributing and keeping track of versions. Use nightly snapshots from Formos if you have to and lock down to specific unique snapshot whenever possible. Kalle - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T 5.1 vs 5.0 JSON encoding - breaks IE8
But doesn't stabilizing mean to fix at least the major bugs? Especially if patches are provided? Otherwise it looks more like hibernating. Markus On Wed, Nov 18, 2009 at 10:30 AM, Howard Lewis Ship hls...@gmail.com wrote: On Tue, Nov 17, 2009 at 11:56 AM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: On Tue, Nov 17, 2009 at 11:01 AM, David Rees dree...@gmail.com wrote: On Tue, Nov 17, 2009 at 2:00 AM, Ciaran Wood ciar...@gamesys.co.uk wrote: The issue you were thinking of is https://issues.apache.org/jira/browse/TAP5-714 - there is a patch w/tests attached to the issue so a committer can probably fix this one! Thanks, voted. BTW, it affects all versions of IE that I tested. It's a show-stopper, not a minor issue - should raise the priority, especially since it has a patch. Agree, maybe not a showstopper, but not a minor either. How can we encourage the developers to get a release out with some of these issues? Are people building their own local version with patches applied? Starting to veer off-topic, but I think the issue there is that Howard has traditionally done all the releases, but he hasn't been actively involved in bug fixing lately (and probably shouldn't need to be). Howard's also been complaining about some difficulties with releasing but I don't know the details. I know though that setting up a fully automated release process with Maven can sometimes be taxing but the efforts are well worth it. Especially for bug fix releases, confidently being able to roll up yet another point release is great (at times, I release my projects a few times a week since it's so simple). I fully agree with you that more frequent point releases for T5 are badly needed. Actually, my intent has been to let T5 stabilize with 5.1 for a bit. In addition, as some of my postings have mentioned, I feel that if I start coding 5.2 features and bug fixes, I'll be less likely to start on a book. Doing releases is merely time consuming; Maven isn't an overwhelming factor in that ... it's more about the constraints of getting releases out, voted and mirrored that can take several days from start to finish. However, Andreas has been working on a new approach based on the Nexus tool for Maven ... we'll have to see what the new process looks like. I'd avoid building your own versions if at all possible. Not because building would be too difficult, but with local versions, you need to deal with everything else included - deploying, maintaining, distributing and keeping track of versions. Use nightly snapshots from Formos if you have to and lock down to specific unique snapshot whenever possible. Kalle - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.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: T 5.1 vs 5.0 JSON encoding - breaks IE8
True; the big question is whether bugs should be fixed for 5.1 (i.e., leading up to a 5.1.0.6 release perhaps) or whether they can be bundled into a 5.2 alpha release. On Wed, Nov 18, 2009 at 1:52 AM, Markus Joschko markus.josc...@gmail.com wrote: But doesn't stabilizing mean to fix at least the major bugs? Especially if patches are provided? Otherwise it looks more like hibernating. Markus On Wed, Nov 18, 2009 at 10:30 AM, Howard Lewis Ship hls...@gmail.com wrote: On Tue, Nov 17, 2009 at 11:56 AM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: On Tue, Nov 17, 2009 at 11:01 AM, David Rees dree...@gmail.com wrote: On Tue, Nov 17, 2009 at 2:00 AM, Ciaran Wood ciar...@gamesys.co.uk wrote: The issue you were thinking of is https://issues.apache.org/jira/browse/TAP5-714 - there is a patch w/tests attached to the issue so a committer can probably fix this one! Thanks, voted. BTW, it affects all versions of IE that I tested. It's a show-stopper, not a minor issue - should raise the priority, especially since it has a patch. Agree, maybe not a showstopper, but not a minor either. How can we encourage the developers to get a release out with some of these issues? Are people building their own local version with patches applied? Starting to veer off-topic, but I think the issue there is that Howard has traditionally done all the releases, but he hasn't been actively involved in bug fixing lately (and probably shouldn't need to be). Howard's also been complaining about some difficulties with releasing but I don't know the details. I know though that setting up a fully automated release process with Maven can sometimes be taxing but the efforts are well worth it. Especially for bug fix releases, confidently being able to roll up yet another point release is great (at times, I release my projects a few times a week since it's so simple). I fully agree with you that more frequent point releases for T5 are badly needed. Actually, my intent has been to let T5 stabilize with 5.1 for a bit. In addition, as some of my postings have mentioned, I feel that if I start coding 5.2 features and bug fixes, I'll be less likely to start on a book. Doing releases is merely time consuming; Maven isn't an overwhelming factor in that ... it's more about the constraints of getting releases out, voted and mirrored that can take several days from start to finish. However, Andreas has been working on a new approach based on the Nexus tool for Maven ... we'll have to see what the new process looks like. I'd avoid building your own versions if at all possible. Not because building would be too difficult, but with local versions, you need to deal with everything else included - deploying, maintaining, distributing and keeping track of versions. Use nightly snapshots from Formos if you have to and lock down to specific unique snapshot whenever possible. Kalle - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.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 -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T 5.1 vs 5.0 JSON encoding - breaks IE8
Personally I am fine with a 5.2 alpha release as I don't have to test too much functionality. But I guess if tapestry wants to be taken seriously in the enterprise world it needs to provide bug fixing releases for existing stable releases as otherwise the testing departments are crying for complete retests. (Apart from the fact that PMs are crying when they read alpha release just because they want have to a few major bugs fixed) Markus On Wed, Nov 18, 2009 at 10:57 AM, Howard Lewis Ship hls...@gmail.com wrote: True; the big question is whether bugs should be fixed for 5.1 (i.e., leading up to a 5.1.0.6 release perhaps) or whether they can be bundled into a 5.2 alpha release. On Wed, Nov 18, 2009 at 1:52 AM, Markus Joschko markus.josc...@gmail.com wrote: But doesn't stabilizing mean to fix at least the major bugs? Especially if patches are provided? Otherwise it looks more like hibernating. Markus On Wed, Nov 18, 2009 at 10:30 AM, Howard Lewis Ship hls...@gmail.com wrote: On Tue, Nov 17, 2009 at 11:56 AM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: On Tue, Nov 17, 2009 at 11:01 AM, David Rees dree...@gmail.com wrote: On Tue, Nov 17, 2009 at 2:00 AM, Ciaran Wood ciar...@gamesys.co.uk wrote: The issue you were thinking of is https://issues.apache.org/jira/browse/TAP5-714 - there is a patch w/tests attached to the issue so a committer can probably fix this one! Thanks, voted. BTW, it affects all versions of IE that I tested. It's a show-stopper, not a minor issue - should raise the priority, especially since it has a patch. Agree, maybe not a showstopper, but not a minor either. How can we encourage the developers to get a release out with some of these issues? Are people building their own local version with patches applied? Starting to veer off-topic, but I think the issue there is that Howard has traditionally done all the releases, but he hasn't been actively involved in bug fixing lately (and probably shouldn't need to be). Howard's also been complaining about some difficulties with releasing but I don't know the details. I know though that setting up a fully automated release process with Maven can sometimes be taxing but the efforts are well worth it. Especially for bug fix releases, confidently being able to roll up yet another point release is great (at times, I release my projects a few times a week since it's so simple). I fully agree with you that more frequent point releases for T5 are badly needed. Actually, my intent has been to let T5 stabilize with 5.1 for a bit. In addition, as some of my postings have mentioned, I feel that if I start coding 5.2 features and bug fixes, I'll be less likely to start on a book. Doing releases is merely time consuming; Maven isn't an overwhelming factor in that ... it's more about the constraints of getting releases out, voted and mirrored that can take several days from start to finish. However, Andreas has been working on a new approach based on the Nexus tool for Maven ... we'll have to see what the new process looks like. I'd avoid building your own versions if at all possible. Not because building would be too difficult, but with local versions, you need to deal with everything else included - deploying, maintaining, distributing and keeping track of versions. Use nightly snapshots from Formos if you have to and lock down to specific unique snapshot whenever possible. Kalle - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.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 -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.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: T 5.1 vs 5.0 JSON encoding - breaks IE8
Since we recently also fixed a major bug concerning application security, I'd say we should do a 5.1.0.6 release. I wouldn't force my users to upgrade to a new version - aside from it being an alpha version - just in order to receive bug fixes. In the end it *might* mean having to modify a perfectly well running application. Uli Am 18.11.2009 10:57 schrieb Howard Lewis Ship: True; the big question is whether bugs should be fixed for 5.1 (i.e., leading up to a 5.1.0.6 release perhaps) or whether they can be bundled into a 5.2 alpha release. On Wed, Nov 18, 2009 at 1:52 AM, Markus Joschko markus.josc...@gmail.com wrote: But doesn't stabilizing mean to fix at least the major bugs? Especially if patches are provided? Otherwise it looks more like hibernating. Markus On Wed, Nov 18, 2009 at 10:30 AM, Howard Lewis Ship hls...@gmail.com wrote: On Tue, Nov 17, 2009 at 11:56 AM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: On Tue, Nov 17, 2009 at 11:01 AM, David Rees dree...@gmail.com wrote: On Tue, Nov 17, 2009 at 2:00 AM, Ciaran Wood ciar...@gamesys.co.uk wrote: The issue you were thinking of is https://issues.apache.org/jira/browse/TAP5-714 - there is a patch w/tests attached to the issue so a committer can probably fix this one! Thanks, voted. BTW, it affects all versions of IE that I tested. It's a show-stopper, not a minor issue - should raise the priority, especially since it has a patch. Agree, maybe not a showstopper, but not a minor either. How can we encourage the developers to get a release out with some of these issues? Are people building their own local version with patches applied? Starting to veer off-topic, but I think the issue there is that Howard has traditionally done all the releases, but he hasn't been actively involved in bug fixing lately (and probably shouldn't need to be). Howard's also been complaining about some difficulties with releasing but I don't know the details. I know though that setting up a fully automated release process with Maven can sometimes be taxing but the efforts are well worth it. Especially for bug fix releases, confidently being able to roll up yet another point release is great (at times, I release my projects a few times a week since it's so simple). I fully agree with you that more frequent point releases for T5 are badly needed. Actually, my intent has been to let T5 stabilize with 5.1 for a bit. In addition, as some of my postings have mentioned, I feel that if I start coding 5.2 features and bug fixes, I'll be less likely to start on a book. Doing releases is merely time consuming; Maven isn't an overwhelming factor in that ... it's more about the constraints of getting releases out, voted and mirrored that can take several days from start to finish. However, Andreas has been working on a new approach based on the Nexus tool for Maven ... we'll have to see what the new process looks like. I'd avoid building your own versions if at all possible. Not because building would be too difficult, but with local versions, you need to deal with everything else included - deploying, maintaining, distributing and keeping track of versions. Use nightly snapshots from Formos if you have to and lock down to specific unique snapshot whenever possible. Kalle - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.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 - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T 5.1 vs 5.0 JSON encoding - breaks IE8
Em Wed, 18 Nov 2009 08:20:46 -0200, Ulrich Stärk u...@spielviel.de escreveu: Since we recently also fixed a major bug concerning application security, I'd say we should do a 5.1.0.6 release. +1 -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, software architect and developer, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T 5.1 vs 5.0 JSON encoding - breaks IE8
Am 18.11.2009 um 11:20 schrieb Ulrich Stärk: Since we recently also fixed a major bug concerning application security, I'd say we should do a 5.1.0.6 release. +1 Max - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T 5.1 vs 5.0 JSON encoding - breaks IE8
yes, it makes sense to do that 'bug-fix' release once TAP5-714 is fixed On Wed, Nov 18, 2009 at 1:02 PM, Max Weißböck m...@weissboeck.info wrote: Am 18.11.2009 um 11:20 schrieb Ulrich Stärk: Since we recently also fixed a major bug concerning application security, I'd say we should do a 5.1.0.6 release. +1 Max - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Andreas Andreou - andy...@apache.org - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
RE: T 5.1 vs 5.0 JSON encoding - breaks IE8
+1 (+40 if I count all T5 developers here ;-) Although I suggested a 5.1.1.x release in my previous post, quoted from below, I don't care what it's called as long as there's a non 5.2 bug-fix release. (preferably more than one release..) I think you should write the book, but only if there's going to be a T5.1.1.x set of releases with bugfixes - this is long overdue in my opinion. (we have too many 'temporary' tapestry fixes - it's annoying embarrassing) I don't think there's any pressing need for T5.2 yet (IMHO) but there are a lot of bugs in JIRA and some of them are quite serious. You have a few good committers and a community who often submit patches when they enter bugs. What's missing is getting some momentum and getting the results out there in official releases! -Original Message- From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] Sent: 18 November 2009 10:50 To: Tapestry users Subject: Re: T 5.1 vs 5.0 JSON encoding - breaks IE8 Em Wed, 18 Nov 2009 08:20:46 -0200, Ulrich Stärk u...@spielviel.de escreveu: Since we recently also fixed a major bug concerning application security, I'd say we should do a 5.1.0.6 release. +1 - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T 5.1 vs 5.0 JSON encoding - breaks IE8
Em Tue, 17 Nov 2009 16:50:52 -0200, Kalle Korhonen kalle.o.korho...@gmail.com escreveu: Thanks Ciaran, voted. Thiago, would you mind doing the honors? (Since I know you read this anyway :) How do you know I'd read your message? :P It's been months since my last commit, unfortunately. I've just applied the patch, ran the tests, everything ok, commited the code. Thanks Ciaran! :) -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, software architect and developer, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T 5.1 vs 5.0 JSON encoding - breaks IE8
On Wed, Nov 18, 2009 at 1:57 AM, Howard Lewis Ship hls...@gmail.com wrote: On Wed, Nov 18, 2009 at 1:52 AM, Markus Joschko markus.josc...@gmail.com wrote: But doesn't stabilizing mean to fix at least the major bugs? Especially if patches are provided? Otherwise it looks more like hibernating. True; the big question is whether bugs should be fixed for 5.1 (i.e., leading up to a 5.1.0.6 release perhaps) or whether they can be bundled into a 5.2 alpha release. Most projects seem to do the following: Decide which major releases are currently supported. These releases get security patches and bugfixes. Any significant new features go into the next major release. So the question is: What versions of Tapestry is supported? Is 5.0.x supported? Is 5.1.0.x supported? If both are supported, they should both get any security and important bugfixes. And those security / bugfixes should go into trunk for the next major release as well. The biggest issue is manpower - since as you said, it takes a bit of work to backport patches and push out a release - but even if they only get into snapshot builds (a 5.0.19-SNAPSHOT and 5.1.0.6-SNAPSHOT) that are built nightly from the appropriate branch, that would satisfy the needs of a lot of users without having to push out an actual release too often. -Dave - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T 5.1 vs 5.0 JSON encoding - breaks IE8
Since we recently also fixed a major bug concerning application security, I'd say we should do a 5.1.0.6 release. +1 There should also be a new version of the 5.0 branch with any new security fixes +1 -- View this message in context: http://old.nabble.com/T-5.1-vs-5.0-JSON-encoding---breaks-IE8-tp26384537p26414154.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: T 5.1 vs 5.0 JSON encoding - breaks IE8
The issue you were thinking of is https://issues.apache.org/jira/browse/TAP5-714 - there is a patch w/tests attached to the issue so a committer can probably fix this one! Ciaran On 17/11/2009 7:20am, Kalle Korhonen kalle.o.korho...@gmail.com wrote: On Mon, Nov 16, 2009 at 11:14 PM, David Rees dree...@gmail.com wrote: Yep, already using tapx-prototype, that was the first thing I tried before digging into it more and figuring out that the JSON encoding changed in T5.1 (can't find the ticket now, but it was changed to replace instances of \ with ' to save bandwidth). tapx-prototype doesn't affect the JSON encoding - I wouldn't expect it to affect JSON decoding, either. Right, I recall seeing the same ticket, but don't remember exactly. I'll browse around since I'm afraid I may hit the same issue in the near future. Kalle - 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: T 5.1 vs 5.0 JSON encoding - breaks IE8
Thanks Ciaran, voted. Thiago, would you mind doing the honors? (Since I know you read this anyway :) Kalle On Tue, Nov 17, 2009 at 2:00 AM, Ciaran Wood ciar...@gamesys.co.uk wrote: The issue you were thinking of is https://issues.apache.org/jira/browse/TAP5-714 - there is a patch w/tests attached to the issue so a committer can probably fix this one! Ciaran On 17/11/2009 7:20am, Kalle Korhonen kalle.o.korho...@gmail.com wrote: On Mon, Nov 16, 2009 at 11:14 PM, David Rees dree...@gmail.com wrote: Yep, already using tapx-prototype, that was the first thing I tried before digging into it more and figuring out that the JSON encoding changed in T5.1 (can't find the ticket now, but it was changed to replace instances of \ with ' to save bandwidth). tapx-prototype doesn't affect the JSON encoding - I wouldn't expect it to affect JSON decoding, either. Right, I recall seeing the same ticket, but don't remember exactly. I'll browse around since I'm afraid I may hit the same issue in the near future. Kalle - 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: T 5.1 vs 5.0 JSON encoding - breaks IE8
On Tue, Nov 17, 2009 at 2:00 AM, Ciaran Wood ciar...@gamesys.co.uk wrote: The issue you were thinking of is https://issues.apache.org/jira/browse/TAP5-714 - there is a patch w/tests attached to the issue so a committer can probably fix this one! Thanks, voted. BTW, it affects all versions of IE that I tested. It's a show-stopper, not a minor issue - should raise the priority, especially since it has a patch. How can we encourage the developers to get a release out with some of these issues? Are people building their own local version with patches applied? -Dave - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T 5.1 vs 5.0 JSON encoding - breaks IE8
On Tue, Nov 17, 2009 at 11:01 AM, David Rees dree...@gmail.com wrote: On Tue, Nov 17, 2009 at 2:00 AM, Ciaran Wood ciar...@gamesys.co.uk wrote: The issue you were thinking of is https://issues.apache.org/jira/browse/TAP5-714 - there is a patch w/tests attached to the issue so a committer can probably fix this one! Thanks, voted. BTW, it affects all versions of IE that I tested. It's a show-stopper, not a minor issue - should raise the priority, especially since it has a patch. Agree, maybe not a showstopper, but not a minor either. How can we encourage the developers to get a release out with some of these issues? Are people building their own local version with patches applied? Starting to veer off-topic, but I think the issue there is that Howard has traditionally done all the releases, but he hasn't been actively involved in bug fixing lately (and probably shouldn't need to be). Howard's also been complaining about some difficulties with releasing but I don't know the details. I know though that setting up a fully automated release process with Maven can sometimes be taxing but the efforts are well worth it. Especially for bug fix releases, confidently being able to roll up yet another point release is great (at times, I release my projects a few times a week since it's so simple). I fully agree with you that more frequent point releases for T5 are badly needed. I'd avoid building your own versions if at all possible. Not because building would be too difficult, but with local versions, you need to deal with everything else included - deploying, maintaining, distributing and keeping track of versions. Use nightly snapshots from Formos if you have to and lock down to specific unique snapshot whenever possible. Kalle - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T 5.1 vs 5.0 JSON encoding - breaks IE8
On Tue, Nov 17, 2009 at 11:56 AM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: On Tue, Nov 17, 2009 at 11:01 AM, David Rees dree...@gmail.com wrote: On Tue, Nov 17, 2009 at 2:00 AM, Ciaran Wood ciar...@gamesys.co.uk wrote: The issue you were thinking of is https://issues.apache.org/jira/browse/TAP5-714 - there is a patch w/tests attached to the issue so a committer can probably fix this one! Thanks, voted. BTW, it affects all versions of IE that I tested. It's a show-stopper, not a minor issue - should raise the priority, especially since it has a patch. Agree, maybe not a showstopper, but not a minor either. Seems pretty critical to me if it breaks the browser with the single largest market share - but either way - the bug has been known for 6 months now with a patch - yet the patch hasn't been applied anywhere as far as I can tell. How can we encourage the developers to get a release out with some of these issues? Are people building their own local version with patches applied? Starting to veer off-topic, but I think the issue there is that Howard has traditionally done all the releases, but he hasn't been actively involved in bug fixing lately (and probably shouldn't need to be). I agree. Aren't there a handful of Tapestry devs? Howard's also been complaining about some difficulties with releasing but I don't know the details. I know though that setting up a fully automated release process with Maven can sometimes be taxing but the efforts are well worth it. Especially for bug fix releases, confidently being able to roll up yet another point release is great (at times, I release my projects a few times a week since it's so simple). I fully agree with you that more frequent point releases for T5 are badly needed. I concur as well, here. Maven should make it easy to roll out point releases, no? Apply patch to 5.1.0 branch - bump version number, build and deploy. I'd avoid building your own versions if at all possible. Not because building would be too difficult, but with local versions, you need to deal with everything else included - deploying, maintaining, distributing and keeping track of versions. Use nightly snapshots from Formos if you have to and lock down to specific unique snapshot whenever possible. I would like to avoid it as well - but do you have an alternative? It's either apply a 1-line patch to Tapestry 5.1.0.5 and figure out how to build it (call it 5.1.0.5.1 or 5.1.0.6-SNAPSHOT internally or something), or go through hundreds of lines of my own code replacing single quotes with double quotes and more testing to work around this bug. -Dave - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T 5.1 vs 5.0 JSON encoding - breaks IE8
There's a known issue with the version of prototype packaged in
T5.1.0.5 and IE8. Are you using the newly released tapx-prototype
already (http://tapestry.formos.com/projects/tapx/)?
Kalle
On Mon, Nov 16, 2009 at 9:10 PM, David Rees dree...@gmail.com wrote:
Anyone else have issues with the new JSON encoding in 5.1?
I upgraded an application when a block is returned that has a
JavaScript link in it with single quotes, IE8 (haven't tested other
versions of IE) puke on it.
For example, this snippet in the block:
a href= onclick=openWindow('winname')Click me/a
Gets returned in T5.1.0.5 as:
a href='' onclick='openWindow(apos;winnameapos)'Click me/a
Gets returned in T5.0.18 as:
a href= onclick=openWindow('winname')Click me/a
Firefox 3.5 handles both OK.
Any work around that people know of off-hand besides going back to
T5.0? Only thing I've found so far is to swap out single/double
quotes in my .tml files like so:
a href= onclick='openWindow(winname)'Click me/a
But that's a major PITA in a large application.
-Dave
-
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: T 5.1 vs 5.0 JSON encoding - breaks IE8
Hello!
I am not using maven! What do I have to do to use tapx-prototype?
regards,
Mario
On Tue, Nov 17, 2009 at 6:17 AM, Kalle Korhonen
kalle.o.korho...@gmail.comwrote:
There's a known issue with the version of prototype packaged in
T5.1.0.5 and IE8. Are you using the newly released tapx-prototype
already (http://tapestry.formos.com/projects/tapx/)?
Kalle
On Mon, Nov 16, 2009 at 9:10 PM, David Rees dree...@gmail.com wrote:
Anyone else have issues with the new JSON encoding in 5.1?
I upgraded an application when a block is returned that has a
JavaScript link in it with single quotes, IE8 (haven't tested other
versions of IE) puke on it.
For example, this snippet in the block:
a href= onclick=openWindow('winname')Click me/a
Gets returned in T5.1.0.5 as:
a href='' onclick='openWindow(apos;winnameapos)'Click me/a
Gets returned in T5.0.18 as:
a href= onclick=openWindow('winname')Click me/a
Firefox 3.5 handles both OK.
Any work around that people know of off-hand besides going back to
T5.0? Only thing I've found so far is to swap out single/double
quotes in my .tml files like so:
a href= onclick='openWindow(winname)'Click me/a
But that's a major PITA in a large application.
-Dave
-
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: T 5.1 vs 5.0 JSON encoding - breaks IE8
On Mon, Nov 16, 2009 at 9:17 PM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: There's a known issue with the version of prototype packaged in T5.1.0.5 and IE8. Are you using the newly released tapx-prototype already (http://tapestry.formos.com/projects/tapx/)? Yep, already using tapx-prototype, that was the first thing I tried before digging into it more and figuring out that the JSON encoding changed in T5.1 (can't find the ticket now, but it was changed to replace instances of \ with ' to save bandwidth). tapx-prototype doesn't affect the JSON encoding - I wouldn't expect it to affect JSON decoding, either. -Dave - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T 5.1 vs 5.0 JSON encoding - breaks IE8
You need to do at least tiny little bit of homework yourself whether
or not you are using Maven. Get the jar from
http://tapestry.formos.com/maven-repository/com/howardlewisship/tapx-prototype/1.0.0/
Kalle
On Mon, Nov 16, 2009 at 10:47 PM, Mario Udina m.ud...@gmail.com wrote:
Hello!
I am not using maven! What do I have to do to use tapx-prototype?
regards,
Mario
On Tue, Nov 17, 2009 at 6:17 AM, Kalle Korhonen
kalle.o.korho...@gmail.comwrote:
There's a known issue with the version of prototype packaged in
T5.1.0.5 and IE8. Are you using the newly released tapx-prototype
already (http://tapestry.formos.com/projects/tapx/)?
Kalle
On Mon, Nov 16, 2009 at 9:10 PM, David Rees dree...@gmail.com wrote:
Anyone else have issues with the new JSON encoding in 5.1?
I upgraded an application when a block is returned that has a
JavaScript link in it with single quotes, IE8 (haven't tested other
versions of IE) puke on it.
For example, this snippet in the block:
a href= onclick=openWindow('winname')Click me/a
Gets returned in T5.1.0.5 as:
a href='' onclick='openWindow(apos;winnameapos)'Click me/a
Gets returned in T5.0.18 as:
a href= onclick=openWindow('winname')Click me/a
Firefox 3.5 handles both OK.
Any work around that people know of off-hand besides going back to
T5.0? Only thing I've found so far is to swap out single/double
quotes in my .tml files like so:
a href= onclick='openWindow(winname)'Click me/a
But that's a major PITA in a large application.
-Dave
-
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: T 5.1 vs 5.0 JSON encoding - breaks IE8
On Mon, Nov 16, 2009 at 11:14 PM, David Rees dree...@gmail.com wrote: Yep, already using tapx-prototype, that was the first thing I tried before digging into it more and figuring out that the JSON encoding changed in T5.1 (can't find the ticket now, but it was changed to replace instances of \ with ' to save bandwidth). tapx-prototype doesn't affect the JSON encoding - I wouldn't expect it to affect JSON decoding, either. Right, I recall seeing the same ticket, but don't remember exactly. I'll browse around since I'm afraid I may hit the same issue in the near future. Kalle - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T 5.1 vs 5.0 JSON encoding - breaks IE8
My question was badly placed! I have read:
http://tapestry.formos.com/projects/tapx/tapx-prototype/
and there it says that it is a patch, the only patch procedure I am aware of
is to take a file and patch it, however I have never done this in java.
So I assume that the only thing to di is to include the jar in the
dependencies?
regards,
Mario
On Tue, Nov 17, 2009 at 8:16 AM, Kalle Korhonen
kalle.o.korho...@gmail.comwrote:
You need to do at least tiny little bit of homework yourself whether
or not you are using Maven. Get the jar from
http://tapestry.formos.com/maven-repository/com/howardlewisship/tapx-prototype/1.0.0/
Kalle
On Mon, Nov 16, 2009 at 10:47 PM, Mario Udina m.ud...@gmail.com wrote:
Hello!
I am not using maven! What do I have to do to use tapx-prototype?
regards,
Mario
On Tue, Nov 17, 2009 at 6:17 AM, Kalle Korhonen
kalle.o.korho...@gmail.comwrote:
There's a known issue with the version of prototype packaged in
T5.1.0.5 and IE8. Are you using the newly released tapx-prototype
already (http://tapestry.formos.com/projects/tapx/)?
Kalle
On Mon, Nov 16, 2009 at 9:10 PM, David Rees dree...@gmail.com wrote:
Anyone else have issues with the new JSON encoding in 5.1?
I upgraded an application when a block is returned that has a
JavaScript link in it with single quotes, IE8 (haven't tested other
versions of IE) puke on it.
For example, this snippet in the block:
a href= onclick=openWindow('winname')Click me/a
Gets returned in T5.1.0.5 as:
a href='' onclick='openWindow(apos;winnameapos)'Click me/a
Gets returned in T5.0.18 as:
a href= onclick=openWindow('winname')Click me/a
Firefox 3.5 handles both OK.
Any work around that people know of off-hand besides going back to
T5.0? Only thing I've found so far is to swap out single/double
quotes in my .tml files like so:
a href= onclick='openWindow(winname)'Click me/a
But that's a major PITA in a large application.
-Dave
-
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
