RE: [DQSD-Users] [ dqsd-Feature Requests-562098 ] allow for optional extensions

2002-05-31 Thread John W. Bairen, Jr.
another possibility is that dqsd could set an environmental variable at install (call it dqsddir). then you could unzip into %dqsddir%\extensions or something... no?? JB I guess NSIS can fetch the info in the registry. For instance, winamp's plug-ins (like AVS presets at

RE: [DQSD-Users] [ dqsd-Feature Requests-562098 ] allow for optional extensions

2002-05-30 Thread John W. Bairen, Jr.
FWIW, i think you are on to something Glenn. the question then becomes, how do other apps allow extensions/plug-ins? does anyone know how x-teq x-setup does it? (www.xteq.com) JB I'd sure like to hear others thoughts about this.

RE: [DQSD-Users] [ dqsd-Feature Requests-562098 ] allow for optional extensions

2002-05-30 Thread MLL
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John W. Bairen, Jr. Sent: Thursday, May 30, 2002 1:02 PM To: [EMAIL PROTECTED] Subject: RE: [DQSD-Users] [ dqsd-Feature Requests-562098 ] allow for optional extensions FWIW, i think you

RE: [DQSD-Users] [ dqsd-Feature Requests-562098 ] allow for optional extensions

2002-05-30 Thread Glenn Carr
: [DQSD-Users] [ dqsd-Feature Requests-562098 ] allow for optional extensions FWIW, i think you are on to something Glenn. the question then becomes, how do other apps allow extensions/plug-ins? does anyone know how x-teq x-setup does it? (www.xteq.com) JB I'd sure like to hear others

Re: [DQSD-Users] [ dqsd-Feature Requests-562098 ] allow for optional extensions

2002-05-30 Thread Glenn Carr
Sounds good to me.. The extensions could be bundled as self-extracting zip archives, making them easy to overlay into the DQSD tree. (provided the user can specify where this is, I dont have DQSD installed in C:\program files\..) I thought so too, but I'm not sure this is possible with

Re: [DQSD-Users] [ dqsd-Feature Requests-562098 ] allow for optional extensions

2002-05-30 Thread John W. Bairen, Jr.
-Users] [ dqsd-Feature Requests-562098 ] allow for optional extensions I didn't know anything about xteq... pretty interesting. Here's what I'm thinking right now... - have an extensions subdirectory - in the extensions subdir have a single .xml for each extension - any extraneous files needed

Re: [DQSD-Users] [ dqsd-Feature Requests-562098 ] allow for optional extensions

2002-05-30 Thread Glenn Carr
Sounds good. But can these XML files contain all the functionality needed (or links to the files that contain the functionality needed)? What I mean is this... can the XML files contain links to the other files (like .js files)? I think so. Currently our search XML files typically only

Re: [DQSD-Users] [ dqsd-Feature Requests-562098 ] allow for optional extensions

2002-05-30 Thread John W. Bairen, Jr.
so does ZipCentral (cool freeware zip util) http://zipcentral.iscool.net/ I can confirm that zipmagic allows the user to specify a target directory for the extraction, and the user is asked to confirm/override the default target directory when the archive is unpacked...

Re: [DQSD-Users] [ dqsd-Feature Requests-562098 ] allow for optional extensions

2002-05-30 Thread John W. Bairen, Jr.
FWIW, I actually like plug-in as that seems to be the more common term that I see anymore. JB A minor question... I keep waffling between 'extensions' and 'packages' because of my Unix and Emacs influence in my earlier days. Anyone prefer using 'packages' instead of 'extensions' (if we add