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
> http://www.winamp
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Glenn Carr
> Sent: Thursday, May 30, 2002 5:21 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [DQSD-Users] [ dqsd-Feature Requests-562098 ] allow for
> optional extensions
>
>
&
Yeah, WinZip does too. It just doesn't allow you to get information from
the registry about the current install directory (AFAIK). I guess we could
have it prompt for the default install, and have the user enter the actual
install if it was different, but I'd prefer that it be automatic.
> so d
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 ad
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...
>
__
> 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...
Is it possible to grab the install directory from the registry, in case they
aren't using th
> 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
rom them.
>
> Thoughts?
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of John W.
> > Bairen, Jr.
> > Sent: Thursday, May 30, 2002 6:02 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: [DQSD-Users] [ dqs
> 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
:02 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [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
> -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 extensio
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.
_
rtin
> Sent: Wednesday, May 29, 2002 7:57 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [DQSD-Users] [ dqsd-Feature Requests-562098 ] allow for
> optional extensions
>
>
> As one of the people writing functionality you consider an extension - I
> still don't see how this is
As one of the people writing functionality you consider an extension - I
still don't see how this is possible. Most of the things I'm writing
require code insertion into the existing files. I can't imagine how you'll
tackle that issue.
For right now I'm left keeping my modifications to myself,
14 matches
Mail list logo
