Oxygen XML Forum

Hello,

I'd like to know if there is a way to customize the Attributes view to remove the Browse Icon which is located on the right of the Value textfield.

In both Desktop version and Author Component applet.

Hi Patrick,

We do not have such API.
When pressed the button shows a Browse dialog.
By using:
You could add a customizer which could maybe remove all actions from the drop down browse button which is present in any Browse dialog or in any dialog which has such URL choosers.

Regards,
Radu

Hi,

I wondered, maybe this customization was implemented in the latest version?

And could somebody be so kindly to explain why this dialog available for all attributes?
Even if it's value is not accepts any custom text, which would be a link.

Thanks, in advance.

Hi Alexey,

Sorry, but we do not have an API for this.
From what you say, you would actually want to disable any kind of editing there.
Could you elaborate a little bit on your use case? So you have an attribute which only accepts values from a fixed list, like an IDREF? And you fear that the user will insert an invalid link, right? Inserting an invalid value should also trigger a validation error.

Regards,
Radu

Hi Radu,

Our case is not what you have described.
I just try to understand why URL selection is enable for every element.

What I actually want is to avoid situation, when user can perform a valid action (click "browse" and type some URL) and then receive the validation error (because value is invalid).
In the case that you have specified (with IDREF) user will have reasonable question: "Why there is a Browse button, if I can't use it?".

Also, I want to make sure that I haven't missed something, and this link is not used to actually get the value (maybe, with some get request like http://www.myCompany.com/getMeAttribute ... utputclass).

Hi Alexey,

I understand your use case, indeed few attribute values actually need such a "Browse" button for selecting a file path. And users might get confused if they see the "Browse" button.
We'll see what we can do, either add some API or perform some kind of auto detection in our code to see if an attribute value actually needs a browse button for faster choosing the path to a resource.

Regards,
Radu