John L. Clark wrote:
> I think it would be useful if the XMLmind XML Editor (XXE) had a
> facility for remembering commonly used or inserted characters (from its
> 'Characters' panel) somewhere in the user interface.  I imagine this
> could either be automatically generated ("top 256 of your most-used
> characters", "256 of your last-used characters", or both) or manually
> populated (right click on a character and add it to "custom" character
> list).  I desire this simply for easy access to a Unicode subset to
> which a user often refers.  I know that I often use some greek
> characters, some special punctuation, some arrows, and a few
> mathematical symbols quite often, and I'd love to have a single palette
> for this handy Unicode subset.

This is a very good idea. It is too late to implement it for V2.10 but 
you'll probably have it in V2.11.

We cannot have this kind of idea because, here at XMLmind, we almost 
never use the Character tool. We use this alternative:

---
   <!-- ===============================================================
       Inserts at caret position a character specified using
       its entity name.

       Add parameter="[DocBook]" to use the character entities defined
       in the DocBook 4.2 DTD, whatever is the DTD/Schema of the document
       being edited.
   ================================================================= -->

   <binding>
     <keyPressed code="ESCAPE" />
     <charTyped char="C" />
     <command name="insertCharByName" />
   </binding>
---



> As an added bonus, it'd be great to have a way to assign a keyboard
> shortcut to insert a (user-defined) few specific characters.  Actually,
> this is probably possible using the insertString command[0], although
> it's a bit hard for users to customize this from a nice user interface.
> And I just went and played with it, and even this isn't completely true,
> because I remembered that editing XXE configurations with XXE is
> actually not too bad. 

This kind of feature -- *simple* customizations by the end user without 
having to edit configuration files -- is planned for V3. (V2.10, 2.11, 
2.12 are steps toward V3.)



Reply via email to