[jira] [Commented] (DIRSTUDIO-1177) Enhance default editor mappings for eDirectory/Identity Manager
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16585233#comment-16585233 ] Stefan Seelmann commented on DIRSTUDIO-1177: PR: https://github.com/apache/directory-studio/pull/3 > Enhance default editor mappings for eDirectory/Identity Manager > --- > > Key: DIRSTUDIO-1177 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1177 > Project: Directory Studio > Issue Type: Improvement > Components: studio-ldapbrowser >Affects Versions: 2.0.0-M13 >Reporter: Lothar Haeger >Priority: Minor > > Apache Studio is very popular amongst developers/consultants/admins working > with Novell/NetIQ/Micro Focus Identity Manager (IDM). IDM uses eDirectory as > it's backend data store and has a lot of product-specific attributes in Octet > String syntax that contain XML text. > By default those attribute's contents is displayed in LDAP Browser as "Binary > Data (12345 Bytes)" or similar because the default editor is chosen based on > attribute syntax and does not recognize it's UTF text. A double-click on the > attribute value will open Hex Editor, which then allows to switch to Text > Editor to actually read/edit the value. > I know I can change the default editors in preferences for each of the many > Studio instances I use, but it would be much easier if Studio would default > to the best fitting editor right away. > Here's a visual of the difference: https://youtu.be/azCwgjUOynM > Is there a way to enhance the default attribute-to-editor mapping and tell > Studio to open those approx. 20 attributes with Text Editor immediately? Any > hint on where in the code the default mapping are defined? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DIRSTUDIO-1177) Enhance default editor mappings for eDirectory/Identity Manager
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482415#comment-16482415 ] Stefan Seelmann commented on DIRSTUDIO-1177: I created the plugin structure: https://github.com/apache/directory-studio/commit/390498f4c6aa0666579693d70046e0d15261ef83 > Enhance default editor mappings for eDirectory/Identity Manager > --- > > Key: DIRSTUDIO-1177 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1177 > Project: Directory Studio > Issue Type: Improvement > Components: studio-ldapbrowser >Affects Versions: 2.0.0-M13 >Reporter: Lothar Haeger >Priority: Minor > > Apache Studio is very popular amongst developers/consultants/admins working > with Novell/NetIQ/Micro Focus Identity Manager (IDM). IDM uses eDirectory as > it's backend data store and has a lot of product-specific attributes in Octet > String syntax that contain XML text. > By default those attribute's contents is displayed in LDAP Browser as "Binary > Data (12345 Bytes)" or similar because the default editor is chosen based on > attribute syntax and does not recognize it's UTF text. A double-click on the > attribute value will open Hex Editor, which then allows to switch to Text > Editor to actually read/edit the value. > I know I can change the default editors in preferences for each of the many > Studio instances I use, but it would be much easier if Studio would default > to the best fitting editor right away. > Here's a visual of the difference: https://youtu.be/azCwgjUOynM > Is there a way to enhance the default attribute-to-editor mapping and tell > Studio to open those approx. 20 attributes with Text Editor immediately? Any > hint on where in the code the default mapping are defined? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: [jira] [Commented] (DIRSTUDIO-1177) Enhance default editor mappings for eDirectory/Identity Manager
On 04/19/2018 08:00 AM, Lothar Haeger wrote: >> Stefan Seelmann commented on DIRSTUDIO-1177: >> >> >> Also see https://issues.apache.org/jira/browse/DIRSTUDIO-1002 which proposes >> and implements more eDirectory specific value editors but which would need >> some love. > > I was also thinking along the limes that a separate plugin for edir stuff > would > make sense, great to see there's already some work done to build upon. In > DIRSTUDIO-1002 you offered to create the base plugin structure, can I take you > up on that? Sure, but I probably won't find time within the next 2-3 weeks. Kind Regards, Stefan
Re: [jira] [Commented] (DIRSTUDIO-1177) Enhance default editor mappings for eDirectory/Identity Manager
> Stefan Seelmann commented on DIRSTUDIO-1177: > > > Also see https://issues.apache.org/jira/browse/DIRSTUDIO-1002 which proposes > and implements more eDirectory specific value editors but which would need > some love. I was also thinking along the limes that a separate plugin for edir stuff would make sense, great to see there's already some work done to build upon. In DIRSTUDIO-1002 you offered to create the base plugin structure, can I take you up on that?
[jira] [Commented] (DIRSTUDIO-1177) Enhance default editor mappings for eDirectory/Identity Manager
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443231#comment-16443231 ] Stefan Seelmann commented on DIRSTUDIO-1177: Also see https://issues.apache.org/jira/browse/DIRSTUDIO-1002 which proposes and implements more eDirectory specific value editors but which would need some love. > Enhance default editor mappings for eDirectory/Identity Manager > --- > > Key: DIRSTUDIO-1177 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1177 > Project: Directory Studio > Issue Type: Improvement > Components: studio-ldapbrowser >Affects Versions: 2.0.0-M13 >Reporter: Lothar Haeger >Priority: Minor > > Apache Studio is very popular amongst developers/consultants/admins working > with Novell/NetIQ/Micro Focus Identity Manager (IDM). IDM uses eDirectory as > it's backend data store and has a lot of product-specific attributes in Octet > String syntax that contain XML text. > By default those attribute's contents is displayed in LDAP Browser as "Binary > Data (12345 Bytes)" or similar because the default editor is chosen based on > attribute syntax and does not recognize it's UTF text. A double-click on the > attribute value will open Hex Editor, which then allows to switch to Text > Editor to actually read/edit the value. > I know I can change the default editors in preferences for each of the many > Studio instances I use, but it would be much easier if Studio would default > to the best fitting editor right away. > Here's a visual of the difference: https://youtu.be/azCwgjUOynM > Is there a way to enhance the default attribute-to-editor mapping and tell > Studio to open those approx. 20 attributes with Text Editor immediately? Any > hint on where in the code the default mapping are defined? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DIRSTUDIO-1177) Enhance default editor mappings for eDirectory/Identity Manager
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16443222#comment-16443222 ] Stefan Seelmann commented on DIRSTUDIO-1177: Yes, the is its own extension "org.apache.directory.studio.valueeditors" defined for value editors. Many value edtiors are implementented in the "valueeditors" plugin [https://github.com/apache/directory-studio/tree/master/plugins/valueeditors.] And the mappings from syntax or attribute to the editors are in [https://github.com/apache/directory-studio/blob/master/plugins/valueeditors/plugin.xml,] here or in any other plugin.xml you can define such mappings. > Enhance default editor mappings for eDirectory/Identity Manager > --- > > Key: DIRSTUDIO-1177 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1177 > Project: Directory Studio > Issue Type: Improvement > Components: studio-ldapbrowser >Affects Versions: 2.0.0-M13 >Reporter: Lothar Haeger >Priority: Minor > > Apache Studio is very popular amongst developers/consultants/admins working > with Novell/NetIQ/Micro Focus Identity Manager (IDM). IDM uses eDirectory as > it's backend data store and has a lot of product-specific attributes in Octet > String syntax that contain XML text. > By default those attribute's contents is displayed in LDAP Browser as "Binary > Data (12345 Bytes)" or similar because the default editor is chosen based on > attribute syntax and does not recognize it's UTF text. A double-click on the > attribute value will open Hex Editor, which then allows to switch to Text > Editor to actually read/edit the value. > I know I can change the default editors in preferences for each of the many > Studio instances I use, but it would be much easier if Studio would default > to the best fitting editor right away. > Here's a visual of the difference: https://youtu.be/azCwgjUOynM > Is there a way to enhance the default attribute-to-editor mapping and tell > Studio to open those approx. 20 attributes with Text Editor immediately? Any > hint on where in the code the default mapping are defined? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
