Hello Sunny,
Here it goes, another idea...
Ok, you posted about the special attributes in wich we can control how the XML editor behaves.
"It has a couple unpublished tricks as well. You can place special attributes in your XML file to control the way the XML Editor functions. For example,
<link __hide="true">home</link> will hide the node contents from the Editor.
__label="text label" use specified text as label
__up="false" no move "Up" option for node
__down="false" no move "Down" option for node
__duplicate="false" no "Copy" option for node
__delete="false" no "Delete" option for node
__hide="true" hide node contents from editor"And I just got this idea, to add another attribute to the list.
Let me explain. When editing content with the XML editor for a custom module, its not so user friendly to have to write a path to a file, like a path to a picture. One could spell the filename wrong and not see an image displayed on a picture gallery for example. It would be so much effective to browse to the location of the file and update the filename on a XML node.
One doesn't have to worry about a node that displays text but rather paths to files. However the browse method might be, filetree or thumbnail browser...
the idea is to be able to control wich node content can be browsed by enabling it through a special attribute set to true.
Example
<image __browse="true">earth purple.jpg</image>
Then maybe see a "browse" boton next to the node on the XML editor.
I illustrated the idea in the following screenshot

One could make a custom editor for a module, but then again... the XML editor is already so versatile.