[jira] Created: (VELOCITY-572) Need to make escaping examples more clear
Need to make escaping examples more clear - Key: VELOCITY-572 URL: https://issues.apache.org/jira/browse/VELOCITY-572 Project: Velocity Issue Type: Improvement Components: Documentation Reporter: Spencer Davis The examples for escaping could be changed to make it easier to understand for newcomers. It would be better if there was an example showing how to escape (with one backslash) and then move on to the more complicated examples. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (VELOCITY-573) Combine the two sections about escaping
Combine the two sections about escaping --- Key: VELOCITY-573 URL: https://issues.apache.org/jira/browse/VELOCITY-573 Project: Velocity Issue Type: Improvement Components: Documentation Reporter: Spencer Davis It would make more sense to just have one section of the User Guide about escaping. The two sections, Escaping Valid VTL References and Escaping VTL Directives should be combined into one section where the Escaping VTL Directives section is now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (VELOCITY-574) VTL Comment Blocks description is not clear
[ https://issues.apache.org/jira/browse/VELOCITY-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Spencer Davis updated VELOCITY-574: --- Description: The User Guide says: There is a third type of comment, the VTL comment block, which may be used to store such information as the document author and versioning information: #** This is a VTL comment block and may be used to store such information as the document author and versioning information: @author @version 5 *# The description only says that it can be used to store the information but not why you would want to store the information or how it could be used. Also, the examples should either show more of how it is used or there should be an explanation of how to use @author and @version. was: The User Guide says: There is a third type of comment, the VTL comment block, which may be used to store such information as the document author and versioning information: #** This is a VTL comment block and may be used to store such information as the document author and versioning information: @author @version 5 *# The description only says that it can be used to store the information but not why you would want to store the information or how it could be used. Also, the examples should either show more of how it is used or there should be an explanation of how to use them. VTL Comment Blocks description is not clear --- Key: VELOCITY-574 URL: https://issues.apache.org/jira/browse/VELOCITY-574 Project: Velocity Issue Type: Improvement Components: Documentation Reporter: Spencer Davis Priority: Minor The User Guide says: There is a third type of comment, the VTL comment block, which may be used to store such information as the document author and versioning information: #** This is a VTL comment block and may be used to store such information as the document author and versioning information: @author @version 5 *# The description only says that it can be used to store the information but not why you would want to store the information or how it could be used. Also, the examples should either show more of how it is used or there should be an explanation of how to use @author and @version. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (VELOCITY-575) Shorthand Notation should be called regular notation
Shorthand Notation should be called regular notation Key: VELOCITY-575 URL: https://issues.apache.org/jira/browse/VELOCITY-575 Project: Velocity Issue Type: Improvement Components: Documentation Reporter: Spencer Davis Priority: Minor In the User Guide, it shows the shorthand notation for references but does not mention any other notation until the section about formal notation. In the VTL Reference, it calls the same notation regular notation. The User Guide should be changed so that it is consistent with the reference. This also prevents confusion about calling it shorthand without mentioning any other notations until much later on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (VELOCITY-572) Need to make escaping examples more clear
[ https://issues.apache.org/jira/browse/VELOCITY-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Spencer Davis updated VELOCITY-572: --- Comment: was deleted Need to make escaping examples more clear - Key: VELOCITY-572 URL: https://issues.apache.org/jira/browse/VELOCITY-572 Project: Velocity Issue Type: Improvement Components: Documentation Reporter: Spencer Davis The examples for escaping could be changed to make it easier to understand for newcomers. It would be better if there was an example showing how to escape (with one backslash) and then move on to the more complicated examples. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (VELOCITY-572) Need to make escaping examples more clear
[ https://issues.apache.org/jira/browse/VELOCITY-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Spencer Davis updated VELOCITY-572: --- Description: In the User Guide, the examples for escaping could be changed to make it easier to understand for newcomers. It would be better if there was an example showing how to escape (with one backslash) and then move on to the more complicated examples. was: The examples for escaping could be changed to make it easier to understand for newcomers. It would be better if there was an example showing how to escape (with one backslash) and then move on to the more complicated examples. Need to make escaping examples more clear - Key: VELOCITY-572 URL: https://issues.apache.org/jira/browse/VELOCITY-572 Project: Velocity Issue Type: Improvement Components: Documentation Reporter: Spencer Davis In the User Guide, the examples for escaping could be changed to make it easier to understand for newcomers. It would be better if there was an example showing how to escape (with one backslash) and then move on to the more complicated examples. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (VELOCITY-576) he section about all variables being converted to strings should
he section about all variables being converted to strings should - Key: VELOCITY-576 URL: https://issues.apache.org/jira/browse/VELOCITY-576 Project: Velocity Issue Type: Improvement Components: Documentation Reporter: Spencer Davis Priority: Minor In the References section of the User Guide it says: Everything coming to and from a reference is treated as a String object. If there is an object that represents $foo (such as an Integer object), then Velocity will call its .toString() method to resolve the object into a String. This would make more sense if it was at the end of the section on references so that the different types of objects are introduced before this is. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Logo Proposition for VelocityTools
Hey Edward, That's a pretty good start, though i confess that it took me a second to realize that the symbol was a V with a T inset. The T is particularly hard to recognize. Still, the symbol looks a lot snazzier than the current meager wrench (no offense, if you're still out there Tim Colson :). I do think the color scheme could use some adjustment to fit better, as it clashes a bit right now. I attached a screenshot of this draft logo in the velocitytools docs to show that. I think that's it for stylistic feedback. I'm not really the best at that. Functionally, the logo will need to be smaller and could probably stand to have some of the surrounding whitespace reduced to make better use of its space. Thanks for working on this! I'm excited to have a nice logo for once! :) peace, nathan On Dec 11, 2007 7:17 PM, Edward [EMAIL PROTECTED] wrote: Hello All, I entered the Google Highly Open Participation Contest for the Velocity Tools logo. Here is my proposition so far: [image: ApacheVelocityTools.png picture by shadowpwner] In case the image doesn't show: http://i226.photobucket.com/albums/dd53/shadowpwner/ApacheVelocityTools.png Please note this will not be the final draft, but only something to start us off with. Please give helpful comments and suggestions, to improve my work. (Example: Too simple, colors don't match layout, etc.) Regards, Edward http://code.google.com/p/google-highly-open-participation-asf/issues/detail?id=52 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (VELOCITY-577) reload template by programming
reload template by programming -- Key: VELOCITY-577 URL: https://issues.apache.org/jira/browse/VELOCITY-577 Project: Velocity Issue Type: Wish Affects Versions: 1.5 Reporter: nguyen thanh tam Dear developers I have a problem when using VelocityEngine to merge template. I want to reload template when i merge it with context every times. but VelocityEngine just merge the cached template for the first time. I dont know anyway to do this. So you can help me. and show me the way to reload template by programming. PS: I put template files in classpath, and i set no cache when init VelocityEngine. Thanks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]