Posted by
Adrian Crum on
URL: http://ofbiz.116.s1.nabble.com/Dev-configurable-custom-views-tp167905p167927.html
Sure.
Also, someone asked me privately about the implementation, so I'll C&P it here...
I modified header.ftl to support alternative style sheets. If an alternative
style sheet is in the environment, then the maincss.css is disabled and the
alternative is used.
I copied and modified the maincss.css file to create different themes. One css
file for each theme.
I set up a "Workspace Manager" web page where the user can select from a list of
themes. The web page stores their selection in the user setting entity.
I modified the GlobalDecorator so that it calls an action that gets the user's
current theme from the user setting entity and puts it in the environment.
Some of this was submitted in Jira 174. That Jira issue is kinda outdated now,
but the changes I made to header.ftl will still work.
Si Chen wrote:
> Maybe . . . Can you create a JIRA issue for it?
>
> Adrian Crum wrote:
>
>>We implemented UI themes that users can choose from. Maybe some of that work
>>could be helpful.
>>
>>
>>
>>Si Chen wrote:
>>
>>
>>
>>>Hi everybody -
>>>
>>>We want to implement a feature where users can configure their view
>>>choices in the applications. For example, the same page can serve up
>>>different content, etc. I think this would have to be implemented
>>>specifically in each application, but nevertheless a common data model
>>>for all of them might be nice.
>>>
>>>My questions:
>>>
>>>1. Is this something we want in OFBIZ?
>>>
>>>2. If so, here's what I have so far
>>>ViewPreference: header entity with an ID, description, etc.
>>>ViewPreferenceItem consisting of viewPrefId, component, view, item (FK
>>>on enum)
>>>ViewPreferenceEnums is a list of allowable choices for all the view
>>>preferences
>>>UserLoginViewPreference - allows userLogin to be associated with a view
>>>preference
>>>
>>>Does this sound reasonable?
>>>
>>>Where I'm a little hazy is how ViewPreferenceItem should be. Should be
>>>structured around application compnent and view-request, or around
>>>screens and sub-screens, or form/fields? Or should we have something
>>>that would allow all of the above, so users can configure any of those?
>>>
>>>Thanks,
>>>
>>>Si
>>>
>>>
>>>_______________________________________________
>>>Dev mailing list
>>>
[hidden email]
>>>
http://lists.ofbiz.org/mailman/listinfo/dev>>>
>>>
>>>
>>
>>_______________________________________________
>>Dev mailing list
>>
[hidden email]
>>
http://lists.ofbiz.org/mailman/listinfo/dev>>
>>
>>
>>
>
> ------------------------------------------------------------------------
>
>
> _______________________________________________
> Dev mailing list
>
[hidden email]
>
http://lists.ofbiz.org/mailman/listinfo/dev_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev