NewsArchive
01-02-2009, 01:47 AM
Hi Friedrich,
One of the things I would like to quickly include in my docuementation is a
list of all the files installed. An excellent place to get that file list
is from... SetupBuilder<g>
The current html format is fine for uploading to the web and displaying as a
resource there. But it falls short when you want to scrape the data out of
it and use it in something else. I _can_ get it into H&M with #MERGE but
the format is a bit wide for it to be useful. Unfortunately it doesn't seem
to work with anything except html and chm which is ok as I could handle
that.
So: How about optionally exporting 3 additional files:
[EXENAME -.ext]_Header.csv
[EXENAME -.ext]_Support.csv
[EXENAME -.ext]_FileList.csv
Header.csv:
A single record (+ header row) comma separated file with the the Summary
information.
Support.csv:
A multi-record (+ header row) comma separated file with the "Support files"
information.
FileList.csv:
A multi-record (+ header row) comma separated file with all the file
information. I.e.:
"ID","File","Source","Destination","Feature","Modified","Size","Version","CRC32","Options"
This way we could easily read this into a program and format this in any way
we wanted to and spit it out ready for use where we want it.
An option to expand variables when exporting would also be very useful when
using variables as part of the file or pathname.
An option to select fields for output would also be useful.
An option to use tab or semicolon separated format would also be useful.
What do you think?
Best regards,
--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com
Icetips product subscriptions at http://www.icetips.com/subscribe.php
One of the things I would like to quickly include in my docuementation is a
list of all the files installed. An excellent place to get that file list
is from... SetupBuilder<g>
The current html format is fine for uploading to the web and displaying as a
resource there. But it falls short when you want to scrape the data out of
it and use it in something else. I _can_ get it into H&M with #MERGE but
the format is a bit wide for it to be useful. Unfortunately it doesn't seem
to work with anything except html and chm which is ok as I could handle
that.
So: How about optionally exporting 3 additional files:
[EXENAME -.ext]_Header.csv
[EXENAME -.ext]_Support.csv
[EXENAME -.ext]_FileList.csv
Header.csv:
A single record (+ header row) comma separated file with the the Summary
information.
Support.csv:
A multi-record (+ header row) comma separated file with the "Support files"
information.
FileList.csv:
A multi-record (+ header row) comma separated file with all the file
information. I.e.:
"ID","File","Source","Destination","Feature","Modified","Size","Version","CRC32","Options"
This way we could easily read this into a program and format this in any way
we wanted to and spit it out ready for use where we want it.
An option to expand variables when exporting would also be very useful when
using variables as part of the file or pathname.
An option to select fields for output would also be useful.
An option to use tab or semicolon separated format would also be useful.
What do you think?
Best regards,
--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com
Icetips product subscriptions at http://www.icetips.com/subscribe.php