PDA

View Full Version : SB7 - write XML files



NewsArchive
09-29-2009, 02:03 AM
Hi Friedrich,

Our company decided that we're not writing to the registry anymore and use
XML files instead (stored in Programmdata\Company\Product). Is it planned to
support this in SB? I attached a sample xml file the way we use

Thank you!

Regards,
Hanspeter Stutz
Global System AG

NewsArchive
09-29-2009, 02:04 AM
Hi Hanspeter,

> Our company decided that we're not writing to the registry anymore and use
> XML files instead (stored in Programmdata\Company\Product). Is it planned
> to support this in SB? I attached a sample xml file the way we use

Only very, very few SetupBuilder users asked for native XML support from
within the installer. Adding new functionality is a priority-driven
processes and so a XML feature has low priority at the moment. Of course,
if there is enough interest, this will change.

But the ability to call your own DLLs from the installer lets you support
XML. You can develop your own XML support (e.g. with the excellent iQ-XML,
written in Clarion by Robert Paresi)

http://www.paresi.net/clarion/

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder is Windows installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

NewsArchive
09-29-2009, 02:05 AM
> But the ability to call your own DLLs from the installer lets you support
> XML. You can develop your own XML support (e.g. with the excellent iQ-XML,
> written in Clarion by Robert Paresi)
>
> http://www.paresi.net/clarion/

Actually unless he is using iqXML in his app, xFiles by CapeSoft would be a
better choice as it would not require the distribution of the extra DLL
that is required for iqXML.

But an even better solution (based on his example) would be if he created a
external XML file "skeleton" that just had tokens inserted where the data
needs to be.


Then he could put the file where it needs to go with the installer, load it
into SetupBuilder and then just replace the tokens with the data from the
installer.

This is how we create the .addin ( XML ) files for the C7 installers of our
products and it works like a charm.

Since it is a known XML structure there is no need to actually have an XML
tool for the task.

It is just a simple search/replace in a text file and SetupBuilder can do
that easily!

:-)

Charles


--
-------------------------------------------------------------------------------------------------------
Charles Edmonds
www.clarionproseries.com - "Get ProPath, make your Clarion programs ready
for Windows 7 and Vista!"
www.ezchangelog.com - "Free ChangeLog software to manage your projects!"
www.setupcast.com - "A revolutionary new publishing system for software
developers - enhanced for SetupBuilder users!"
www.pagesnip.com - "Print and Save the Web, just the way you want it!"
www.clarionproseries.com - "Serious tools for Clarion Developers"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms!"
www.lansrad.com - "Intelligent Solutions for Universal Problems"
www.fotokiss.com - "World's Best Auction Photo Editor"
-------------------------------------------------------------------------------------------------------

NewsArchive
09-29-2009, 02:06 AM
Hi Charles,

good suggestion. So you say the installer installs the XML and also is able
to parse and write this during the installation?

Thanks,
Hanspeter

NewsArchive
09-29-2009, 02:07 AM
> good suggestion. So you say the installer installs the XML and also is able
> to parse and write this during the installation?

Yes - no problem at all.

Attached is a zip file that has the ProPath version of the SetupBuilder
Include script that we use for our C7 installs.

It also includes the .addin file for C7.

Note that the addin file is just a generic file we use. It is simply
renamed ProPath.addin.

The installer places this into the correct folder for C7 accessories.

Then at the end of the installation script all we do is insert the
SetupBuilder include file into the main script.

In the top of the include file are some static variables particular to the
product, but there are also some references like %CLA_ADDINS% that are
simply variables set based on the main install script (and user selections
at runtime of course).

All the script does is count how many lines are in the file that it loads,
then it loops and processes each line looking to see if there are tokens to
be replaced with values.

Easy as pie<g>

With that simple (and quite fast) methodology, you should be able to do
what you want to do without the need of an XML library at all.

Does that help?

Charles




--
-------------------------------------------------------------------------------------------------------
Charles Edmonds
www.clarionproseries.com - "Get ProPath, make your Clarion programs ready
for Windows 7 and Vista!"
www.ezchangelog.com - "Free ChangeLog software to manage your projects!"
www.setupcast.com - "A revolutionary new publishing system for software
developers - enhanced for SetupBuilder users!"
www.pagesnip.com - "Print and Save the Web, just the way you want it!"
www.clarionproseries.com - "Serious tools for Clarion Developers"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms!"
www.lansrad.com - "Intelligent Solutions for Universal Problems"
www.fotokiss.com - "World's Best Auction Photo Editor"
-------------------------------------------------------------------------------------------------------

NewsArchive
09-29-2009, 02:08 AM
Hi Charles,

Wow cool, very appreciated!!!

Regards,
Hanspeter

NewsArchive
09-29-2009, 02:09 AM
>
> Easy as pie<g>
>

VERY COOL! :-)

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder is Windows installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

NewsArchive
09-29-2009, 02:09 AM
Excellent, Charles!

Jane

NewsArchive
09-29-2009, 02:10 AM
bitchen

Jeff Slarve

NewsArchive
09-29-2009, 02:10 AM
Hi Friedrich,

> Only very, very few SetupBuilder users asked for native XML support from
> within the installer. Adding new functionality is a priority-driven
> processes and so a XML feature has low priority at the moment. Of course,
> if there is enough interest, this will change.
I understand and agree
>
> But the ability to call your own DLLs from the installer lets you support
> XML. You can develop your own XML support (e.g. with the excellent
> iQ-XML,
> written in Clarion by Robert Paresi)
this is what I'm planning to do

Thanks,
Hanspeter