[
https://issues.apache.org/jira/browse/OFBIZ-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443216#comment-15443216
]
Taher Alkhateeb commented on OFBIZ-5776:
----------------------------------------
This is an area too big for me to tackle at the moment, but in my opinion web
resources should be in fact completely outside of the framework. Perhaps a
better place is the themes directory. Here are a few thoughts on why this
should be the case:
- The widget system is designed to be technology independent (is not specific
to html). So the skinning, UI behavior and layout, should as much as possible
be a deferred decision (right before painting). For example If I want a button
to glow upon hovering, I should add that to the widget DSL and translate it at
the very last second.
- Even if we introduce a non-pure widget (<platform-specific><html>...) then
the translation of that UI is also a last minute decision happening in the
templates / rendering engine.
So in summary, nothing "Web-specific UI" should reside in the framework. The
framework is the infrastructure tools and low level components (servlets,
entity engine, service engine, scripting, DSLs, widget engine, routing, etc
...) and never things like UI.
If we are going to go through the pain of renaming, refactoring, and fixing all
the links, we might as well do this properly by keeping the framework lean, and
anything that gets painted should go IMO to /themes somewhere. Perhaps we can
have a base theme that holds all the things that other themes extend from.
> Move static resources from framework/images to framework/resources webapp
> -------------------------------------------------------------------------
>
> Key: OFBIZ-5776
> URL: https://issues.apache.org/jira/browse/OFBIZ-5776
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: Trunk
> Reporter: Deepak Dixit
> Assignee: Deepak Dixit
> Priority: Minor
> Attachments: OFBIZ-5776.patch
>
>
> Move all the static resources form images webapp to resources webapp, as they
> all are more related to resources rather then images.
> Also we need to rearrange these resources based on their purpose, like
> - Move all js related files and plugins under resources/js
> - Move all the css related files and plugins under resources/css
> - Move all the images related to js and css under resources/images or
> resources/img
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
