Re: Veltools 1.3 - Showcase Example
Le lundi 11 décembre 2006 à 09:45 -0800, Nathan Bubna a écrit : On 12/9/06, Claude Brisson [EMAIL PROTECTED] wrote: Looks very cool. That's a lot of work! Some remarks: - Alternator: we'd like the hand-made examples to return several values... not that important. not sure i understand... Just that when I give the alternator ['blue','red'], I'd like to see blue, red, blue rather than just blue (that is, it should be evaluated several times). Really not that important. - Date $date.getDay([ ]) $date.getMont([ ]) $date.getYear([ ]) those three methods take a Date argument, so the text field doesn't help much... in fact we should also have string versions for those three methods (that rely on toDate()). actually, those three methods take an Object argument which is automatically fed through toCalendar(Object) which eventually delegates to toDate(Object) whose last resort is parsing the String value of the Object. So, they can be used as is. However, i agree that they're not especially useful like this. i'll drop the quotes around the DateTool function examples. Ok, I browsed the sources too fast. But I did so after having tried 3 or 4 different syntaxes in the field getDay([]), which every newcomer will do as well... This time I tracked the trail to its very end and saw that the default behaviour is to fetch a date time medium format, which means the only string that works is Dec 11, 2006 9:07:05 PM, wich is ok as a default formatting string but not so smart when it comes to parsing... We should include some guessing algorithm, and I'm sure we can easily find a pretty one around there in the apache codebase just waiting for us. - Cookie $cookie.all should be displayed with a #foreach, so that we actually see the cookies. Minor. can do. The CSS layout rocks! Maybe we can use it by default. i guess we could. hadn't really thought about it. Last but not least, this webapp could serve as a basis for testcases. Talking about this, I built a testcase for Velosurf (both whitebox and blackbox using Jetty), so maybe I can work on this for the Tools. interesting idea. would this be automated or automate-able? Could not be more automated. Downloads needed jars, starts Jetty, submits forms, compares results, stops Jetty. And what is cool is that you can manually launch the ant target start-jetty and point your browser to -let's say, localhost:8081, when you need to debug the testcases themselves. It uses HttpUnit to do so. The HttpUnit licence is not an ASF one, but is clearly compatible (never seen a shorter licence: http://httpunit.sourceforge.net/doc/license.html ) and already used by several apache projects. Claude Claude Le vendredi 08 décembre 2006 à 12:02 -0800, Nathan Bubna a écrit : hey folks, you probably noticed that i just checked in a new example app for VelocityTools to replace the layout example. this is something i've been thinking of doing for years, and finally got around to doing. basically, it provides demonstrations (most of which are interactive) of all the Generic and VelocityView tools we have. there is certainly plenty of room for improvement in the usefulness of the examples, but i figured it was time to get it out and see what ya'll think. if some of you were willing to check it out and give it a test run, i'd love to get some feedback. It's easy: - check out the latest revision of VelocityTools from svn - run 'ant showcase' - follow the instructions printed out at the end thanks! p.s. VelocityView and the Generic Tools are largely ready for a 1.3 release. if anyone wants to help me get 1.3 out the door, i'd love some help updating the VelocityStruts dependencies and making sure VelocityStruts is fully compatible with the Struts 1.3.x series. (Marino?) Please note that with Tiles going independent as a TLP and Struts 2.x soon on the way, the future of VelocityStruts beyond VelocityTools 1.3 is very much in question. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Veltools 1.3 - Showcase Example
On 12/11/06, Claude Brisson [EMAIL PROTECTED] wrote: Le lundi 11 décembre 2006 à 09:45 -0800, Nathan Bubna a écrit : On 12/9/06, Claude Brisson [EMAIL PROTECTED] wrote: Looks very cool. That's a lot of work! Some remarks: - Alternator: we'd like the hand-made examples to return several values... not that important. not sure i understand... Just that when I give the alternator ['blue','red'], I'd like to see blue, red, blue rather than just blue (that is, it should be evaluated several times). Really not that important. nah. i'd like to keep the function demos realistic. things like that can go in a full demo at the bottom, such as the ones that IteratorTool or SearchTool have. i've actually been adding a few more of these and will check them in shortly. - Date $date.getDay([ ]) $date.getMont([ ]) $date.getYear([ ]) those three methods take a Date argument, so the text field doesn't help much... in fact we should also have string versions for those three methods (that rely on toDate()). actually, those three methods take an Object argument which is automatically fed through toCalendar(Object) which eventually delegates to toDate(Object) whose last resort is parsing the String value of the Object. So, they can be used as is. However, i agree that they're not especially useful like this. i'll drop the quotes around the DateTool function examples. Ok, I browsed the sources too fast. But I did so after having tried 3 or 4 different syntaxes in the field getDay([]), which every newcomer will do as well... This time I tracked the trail to its very end and saw that the default behaviour is to fetch a date time medium format, which means the only string that works is Dec 11, 2006 9:07:05 PM, wich is ok as a default formatting string but not so smart when it comes to parsing... We should include some guessing algorithm, and I'm sure we can easily find a pretty one around there in the apache codebase just waiting for us. that would be cool. the string - date parsing of DateTool.toDate(Object) is simplistic at best by default. if you use the same format for output and input, then you can configure DateTool to use that as the default. otherwise, you should use DateTool.toDate(String format, Object date) or one of the other toDate() methods. so basically, there's plenty of capability in DateTool, but only limited magic. improvements are welcome! - Cookie $cookie.all should be displayed with a #foreach, so that we actually see the cookies. Minor. can do. The CSS layout rocks! Maybe we can use it by default. i guess we could. hadn't really thought about it. Last but not least, this webapp could serve as a basis for testcases. Talking about this, I built a testcase for Velosurf (both whitebox and blackbox using Jetty), so maybe I can work on this for the Tools. interesting idea. would this be automated or automate-able? Could not be more automated. Downloads needed jars, starts Jetty, submits forms, compares results, stops Jetty. And what is cool is that you can manually launch the ant target start-jetty and point your browser to -let's say, localhost:8081, when you need to debug the testcases themselves. It uses HttpUnit to do so. The HttpUnit licence is not an ASF one, but is clearly compatible (never seen a shorter licence: http://httpunit.sourceforge.net/doc/license.html ) and already used by several apache projects. sounds awesome! i'd definitely be interested in exploring such things. Claude Claude Le vendredi 08 décembre 2006 à 12:02 -0800, Nathan Bubna a écrit : hey folks, you probably noticed that i just checked in a new example app for VelocityTools to replace the layout example. this is something i've been thinking of doing for years, and finally got around to doing. basically, it provides demonstrations (most of which are interactive) of all the Generic and VelocityView tools we have. there is certainly plenty of room for improvement in the usefulness of the examples, but i figured it was time to get it out and see what ya'll think. if some of you were willing to check it out and give it a test run, i'd love to get some feedback. It's easy: - check out the latest revision of VelocityTools from svn - run 'ant showcase' - follow the instructions printed out at the end thanks! p.s. VelocityView and the Generic Tools are largely ready for a 1.3 release. if anyone wants to help me get 1.3 out the door, i'd love some help updating the VelocityStruts dependencies and making sure VelocityStruts is fully compatible with the Struts 1.3.x series. (Marino?) Please note that with Tiles going independent as a TLP and Struts 2.x soon on the way, the future of VelocityStruts beyond VelocityTools 1.3 is very much in question.
Re: Veltools 1.3 - Showcase Example
On 12/10/06, Henning P. Schmiedehausen [EMAIL PROTECTED] wrote: Claude Brisson [EMAIL PROTECTED] writes: p.s. VelocityView and the Generic Tools are largely ready for a 1.3 release. if anyone wants to help me get 1.3 out the door, i'd love some help updating the VelocityStruts dependencies and making sure VelocityStruts is fully compatible with the Struts 1.3.x series. I pimped up the velocity gump build a bit; if it passes the next cycle then I will switch from the packaged struts to struts-action, struts-taglib, struts-tiles dependency; if that passes that should be a good sign that vel-tools works with struts 1.3. thanks! that'll be very helpful. How about releasing a beta to get people ready for this? first i want to upgrade the struts dependencies. right now the build still uses the 1.2.x series. then we'll push a beta out. Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person Open Source Consulting, Development, Design | Velocity - Turbine guy Save the cheerleader. Save the world. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Veltools 1.3 - Showcase Example
Le lundi 11 décembre 2006 à 12:47 -0800, Nathan Bubna a écrit : so basically, there's plenty of capability in DateTool, but only limited magic. improvements are welcome! Ah, one last thing (for now) about the DateTool that I forgot to mention: are we sure we want to keep the jdk zero-based behaviour for the month? If so we should recall that in the docs, rather twice than once... Claude - Cookie $cookie.all should be displayed with a #foreach, so that we actually see the cookies. Minor. can do. The CSS layout rocks! Maybe we can use it by default. i guess we could. hadn't really thought about it. Last but not least, this webapp could serve as a basis for testcases. Talking about this, I built a testcase for Velosurf (both whitebox and blackbox using Jetty), so maybe I can work on this for the Tools. interesting idea. would this be automated or automate-able? Could not be more automated. Downloads needed jars, starts Jetty, submits forms, compares results, stops Jetty. And what is cool is that you can manually launch the ant target start-jetty and point your browser to -let's say, localhost:8081, when you need to debug the testcases themselves. It uses HttpUnit to do so. The HttpUnit licence is not an ASF one, but is clearly compatible (never seen a shorter licence: http://httpunit.sourceforge.net/doc/license.html ) and already used by several apache projects. sounds awesome! i'd definitely be interested in exploring such things. Claude Claude Le vendredi 08 décembre 2006 à 12:02 -0800, Nathan Bubna a écrit : hey folks, you probably noticed that i just checked in a new example app for VelocityTools to replace the layout example. this is something i've been thinking of doing for years, and finally got around to doing. basically, it provides demonstrations (most of which are interactive) of all the Generic and VelocityView tools we have. there is certainly plenty of room for improvement in the usefulness of the examples, but i figured it was time to get it out and see what ya'll think. if some of you were willing to check it out and give it a test run, i'd love to get some feedback. It's easy: - check out the latest revision of VelocityTools from svn - run 'ant showcase' - follow the instructions printed out at the end thanks! p.s. VelocityView and the Generic Tools are largely ready for a 1.3 release. if anyone wants to help me get 1.3 out the door, i'd love some help updating the VelocityStruts dependencies and making sure VelocityStruts is fully compatible with the Struts 1.3.x series. (Marino?) Please note that with Tiles going independent as a TLP and Struts 2.x soon on the way, the future of VelocityStruts beyond VelocityTools 1.3 is very much in question. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Veltools 1.3 - Showcase Example
I've debated that myself a dozen times. The main issue is that i've not had cause to use that particular function myself. I just added the getMonth() and getDay() methods as logical fellows of the getYear() method that i really wanted. I could easily be swayed either direction, and either way, the documentation definitely should be improved. Anyone else have thoughts on this one? I'm actually leaning back toward the normal 1-based month and away from the j.u.Calendar's 0-based month right now. While the DateTool is in the generic package, it's primary use is probably in a view layer of an application, where it is more natural to present the human month value rather than the machine one. On 12/11/06, Claude Brisson [EMAIL PROTECTED] wrote: Le lundi 11 décembre 2006 à 12:47 -0800, Nathan Bubna a écrit : so basically, there's plenty of capability in DateTool, but only limited magic. improvements are welcome! Ah, one last thing (for now) about the DateTool that I forgot to mention: are we sure we want to keep the jdk zero-based behaviour for the month? If so we should recall that in the docs, rather twice than once... Claude - Cookie $cookie.all should be displayed with a #foreach, so that we actually see the cookies. Minor. can do. The CSS layout rocks! Maybe we can use it by default. i guess we could. hadn't really thought about it. Last but not least, this webapp could serve as a basis for testcases. Talking about this, I built a testcase for Velosurf (both whitebox and blackbox using Jetty), so maybe I can work on this for the Tools. interesting idea. would this be automated or automate-able? Could not be more automated. Downloads needed jars, starts Jetty, submits forms, compares results, stops Jetty. And what is cool is that you can manually launch the ant target start-jetty and point your browser to -let's say, localhost:8081, when you need to debug the testcases themselves. It uses HttpUnit to do so. The HttpUnit licence is not an ASF one, but is clearly compatible (never seen a shorter licence: http://httpunit.sourceforge.net/doc/license.html ) and already used by several apache projects. sounds awesome! i'd definitely be interested in exploring such things. Claude Claude Le vendredi 08 décembre 2006 à 12:02 -0800, Nathan Bubna a écrit : hey folks, you probably noticed that i just checked in a new example app for VelocityTools to replace the layout example. this is something i've been thinking of doing for years, and finally got around to doing. basically, it provides demonstrations (most of which are interactive) of all the Generic and VelocityView tools we have. there is certainly plenty of room for improvement in the usefulness of the examples, but i figured it was time to get it out and see what ya'll think. if some of you were willing to check it out and give it a test run, i'd love to get some feedback. It's easy: - check out the latest revision of VelocityTools from svn - run 'ant showcase' - follow the instructions printed out at the end thanks! p.s. VelocityView and the Generic Tools are largely ready for a 1.3 release. if anyone wants to help me get 1.3 out the door, i'd love some help updating the VelocityStruts dependencies and making sure VelocityStruts is fully compatible with the Struts 1.3.x series. (Marino?) Please note that with Tiles going independent as a TLP and Struts 2.x soon on the way, the future of VelocityStruts beyond VelocityTools 1.3 is very much in question. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Velocity Site - Preview
Interesting. I like the look and feel. I've got lots of comments on the content. But I'm going to send them tomorrow when I'm more awake. WILL On 12/11/06, Henning P. Schmiedehausen [EMAIL PROTECTED] wrote: [Hm. I could have sworn I've sent this out already. Seems it never made it] To let you know what I've been busy over the weekend: I've been wrestling with maven 2 and site building. A preview of where I intent to go is currently visible at http://velocity.apache.org/staging/ Comments, Criticism, Help, Patches wanted. Most of that is already in the site svn; I've created a custom skin for the site, that is not yet there. Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person Open Source Consulting, Development, Design | Velocity - Turbine guy Save the cheerleader. Save the world. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
