Hello Kohei,
Hi Andreas,
On 11/8/06, Andreas Schlüns <[EMAIL PROTECTED]> wrote:
b)
Patching the menu.xml file of the calc module directly. Because such job
will be used everytime the event is triggered and it will be called
everytime during startup of the office it can be a performance issue.
Because you patch already the calc source directly using a build flag,
you should do the same with corresponding menu.xml file. It should be
easy to diplicate the orginal file and deploy/pack it instead of using
the original file.
This way is easier and more simple.
I agree. I was coming to the same conclusion myself. This is
probably simpler and better way to go.
Smal hint: the maintenance of two source files (meaning the same but
slightly different) can be a problem. Might be those two files will run
out of sync during the next time. May be you should also think about a
small "build helper tool", which can merge two text files together.
It's not needed to use a full featured xml parser/generator here.
Copying text fragments should be enough.
E.g:
file_1.xml (contains all shared UI elements)
file_2.xml (contains the normal calc elements)
file_3.xml (contains your set of elements)
normal_calc_ui.xml = file_1+file_2
your_calc_ui.xml = file_1+file_3
If you need an example of these ... please have a look on the set of
makefiles inside cvs directory "filter/source/config/fragments/". My
filter configuration is also generated from a set of xml fragments. I
wrote a tool (merging list of files together) in java
("filter/source/config/tools"). It cant be used directly for your use
case ... but might be give you an idea - how it can work (e.g. the
makefile handling).
Thanks for your suggestion, Andreas.
Kohei
Best Regards
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
