https://bitbucket.org/idempiere/idempiere/changeset/74c82bdd8866
https://bitbucket.org/idempiere/idempiere/changeset/7e11b8c18010
https://bitbucket.org/idempiere/idempiere/changeset/06c644e762d9

Hi Carlos,

Thanks for the scripts.
I've started to work on a generic method and it seems to work !

Please find attached:

• new X and I classes

• MToolBarButtonRestrict (full class)

• APanel (patch)

• migration scripts (which contain minor modifications to AD_ToolBarButtonRestrict table)

Please review.

I'll start my own fork later (tbayen say he will try to write some documentation, so i'll follow it).

Now, let's talk about 'ToolBar button' window.

I'm not sure that making Classname mandatory is a good thing.
For instance, 'Print' is common to APanel, Viewer and CWindowToolbar
So, if we want to forbid people to print through the whole application, it should be done with a blank Classname field (one record is better than 3 ?)

WDYT ?

Regards,

Nicolas

Hi Nicolas

According to what we agreed on weekly meeting ( http://bit.ly/H0VwR8 ) I'm uploading the scripts for the creation of the tables AD_ToolBarButton and AD_ToolBarButtonRestrict - and also the initial records for swing window toolbar and zk window toolbar.

Regards,

Carlos Ruiz

Transcribing here the summary of what was discussed on weekly meeting http://goo.gl/NWoql

Create a table AD_VisualComponent
Columns: the usual plus

• VisualGroup for "Toolbar Window", "Toolbar Report Viewer", "Toolbar Jasper Viewer", "About window", "Other window components" (like the record info button)

• SeqNo

• Name

• Component Type

• Java class (to implement some sort of configurable interface in future)

Create a table AD_VisualComponentRestrict - to register restrictions per role
Columns: the usual plus

• AD_VisualComponent_ID

• AD_Role_ID

Regards,

Carlos Ruiz