O
omega
(e-mail address removed) (D F):
When install.vbs is run, it prompts up an interactive box, for user input
(in its case, for where to save the .txt clips). Then based on what is
entered, it modifies its .htm script.
:: htmStrF=Replace (htmStr,"archivePath =","archivePath = "&chr(34)&pathArchive&chr(34)&vbCrLf)
:: Set final=fso.CreateTextFile(Webfldr&"\ArchiveSelTxt.htm")
In the case of your script, there are more fields for interaction. One
for the text editor to be used, one for the path to save clips. Would this
be a way to go, if you wanted to add an install vbs for your script? For
that one group of folks who might prefer such a method, over editing the
script directly for their custom paths.
There is one more definable choice. User choice of the script's install
directory. In the case of IE Text Archiver, he forces it off to what is
defined as "Winfldr&"\web." Those who would choose an automated install of
your script, instead of manual, they would probably be satisfied just with
that regular default install location, I think. So maybe you could skip
offering up that choice during the routine.
Some of us much prefer to do the config ourselves. Yet I believe there are
also a lot of folks who could be more interested in an automated install
for this. So, I'm wondering what you think about writing another file for
that option. And based perhaps on how it's done install.vbs? That is, given
everything involved is workable for yours....the key difference being two
different fields to customize, not one, before the modified script.htm is
written to disk.
Btw, if you do look over install.vbs, and do anything based on it, I hope
that one thing you can change is the timeout (or however the cause) for the
user prompt staying on screen. It vanishes after four seconds, before one
has time to think, which makes the process very confusing.
When install.vbs is run, it prompts up an interactive box, for user input
(in its case, for where to save the .txt clips). Then based on what is
entered, it modifies its .htm script.
:: htmStrF=Replace (htmStr,"archivePath =","archivePath = "&chr(34)&pathArchive&chr(34)&vbCrLf)
:: Set final=fso.CreateTextFile(Webfldr&"\ArchiveSelTxt.htm")
In the case of your script, there are more fields for interaction. One
for the text editor to be used, one for the path to save clips. Would this
be a way to go, if you wanted to add an install vbs for your script? For
that one group of folks who might prefer such a method, over editing the
script directly for their custom paths.
There is one more definable choice. User choice of the script's install
directory. In the case of IE Text Archiver, he forces it off to what is
defined as "Winfldr&"\web." Those who would choose an automated install of
your script, instead of manual, they would probably be satisfied just with
that regular default install location, I think. So maybe you could skip
offering up that choice during the routine.
Some of us much prefer to do the config ourselves. Yet I believe there are
also a lot of folks who could be more interested in an automated install
for this. So, I'm wondering what you think about writing another file for
that option. And based perhaps on how it's done install.vbs? That is, given
everything involved is workable for yours....the key difference being two
different fields to customize, not one, before the modified script.htm is
written to disk.
Btw, if you do look over install.vbs, and do anything based on it, I hope
that one thing you can change is the timeout (or however the cause) for the
user prompt staying on screen. It vanishes after four seconds, before one
has time to think, which makes the process very confusing.