sumanto
9th October 2002 15:11 UTC
XML editing in NSIS
:( I am in bit of a soup and need help.
Is there any simple way of editing XML configuration files in NSIS? :rolleyes:
Also, is there any way to add a task to the scheduled tasks during installation itself using NSIS?
Any help will be very welcome.
Thanks :up:
kichik
9th October 2002 16:26 UTC
Unless someone made an XML plugin and didn't tell us, there is no easy way of editing XML in NSIS.
I will check about that scheduled tasks and get back to you.
sala
24th September 2003 14:56 UTC
Originally posted by kichik
Unless someone made an XML plugin and didn't tell us, there is no easy way of editing XML in NSIS.
I will check about that scheduled tasks and get back to you.
Is there any progress with that xml plugin?
kichik
24th September 2003 15:13 UTC
One was never started as far as I know.
Sumanto, I am sorry about not getting back to you about the scheduled tasks. Here's a link that should help:
http://forums.winamp.com/showthread....highlight=task
sala
24th September 2003 15:23 UTC
To edit xml I use gsar by just executing it with command line (but this is realy dirty way!).
http://sourceforge.net/project/showf...lease_id=62659
b_avery@yahoo.c
6th April 2004 16:19 UTC
Has a plug in been created yet, for editing XML files?
Joost Verburg
6th April 2004 17:11 UTC
Nope
sealite
16th November 2004 10:31 UTC
Still no plugin ?
XML is going to replace (most of) registry in the near future. Most multi platform application are already using xml for storing configuration.
Joel
16th November 2004 15:04 UTC
I don't promise nothing nor good and stable one, but I'll work with the future plugin called xml.dll for NSIS.
My idea is only read the text between elements...
for example:
<element>nsis</element>
Should return nsis
what you thing?
Reading attributes can be pain in the touchi :D, but ideas can be helpfull...
sealite
16th November 2004 16:06 UTC
Cool but i'll give you one example. I want to modify the path of the templates in Openoffice.org. Here it's a part of the config file.
As you can see it's not very easy to define the structure where to find this.
<?xml version="1.0" encoding="UTF-8"?>
<oor:component-data xmlns:oor="http://openoffice.org/2001/registry" xmlns:xs="http://www.w3.org/2001/XMLSchema" oor:name="Common" oor:package="org.openoffice.Office">
<node oor:name="Path">
<node oor:name="Current">
<prop oor:name="OfficeInstall" oor:type="xs:string">
<value>C:\Program Files\OpenOffice.org1.1.3</value>
</prop>
<prop oor:name="Template" oor:type="oor:string-list">
<value>file:///P:/templates</value>
</prop>
</node>
</node>