[
https://issues.apache.org/jira/browse/DIRSTUDIO-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443222#comment-16443222
]
Stefan Seelmann edited comment on DIRSTUDIO-1177 at 4/18/18 9:47 PM:
---------------------------------------------------------------------
Yes, there exists extension point "org.apache.directory.studio.valueeditors"
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.
was (Author: seelmann):
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)
