Download
2012-06-02, 06:06:11
Feature 1
Scan the plugins global for all registered menu hooks and provide options to disable any sidemenu or tab registered via a user permissions control.
Feature 2
Create a global array of known items to hide and their jquery patterns/hook patterns/querystring patterns.
Plugins can add their own to this and users can enabled them as checkboxesor what not.
Global would be an array of ojbects or named arrays.
application,
filtername,
filtertype,
pattern
you can match applications and enable all group by application
you can match by application filter name and group as a client side and server side filters pair.
Feature 3
A user permissions global can be made available and accessed by plugins to check their own security during execution to avoid need for client side hiding hacks.
Further Details
I have been engineering this for a few months now, don't have any code written though.
details on mask array would be something like.
A nested assoc array might be easier to scan by index
but for doc sake.
You can see how you could loop the groups for application, filtername with this and provide a hierarchical selection.
filterypes would be say
'jquery' or 'client'
'querystring' or 'server'
'bool' ( for built in plugin evaluations in its code, no pattern for this )
'sidemenu'
'tab'
Oh and users can easily edit this and add their own or contribute or share security sets for entire plugins.
You can also control some stuff by removing hooks from the plugins array directly.
And please implement my super user feature I posted about, and maybe a way to disable multi user login when plugin is off or removed. ( I posted details on these in another post while back)
Scan the plugins global for all registered menu hooks and provide options to disable any sidemenu or tab registered via a user permissions control.
Feature 2
Create a global array of known items to hide and their jquery patterns/hook patterns/querystring patterns.
Plugins can add their own to this and users can enabled them as checkboxesor what not.
Global would be an array of ojbects or named arrays.
application,
filtername,
filtertype,
pattern
you can match applications and enable all group by application
you can match by application filter name and group as a client side and server side filters pair.
Feature 3
A user permissions global can be made available and accessed by plugins to check their own security during execution to avoid need for client side hiding hacks.
Further Details
I have been engineering this for a few months now, don't have any code written though.
details on mask array would be something like.
A nested assoc array might be easier to scan by index
but for doc sake.
Code:
application name => theplugin,
filtername => allowadd,
filtertype => jquery,
pattern => '$(#theplugin_add_button)'
application name => theplugin,
filtername => allowadd,
filtertype => query,
pattern => 'action=add'
OR
array['theplugin']['allowadd']['jquery']='$(#theplugin_add_button)';
array['theplugin']['allowadd']['query'] = 'action=add';You can see how you could loop the groups for application, filtername with this and provide a hierarchical selection.
filterypes would be say
'jquery' or 'client'
'querystring' or 'server'
'bool' ( for built in plugin evaluations in its code, no pattern for this )
'sidemenu'
'tab'
Oh and users can easily edit this and add their own or contribute or share security sets for entire plugins.
You can also control some stuff by removing hooks from the plugins array directly.
And please implement my super user feature I posted about, and maybe a way to disable multi user login when plugin is off or removed. ( I posted details on these in another post while back)
