[jira] Updated: (TAP5-697) Tapestry_improvement_ideas

2009-05-14 Thread Tam Du (JIRA)

 [ 
https://issues.apache.org/jira/browse/TAP5-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tam Du updated TAP5-697:


Summary: Tapestry_improvement_ideas  (was: Tapestry_improment_ideas)

 Tapestry_improvement_ideas
 --

 Key: TAP5-697
 URL: https://issues.apache.org/jira/browse/TAP5-697
 Project: Tapestry 5
  Issue Type: Improvement
  Components: tapestry-core
Affects Versions: 5.1.0.5, 5.0.18
Reporter: Tam Du

 During the time using Tapestry, I found some feature can be improved for 
 Tapestry. Here they are:
 1.In the tml file, we should not disable html the second time, that is, 
 if it is already disabled, then should not disable again. For more details, I 
 attach here my file DisableHTMLTag.java which I have been using to not 
 disable html the second time. I hope that you can improve this feature in the 
 next version.
 2.When using Grid component of Tapestry, I found that we should have an 
 option to display/not display the header of the Grid. The reason of this 
 requirement is: when developing my product, in some cases, I need to use Grid 
 but I don't want to display the header of that grid. 
 For example, I use Tapestry to write the list topic page 
 http://62.101.68.227:/snippetrepobrowser/, the header of Grid is 
 unnecessary.
 3.In the current version of Tapestry framework, I can only configure my 
 project in only one .properties file. This is no problem with a simple 
 project but with a complex project which requires other projects. In complex 
 projects, I must copy/paste keys in properties file from one project to 
 another. It makes me hard to maintain and manage my projects as well as my 
 products. So, I hope that Tapestry can support multi properties file in each 
 project (especially in the complex projects).
 For example:
 I have this code to set the value of key APPLICATION_ CATALOG in file 
 í8n.properties
  configuration.add (SymbolConstants.APPLICATION_CATALOG, 
 WEB-INF/classes/i18n/i18n.properties); 
 I would like to set the value of key APPLICATION_CATALOG in other file 
 properties, like this:
  configuration.add (SymbolConstants.APPLICATION_CATALOG, 
 WEB-INF/classes/i18n/i18n.properties; 
 WEB-INF/classes/i18n/i18n_vn.properties;);
 4. I use Tapestry and Flex Blaze-DS to develop my project. Current 
 TapestryFilter class filters not only Tapestry patterns but also Flex 
 Blaze-DS patterns. I think it had better have an option so that we can 
 control what Tapestry filters.  In this case, I suggest that we need to 
 improve TapestryFilter class for the purpose of ignoring any patterns that 
 developers don't want Tapestry to filter.
 For example: I want TapestryFilter ignore some patterns which contain string 
 /messageBroker/. The source code may be like this:
 filter
   filter-nameapp/filter-name
   filter-classorg.apache.tapestry5.TapestryFilter/filter-class
   ignore-pattern/messageBroker//ignore-pattern 
 /filter
 5.I request this feature for purpose of the security of website. 
 Currently, I found that users can download tml files by putting .tml at the 
 end of URL. Users can do like that because .tml files are put in the webroot 
 folder of the project. To prevent download, I have 2 solutions for this case:
  Solution 1:   .tml files can be saved anywhere in project, and Tapestry 
 will support the configuration to determine where to save these files.
  Solution 2:   Save tml file in the WEB_INF folder of project.
 I hope that Tapestry will be improved these features. 
 Thank you very much.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (TAP5-697) Tapestry_improvement_ideas

2009-05-14 Thread Tam Du (JIRA)

 [ 
https://issues.apache.org/jira/browse/TAP5-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tam Du updated TAP5-697:


Description: In the tml file, we should not disable html the second time, 
that is, if it is already disabled, then should not disable again. For more 
details, I attach here my file DisableHTMLTag.java which I have been using to 
not disable html the second time. I hope that you can improve this feature in 
the next version.  (was: During the time using Tapestry, I found some feature 
can be improved for Tapestry. Here they are:
1.  In the tml file, we should not disable html the second time, that is, 
if it is already disabled, then should not disable again. For more details, I 
attach here my file DisableHTMLTag.java which I have been using to not 
disable html the second time. I hope that you can improve this feature in the 
next version.

2.  When using Grid component of Tapestry, I found that we should have an 
option to display/not display the header of the Grid. The reason of this 
requirement is: when developing my product, in some cases, I need to use Grid 
but I don't want to display the header of that grid. 
For example, I use Tapestry to write the list topic page 
http://62.101.68.227:/snippetrepobrowser/, the header of Grid is 
unnecessary.

3.  In the current version of Tapestry framework, I can only configure my 
project in only one .properties file. This is no problem with a simple 
project but with a complex project which requires other projects. In complex 
projects, I must copy/paste keys in properties file from one project to 
another. It makes me hard to maintain and manage my projects as well as my 
products. So, I hope that Tapestry can support multi properties file in each 
project (especially in the complex projects).
For example:
I have this code to set the value of key APPLICATION_ CATALOG in file 
í8n.properties
 configuration.add (SymbolConstants.APPLICATION_CATALOG, 
WEB-INF/classes/i18n/i18n.properties); 
I would like to set the value of key APPLICATION_CATALOG in other file 
properties, like this:
 configuration.add (SymbolConstants.APPLICATION_CATALOG, 
WEB-INF/classes/i18n/i18n.properties; 
WEB-INF/classes/i18n/i18n_vn.properties;);

4.   I use Tapestry and Flex Blaze-DS to develop my project. Current 
TapestryFilter class filters not only Tapestry patterns but also Flex Blaze-DS 
patterns. I think it had better have an option so that we can control what 
Tapestry filters.  In this case, I suggest that we need to improve 
TapestryFilter class for the purpose of ignoring any patterns that developers 
don't want Tapestry to filter.
For example: I want TapestryFilter ignore some patterns which contain string 
/messageBroker/. The source code may be like this:
filter
  filter-nameapp/filter-name
  filter-classorg.apache.tapestry5.TapestryFilter/filter-class
  ignore-pattern/messageBroker//ignore-pattern 
/filter

5.  I request this feature for purpose of the security of website. 
Currently, I found that users can download tml files by putting .tml at the 
end of URL. Users can do like that because .tml files are put in the webroot 
folder of the project. To prevent download, I have 2 solutions for this case:
 Solution 1:   .tml files can be saved anywhere in project, and Tapestry 
will support the configuration to determine where to save these files.
 Solution 2:   Save tml file in the WEB_INF folder of project.

I hope that Tapestry will be improved these features. 
Thank you very much.
)

 Tapestry_improvement_ideas
 --

 Key: TAP5-697
 URL: https://issues.apache.org/jira/browse/TAP5-697
 Project: Tapestry 5
  Issue Type: Improvement
  Components: tapestry-core
Affects Versions: 5.1.0.5, 5.0.18
Reporter: Tam Du
 Attachments: DisableHtmlTag.java


 In the tml file, we should not disable html the second time, that is, if it 
 is already disabled, then should not disable again. For more details, I 
 attach here my file DisableHTMLTag.java which I have been using to not 
 disable html the second time. I hope that you can improve this feature in the 
 next version.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.