Hi Dev-people
A thing I would like to make it into the module-API for 2.0 is a way to allow module-developers to store different preferences for different users/groups. This would allow, as it mostly my concern, for different toolbarsettings in wysiwyg for different kinds of users. But probably other module could benifit as well. I should make it clear that I think it should be a new set of API-methods, not breaking backwards compatibility, but simply allowing module-devs to add more finegrained features to their module, where they find it fitting.
I see 2 approaches:
1. Simple version: Make some functions allowing preferences to be set/get for EITHER specific users or groups (we should decide which) overriding general preferences, should these exist.
2. Advanced version: Doing a preference profile-system, where profiles can be maintained, groups set to override default profile, and users be set to override groups and default profile. Of course a "default" profile should exist from the start and both new groups and users be set to user the defaults, making sure that nothing is required of users not wanting to think of this kind of finegrainedness... this requires some DB-additions, though...
Any thoughts about this?
I'll gladly put some work into this for 2.0.
Regards
Silmarillion
Per user/groups module-preferences for 2.0?
-
Silmarillion
- Dev Team Member
- Posts: 483
- Joined: Sun Jan 02, 2005 9:10 pm
- Location: Denmark
-
Duketown
Re: Per user/groups module-preferences for 2.0?
Silmarillion,
It is not entirely clear to me, but I take it that you also mean to store per user what the selection, sort criteria are per module. Such as the in the news module. The first tab is about the articles. One can change the category, use the submit button to have the query run. Once one is going to another module and comes back, the earlier change to the category is not saved and retrieved.
It would speed up things and make work for the user more efficient. Developers like me could use it in their module as well. As a matter of fact, I would use it in both the modules that I'm currently solely responsible for.
It is not entirely clear to me, but I take it that you also mean to store per user what the selection, sort criteria are per module. Such as the in the news module. The first tab is about the articles. One can change the category, use the submit button to have the query run. Once one is going to another module and comes back, the earlier change to the category is not saved and retrieved.
It would speed up things and make work for the user more efficient. Developers like me could use it in their module as well. As a matter of fact, I would use it in both the modules that I'm currently solely responsible for.
