Karl Dattar wrote:
> 
> Example:
> Our documentation consists of a System Guide, User Guide and Sample Guide.
> For each of document, there is a different customize.xxe file.  So we have
> a customize_1.xxe,  customize_2.xxe, customize_3.xxe files that is stored
> in
> C:\Documents and Settings\user\Application Data\XMLmind\XMLEditor\
> 
> Whenever we need to regenerate a document into PDF, we have to :
> 1. Go to directory
> C:\Documents and Settings\user\Application Data\XMLmind\XMLEditor\
> 2. Copy file customize_1.xxe to customize.xxe
> 3. Restart xmleditor
> 
> Is there any way to specify the location or name of the file customize.xxe
> on startup of xmleditor 

No.


> or change the customize.exe to use when inside
> xmleditor.

No.



> 
> Ideally, I would like to store the customize.xxe for each project with the
> xml documents in the project directory so that when we checkin/checkout
> from source control, we are not missing the correct customize.xxe for each
> documentation project.
> 

I'm sorry but I don't see any way to do this.

However, I would suggest to:

[1] To remove customize_1.xxe,  customize_2.xxe, customize_3.xxe from
each user's preferences directory addon\ subdirectory and from XXE's
system addon\ subdirectory.

[2] To put customize_1.xxe,  customize_2.xxe, customize_3.xxe in 3
different directory located on a file share accessible by all users.
Let's call these directories Z:\shared\xxe1, xxe2, xxe3.

[3] To use the  XXE_ADDON_PATH environment variable to point to the
right customization directory.

Example:

C:\> set XXE_ADDON_PATH=Z:\shared\xxe3

If you start XXE normally after that, it will automatically use
Z:\shared\xxe3\customize_3.xxe

Not elegant but better that nothing.

More information in "The lookup phase during XXE startup", "XMLmind XML
Editor - Configuration and Deployment",
http://www.xmlmind.com/xmleditor/_distrib/doc/configure/lookup_phase.html

---
PS: I've rerouted this question and its answer to the xmleditor-support
public mailing list as it is of general interest.






Reply via email to