Details
Description
The resource loading strategy for JSP tags could be improved. Currently, if not using Spring MVC resource mapping the developer must manually include the needed CSS, JavaScript and image resources in the application project structure.
The location of the various tag resources also currently lacks a standard structure. For instance, the iscroll.js resource is located under the JSF component resources, and in the ICEmobile Spring MVC demo. It would be better if there were only one location for this resource.
We may also consider a resource loading utility servlet that could be used in straight JSP (non-Spring MVC) environments, so that users are not forced to manually include the resources in their project structure.
It's also a bit odd that the folder name for the skins is 'org.icefaces.component.skins'. We may want to remove the ICEfaces reference here. I think 'skins' would suffice.
The location of the various tag resources also currently lacks a standard structure. For instance, the iscroll.js resource is located under the JSF component resources, and in the ICEmobile Spring MVC demo. It would be better if there were only one location for this resource.
We may also consider a resource loading utility servlet that could be used in straight JSP (non-Spring MVC) environments, so that users are not forced to manually include the resources in their project structure.
It's also a bit odd that the folder name for the skins is 'org.icefaces.component.skins'. We may want to remove the ICEfaces reference here. I think 'skins' would suffice.
Issue Links
- blocks
-
MOBI-260 Identify Improvements in component implementation strategies for multple platforms.
- Closed
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion