http://ofbiz.116.s1.nabble.com/Dev-configurable-custom-views-tp167905p167906.html
This could be something of interest in the project. I've certainly heard questions about things like this over the years...
Stepping back a little from the implementation: what types of things would the user be able to configure? You mentioned different content, and I've heard requests for things like custom fields on a form, or removing fields, or even going as far as "user configurable reports" and the like. I think a lot of this stems from what some applications do to make these sorts of changes easier, and in some cases this is the _only_ way to change the apps, so people get really hung up about it and aren't sure what to think when it is not included in something like OFBiz.
> 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