nsis-devel — NSIS developers lounge

Re: [NSIS-devel] Requirements for 3.0a0 release?

[Amir S. <ki...@gm...>]

We also need to update our tests to run the new stuff.
Mostly for the release we have `scons test`. It both runs our minor
collection of unit tests (`test-code`) and builds all .nsi files
(`test-scripts`).
We need to add more example files that use Unicode and possibly get
`test-scripts` to build in both ANSI and Unicode.
And any other new features, if any, could use an example being implemented.

Right now it seems `test-scripts` doesn't even work.

On Thu, Nov 8, 2012 at 1:01 PM, Oleksandr Gavenko <gav...@gm...> wrote:
> Amir Szekely point me to ask about requirements for 3.0a0 release.
>
> I just quote from private mail to me:
>
>> Before being able to release that, we need to become a bit more stabler.
>> Honestly, being an alpha, I'm more than OK with it not being perfect.
>> What we do need to figure out is what would be an acceptable minimum for
>> the release.
>
> Also Amir prepared wonderful page:
>
>   http://nsis.sourceforge.net/Release_Process
>
> According to it this step necessary (but not all!!):
>
>  * Update history.but file with changes (I can do initial job on this by
>    reviewing SVN changes in trunk since v246 tag)
>  * Update docs
>  * Build a dummy release (I have access only to WinXP and don't familiar with
>    testing steps of NSIS)
>  * Fix release.py for current API of Sourceforge (I can try this)
>
> Any ideas?
>
> --
> Best regards!
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
> _______________________________________________
> Nsis-devel mailing list
> Nsi...@li...
> https://lists.sourceforge.net/lists/listinfo/nsis-devel

Re: [NSIS-devel] Intro for myself (release manager).

[Wizou <sou...@wi...>]

Welcome Oleksandr :)

I've been a bit absent from this project for a while
but I hope your presence will give NSIS the opportunity to get back on 
tracks


Le 08/11/2012 21:36, Oleksandr Gavenko a écrit :
> Hi! I subscribed for SF blog and read article:
>
>    http://sourceforge.net/blog/developers-wanted-nullsoft-scriptable-install-system/
>
> and follow thread:
>
>    http://forums.winamp.com/showthread.php?s=91da2a036dd79f9e83979f04e4c6f915&t=348606
>
> After contacting with Amir Szekely and performing successful build of NSIS it
> seems acceptable to introduce myself to rest team.
>
> For quick intro about my devel skills refer to my resume:
>
>    http://gavenkoa.users.sourceforge.net/resume-en.html
>
> My face:
>
>    http://gavenkoa.users.sourceforge.net/photos.html
>
> My home page and blog:
>
>    http://gavenkoa.users.sourceforge.net/
>    http://brain-break.blogspot.com/
>
> Previously I use NSIS to package various drivers at job. Also two years ago I
> sent corrections for 2 languages: Russian and Ukrainian (I am native speaker).
>
> My interest on NSIS:
>
>   * kudos from working on well known open source project
>
> I can:
>
>   * Fix build issues.
>   * Update doc, CHANGES file etc.
>   * Check that bugs was go away.
>

Re: [NSIS-devel] Building NSIS. Suggestion for another one dll stab name.

[Amir S. <ki...@gm...>]

I created a new zlib package directly from 1.2.7 source using VC6.
So far it worked with everything we threw at it. Haven't tried cygwin
though, so let me know.

You can get it from:

http://nsis.sourceforge.net/Zlib

I also updated the documentation to point there.

The "Building NSIS from SVN" page does seem like it needs some updating.
INSTALL and "Building NSIS" in the docs are way more thorough. Maybe we
should just link there?


On Thu, Nov 8, 2012 at 2:28 PM, Anders <and...@us...>wrote:

> The building NSIS page links to
> http://prdownloads.sourceforge.net/libpng/zlib124-dll.zip but for some
> reason that file was deleted from SF at some point. The .lib in
> zlib125-dll.zip seems to crash when using Visual Studio! What I have
> been doing is to grab the .lib from zlib123-dll.zip and the .dll from
> zlib125-dll.zip ( http://sourceforge.net/projects/libpng/files/zlib/ )
> and that works both for MinGW and VC2003 IIRC.
>
>
>
> On Thu, Nov 8, 2012 at 9:50 PM, Oleksandr Gavenko <gav...@gm...>
> wrote:
> > I built NSIS trunk by:
> >
> >   set
> PATH=c:\opt\python27;c:\opt\python27\Scripts;c:\opt\MinGW\msys\1.0\bin;c:\opt\MinGW\bin;%PATH%
> >   set ZLIB_W32=c:\opt\zlib
> >
> >   scons SKIPUTILS="NSIS Menu"
> >   scons PREFIX="C:\opt\NSIS" install
> >
> >   $ cd c:\opt\nsis
> >   $ makensis.exe Examples\example1.nsi
> >   ...
> >   $ Examples\example1.exe
> >   ...
> >
> > But one step took a long time. That was zlib library. I got zlib from
> well
> > known Gnuwin32 project unpuck them and build failed at configuration
> step. As
> > I was new to SCons I spend a lot of time on finding a way to debug issue.
> >
> > My problem come from 2 thing:
> >
> >  * where do zlib live?
> >  * how to install zlib (file names, directory layout)?
> >
> > After all I found reference about zlib at:
> >
> >   http://nsis.sourceforge.net/Docs/AppendixG.html
> >
> > but these pages initially frustrate me:
> >
> >   http://nsis.sourceforge.net/Development_Files
> >   http://nsis.sourceforge.net/Building_NSIS_from_SVN
> >   http://nsis.sourceforge.net/Special_Builds
> >
> > In order to build I prepare fix:
> >
> > Index: SConstruct
> > ===================================================================
> > --- SConstruct  (revision 6273)
> > +++ SConstruct  (working copy)
> > @@ -461,7 +461,7 @@
> >         )
> >     ))
> >     # Search for import library of zlib for VisualC or mingw
> > -   for importlib in ['zdll.lib', 'libzdll.a']:
> > +   for importlib in ['zdll.lib', 'libzdll.a', 'libz.dll.a']:
> >         defenv['ZLIB_W32_LIB'] = os.path.dirname(str(
> >             defenv.FindFile(importlib,
> >                 [
> >
> > Note that "libz.dll.a" name also used in Cygwin...
> >
> > Also I have attempt to cross-compile NSIS in Debian and in Cygwin. But
> seems
> > Sconstruct must be fixed to do so.
> >
> > --
> > Best regards!
> >
> >
> ------------------------------------------------------------------------------
> > Everyone hates slow websites. So do we.
> > Make your web apps faster with AppDynamics
> > Download AppDynamics Lite for free today:
> > http://p.sf.net/sfu/appdyn_d2d_nov
> > _______________________________________________
> > Nsis-devel mailing list
> > Nsi...@li...
> > https://lists.sourceforge.net/lists/listinfo/nsis-devel
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
> _______________________________________________
> Nsis-devel mailing list
> Nsi...@li...
> https://lists.sourceforge.net/lists/listinfo/nsis-devel
>

Re: [NSIS-devel] Intro for myself (release manager).

[Amir S. <ki...@gm...>]

Welcome to the team Oleksandr!
I'm happy to have you join us, and hope we can work together to push NSIS
forward.


On Thu, Nov 8, 2012 at 12:36 PM, Oleksandr Gavenko <gav...@gm...>wrote:

> Hi! I subscribed for SF blog and read article:
>
>
> http://sourceforge.net/blog/developers-wanted-nullsoft-scriptable-install-system/
>
> and follow thread:
>
>
> http://forums.winamp.com/showthread.php?s=91da2a036dd79f9e83979f04e4c6f915&t=348606
>
> After contacting with Amir Szekely and performing successful build of NSIS
> it
> seems acceptable to introduce myself to rest team.
>
> For quick intro about my devel skills refer to my resume:
>
>   http://gavenkoa.users.sourceforge.net/resume-en.html
>
> My face:
>
>   http://gavenkoa.users.sourceforge.net/photos.html
>
> My home page and blog:
>
>   http://gavenkoa.users.sourceforge.net/
>   http://brain-break.blogspot.com/
>
> Previously I use NSIS to package various drivers at job. Also two years
> ago I
> sent corrections for 2 languages: Russian and Ukrainian (I am native
> speaker).
>
> My interest on NSIS:
>
>  * kudos from working on well known open source project
>
> I can:
>
>  * Fix build issues.
>  * Update doc, CHANGES file etc.
>  * Check that bugs was go away.
>
> --
> Best regards!
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
> _______________________________________________
> Nsis-devel mailing list
> Nsi...@li...
> https://lists.sourceforge.net/lists/listinfo/nsis-devel
>

Re: [NSIS-devel] Building NSIS. Suggestion for another one dll stab name.

[Anders <and...@us...>]

The building NSIS page links to
http://prdownloads.sourceforge.net/libpng/zlib124-dll.zip but for some
reason that file was deleted from SF at some point. The .lib in
zlib125-dll.zip seems to crash when using Visual Studio! What I have
been doing is to grab the .lib from zlib123-dll.zip and the .dll from
zlib125-dll.zip ( http://sourceforge.net/projects/libpng/files/zlib/ )
and that works both for MinGW and VC2003 IIRC.



On Thu, Nov 8, 2012 at 9:50 PM, Oleksandr Gavenko <gav...@gm...> wrote:
> I built NSIS trunk by:
>
>   set PATH=c:\opt\python27;c:\opt\python27\Scripts;c:\opt\MinGW\msys\1.0\bin;c:\opt\MinGW\bin;%PATH%
>   set ZLIB_W32=c:\opt\zlib
>
>   scons SKIPUTILS="NSIS Menu"
>   scons PREFIX="C:\opt\NSIS" install
>
>   $ cd c:\opt\nsis
>   $ makensis.exe Examples\example1.nsi
>   ...
>   $ Examples\example1.exe
>   ...
>
> But one step took a long time. That was zlib library. I got zlib from well
> known Gnuwin32 project unpuck them and build failed at configuration step. As
> I was new to SCons I spend a lot of time on finding a way to debug issue.
>
> My problem come from 2 thing:
>
>  * where do zlib live?
>  * how to install zlib (file names, directory layout)?
>
> After all I found reference about zlib at:
>
>   http://nsis.sourceforge.net/Docs/AppendixG.html
>
> but these pages initially frustrate me:
>
>   http://nsis.sourceforge.net/Development_Files
>   http://nsis.sourceforge.net/Building_NSIS_from_SVN
>   http://nsis.sourceforge.net/Special_Builds
>
> In order to build I prepare fix:
>
> Index: SConstruct
> ===================================================================
> --- SConstruct  (revision 6273)
> +++ SConstruct  (working copy)
> @@ -461,7 +461,7 @@
>         )
>     ))
>     # Search for import library of zlib for VisualC or mingw
> -   for importlib in ['zdll.lib', 'libzdll.a']:
> +   for importlib in ['zdll.lib', 'libzdll.a', 'libz.dll.a']:
>         defenv['ZLIB_W32_LIB'] = os.path.dirname(str(
>             defenv.FindFile(importlib,
>                 [
>
> Note that "libz.dll.a" name also used in Cygwin...
>
> Also I have attempt to cross-compile NSIS in Debian and in Cygwin. But seems
> Sconstruct must be fixed to do so.
>
> --
> Best regards!
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
> _______________________________________________
> Nsis-devel mailing list
> Nsi...@li...
> https://lists.sourceforge.net/lists/listinfo/nsis-devel

[NSIS-devel] Requirements for 3.0a0 release?

[Oleksandr G. <gav...@gm...>]

Amir Szekely point me to ask about requirements for 3.0a0 release.

I just quote from private mail to me:

> Before being able to release that, we need to become a bit more stabler.
> Honestly, being an alpha, I'm more than OK with it not being perfect.
> What we do need to figure out is what would be an acceptable minimum for
> the release.

Also Amir prepared wonderful page:

  http://nsis.sourceforge.net/Release_Process

According to it this step necessary (but not all!!):

 * Update history.but file with changes (I can do initial job on this by
   reviewing SVN changes in trunk since v246 tag)
 * Update docs
 * Build a dummy release (I have access only to WinXP and don't familiar with
   testing steps of NSIS)
 * Fix release.py for current API of Sourceforge (I can try this)

Any ideas?

-- 
Best regards!

[NSIS-devel] Building NSIS. Suggestion for another one dll stab name.

[Oleksandr G. <gav...@gm...>]

I built NSIS trunk by:

  set PATH=c:\opt\python27;c:\opt\python27\Scripts;c:\opt\MinGW\msys\1.0\bin;c:\opt\MinGW\bin;%PATH%
  set ZLIB_W32=c:\opt\zlib

  scons SKIPUTILS="NSIS Menu"
  scons PREFIX="C:\opt\NSIS" install

  $ cd c:\opt\nsis
  $ makensis.exe Examples\example1.nsi
  ...
  $ Examples\example1.exe
  ...

But one step took a long time. That was zlib library. I got zlib from well
known Gnuwin32 project unpuck them and build failed at configuration step. As
I was new to SCons I spend a lot of time on finding a way to debug issue.

My problem come from 2 thing:

 * where do zlib live?
 * how to install zlib (file names, directory layout)?

After all I found reference about zlib at:

  http://nsis.sourceforge.net/Docs/AppendixG.html

but these pages initially frustrate me:

  http://nsis.sourceforge.net/Development_Files
  http://nsis.sourceforge.net/Building_NSIS_from_SVN
  http://nsis.sourceforge.net/Special_Builds

In order to build I prepare fix:

Index: SConstruct
===================================================================
--- SConstruct  (revision 6273)
+++ SConstruct  (working copy)
@@ -461,7 +461,7 @@
        )
    ))
    # Search for import library of zlib for VisualC or mingw
-   for importlib in ['zdll.lib', 'libzdll.a']:
+   for importlib in ['zdll.lib', 'libzdll.a', 'libz.dll.a']:
        defenv['ZLIB_W32_LIB'] = os.path.dirname(str(
            defenv.FindFile(importlib, 
                [

Note that "libz.dll.a" name also used in Cygwin...

Also I have attempt to cross-compile NSIS in Debian and in Cygwin. But seems
Sconstruct must be fixed to do so.

-- 
Best regards!

[NSIS-devel] Intro for myself (release manager).

[Oleksandr G. <gav...@gm...>]

Hi! I subscribed for SF blog and read article:

  http://sourceforge.net/blog/developers-wanted-nullsoft-scriptable-install-system/

and follow thread:

  http://forums.winamp.com/showthread.php?s=91da2a036dd79f9e83979f04e4c6f915&t=348606

After contacting with Amir Szekely and performing successful build of NSIS it
seems acceptable to introduce myself to rest team.

For quick intro about my devel skills refer to my resume:

  http://gavenkoa.users.sourceforge.net/resume-en.html

My face:

  http://gavenkoa.users.sourceforge.net/photos.html

My home page and blog:

  http://gavenkoa.users.sourceforge.net/
  http://brain-break.blogspot.com/

Previously I use NSIS to package various drivers at job. Also two years ago I
sent corrections for 2 languages: Russian and Ukrainian (I am native speaker).

My interest on NSIS:

 * kudos from working on well known open source project

I can:

 * Fix build issues.
 * Update doc, CHANGES file etc.
 * Check that bugs was go away.

-- 
Best regards!

Re: [NSIS-devel] VIFileVersion version attribute

[Wizou <sou...@wi...>]

Hi

I would use my PETool.exe (available at http://wizou.fr) to tweak the 
FileVersion
after NSIS generation. Seems much easier than the big script on 
stackoverflow.com

but VIFileVersion seems a good idea and your doc (and fallback) is fine.

I have no opinion on the question of input validation.

Wizou


Le 28/07/2011 23:57, Anders a écrit :
> I'm adding a VIFileVersion command because of
> http://stackoverflow.com/questions/6859153/why-does-viproductversion-argument-override-value-of-productversion-key
>
> Having ProductVersion != FileVersion in VS_FIXEDFILEINFO is probably
> pretty rare but the workaround you need to use without it is horrible.
>
> My initial rewrite of the docs looks like
> http://jsbin.com/icewuh/2/edit#preview The reference to
> VS_FIXEDFILEINFO might be a bit obscure but it does reflect what the
> attribute actually does (The FileVersion string does not have to match
> the FileVersion in VS_FIXEDFILEINFO and the WinXP version properties
> tab will display both (VS_FIXEDFILEINFO at the top and the string in
> the list of strings)). The old docs had a major docbug since it is the
> file version and not the product version that is displayed at the top
> of the version tab dialog!
>
> Another quirk is that makensis does not seem to echo any information
> when the VIProductVersion command is used and it does not validate the
> input in script.cpp like most commands, it does it during
> CEXEBuild::write_output. Why? I don't know but I did not want to
> change it since it could possibly affect scripts that use !delfile to
> do cleanup etc since the invalid input error is delayed. VIFileVersion
> does not echo any information either but it does validate the input
> right away but that is ok since the command is new. Should I keep the
> old delayed VIProductVersion input validation for compatibility or
> just fail in script.cpp when the command is executed with a bad param?
>
> Also, if the script does not contain a VIFileVersion command it falls
> back to the old behavior with FileVersion == ProductVersion.
>
> What do you guys think?
>
> ------------------------------------------------------------------------------
> Got Input?   Slashdot Needs You.
> Take our quick survey online.  Come on, we don't ask for help often.
> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
> http://p.sf.net/sfu/slashdot-survey
> _______________________________________________
> Nsis-devel mailing list
> Nsi...@li...
> https://lists.sourceforge.net/lists/listinfo/nsis-devel
>

[NSIS-devel] VIFileVersion version attribute

[Anders <and...@us...>]

I'm adding a VIFileVersion command because of
http://stackoverflow.com/questions/6859153/why-does-viproductversion-argument-override-value-of-productversion-key

Having ProductVersion != FileVersion in VS_FIXEDFILEINFO is probably
pretty rare but the workaround you need to use without it is horrible.

My initial rewrite of the docs looks like
http://jsbin.com/icewuh/2/edit#preview The reference to
VS_FIXEDFILEINFO might be a bit obscure but it does reflect what the
attribute actually does (The FileVersion string does not have to match
the FileVersion in VS_FIXEDFILEINFO and the WinXP version properties
tab will display both (VS_FIXEDFILEINFO at the top and the string in
the list of strings)). The old docs had a major docbug since it is the
file version and not the product version that is displayed at the top
of the version tab dialog!

Another quirk is that makensis does not seem to echo any information
when the VIProductVersion command is used and it does not validate the
input in script.cpp like most commands, it does it during
CEXEBuild::write_output. Why? I don't know but I did not want to
change it since it could possibly affect scripts that use !delfile to
do cleanup etc since the invalid input error is delayed. VIFileVersion
does not echo any information either but it does validate the input
right away but that is ok since the command is new. Should I keep the
old delayed VIProductVersion input validation for compatibility or
just fail in script.cpp when the command is executed with a bad param?

Also, if the script does not contain a VIFileVersion command it falls
back to the old behavior with FileVersion == ProductVersion.

What do you guys think?

Re: [NSIS-devel] makensis.nsi in a post UAC world

[Anders <and...@us...>]

Yes, I was talking about a new stub exe. Currently we just set
notepad.exe under the open verb in the registry but that means we
can't use the default programs control panel in vista, so to work
around that we could have a little stub that first tries ShellExecute
using the edit verb, if that fails, just run notepad...

Re: [NSIS-devel] makensis.nsi in a post UAC world

[Wizou <sou...@wi...>]

1) I was simply talking about changing the behaviour of the "Edit 
script" menu from MakeNSISw, so it can't loop, even if MakeNSISw is 
somehow registered as edit verb, the user would still have to choose the 
menu item
2) i'm not sure what you're referring to with "nsisstub.exe", is it a 
stub that would launch an editor ?


Le 28/03/2011 02:54, Anders a écrit :
> The edit verb approach might have some issues:
>
> 1) If we are somehow registered as the edit verb, we will loop forever!
>
> 2) I'm not sure if the Win7 recent files jump list is going to be
> happy with nsisstub.exe>>>  notepad.exe but who knows, maybe it will
> work correctly.
>
>
> I created a little proof of concept app that shows what we should be
> aiming for (IMHO): http://i.imgur.com/yUDSy.png
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> Nsis-devel mailing list
> Nsi...@li...
> https://lists.sourceforge.net/lists/listinfo/nsis-devel
>

Re: [NSIS-devel] makensis.nsi in a post UAC world

[Anders <and...@us...>]

The edit verb approach might have some issues:

1) If we are somehow registered as the edit verb, we will loop forever!

2) I'm not sure if the Win7 recent files jump list is going to be
happy with nsisstub.exe >>> notepad.exe but who knows, maybe it will
work correctly.


I created a little proof of concept app that shows what we should be
aiming for (IMHO): http://i.imgur.com/yUDSy.png

Re: [NSIS-devel] makensis.nsi in a post UAC world

[Wizou <sou...@wi...>]

I agree.

I was thinking we could try launching the NSI/NSH file with the "edit" verb
and only if that doesn't work, run Notepad
So that the installed adequate editor is run first, which makes a better 
integration.

Le 25/03/2011 18:31, Amir Szekely a écrit :
> I don't know if we want to create unnecessary competition for 
> currently available IDEs.
> People will start asking for features and eventually we'll cave to 
> some of them, spending time on features already available in other 
> editors and that could be used for features of NSIS itself.
> I'm not sure that we want, with our limited development time, to focus 
> on that.
>
> On Fri, Mar 25, 2011 at 12:20 AM, Anders 
> <and...@us... 
> <mailto:and...@us...>> wrote:
>
>     I was thinking about adding support for the default programs feature
>     added to Vista (
>     http://msdn.microsoft.com/en-us/library/cc144154%28v=vs.85%29.aspx#SetYourDefaultPrograms
>     ) but there is a problem; there is no way to specify a icon, the UI
>     uses the icon from the first verb and in our case that is notepad.exe!
>     I'll put this feature on the back burner for now...
>
>     ...maybe we should add basic file editing to makensisw so we could
>     open files there and not in notepad?
>
>     ------------------------------------------------------------------------------
>     Enable your software for Intel(R) Active Management Technology to
>     meet the
>     growing manageability and security demands of your customers.
>     Businesses
>     are taking advantage of Intel(R) vPro (TM) technology - will your
>     software
>     be a part of the solution? Download the Intel(R) Manageability Checker
>     today! http://p.sf.net/sfu/intel-dev2devmar
>     _______________________________________________
>     Nsis-devel mailing list
>     Nsi...@li...
>     <mailto:Nsi...@li...>
>     https://lists.sourceforge.net/lists/listinfo/nsis-devel
>
>
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
>
>
> _______________________________________________
> Nsis-devel mailing list
> Nsi...@li...
> https://lists.sourceforge.net/lists/listinfo/nsis-devel

Re: [NSIS-devel] makensis.nsi in a post UAC world

[Amir S. <ki...@gm...>]

I don't know if we want to create unnecessary competition for currently
available IDEs.
People will start asking for features and eventually we'll cave to some of
them, spending time on features already available in other editors and that
could be used for features of NSIS itself.
I'm not sure that we want, with our limited development time, to focus on
that.

On Fri, Mar 25, 2011 at 12:20 AM, Anders <and...@us...>wrote:

> I was thinking about adding support for the default programs feature
> added to Vista (
>
> http://msdn.microsoft.com/en-us/library/cc144154%28v=vs.85%29.aspx#SetYourDefaultPrograms
> ) but there is a problem; there is no way to specify a icon, the UI
> uses the icon from the first verb and in our case that is notepad.exe!
> I'll put this feature on the back burner for now...
>
> ...maybe we should add basic file editing to makensisw so we could
> open files there and not in notepad?
>
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> Nsis-devel mailing list
> Nsi...@li...
> https://lists.sourceforge.net/lists/listinfo/nsis-devel
>

Re: [NSIS-devel] makensis.nsi in a post UAC world

[Anders <and...@us...>]

I was thinking about adding support for the default programs feature
added to Vista (
http://msdn.microsoft.com/en-us/library/cc144154%28v=vs.85%29.aspx#SetYourDefaultPrograms
) but there is a problem; there is no way to specify a icon, the UI
uses the icon from the first verb and in our case that is notepad.exe!
I'll put this feature on the back burner for now...

...maybe we should add basic file editing to makensisw so we could
open files there and not in notepad?

Re: [NSIS-devel] makensis.nsi in a post UAC world

[Wizou <sou...@wi...>]

Maybe other program/plugin/editors working with NSIS are using 
HK*\Software\NSIS
Make sure you don't break compatibility

Le 22/03/2011 09:31, Anders a écrit :
> ...and just to clarify question B; I know makensisw.exe uses
> HKCU\Software\NSIS but the current installer only writes to
> HKLM\Software\NSIS and I was only talking about the entries written by
> the installer (Path and version)
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> Nsis-devel mailing list
> Nsi...@li...
> https://lists.sourceforge.net/lists/listinfo/nsis-devel
>

Re: [NSIS-devel] makensis.nsi in a post UAC world

[Anders <and...@us...>]

...and just to clarify question B; I know makensisw.exe uses
HKCU\Software\NSIS but the current installer only writes to
HKLM\Software\NSIS and I was only talking about the entries written by
the installer (Path and version)

Re: [NSIS-devel] makensis.nsi in a post UAC world

[Anders <and...@us...>]

A couple of small changes and bugfixes:

+Make sure NT4 user is admin in .onInit
*Does not force default verb to be "open" (open is default if not set)
*Using </CurrentUser|/AllUsers> /D=c:\foo forces the /D path to be the
default for that install mode (In GUI mode)
*Minor optimizations

http://pastebin.com/nVjZG5KM

It is now very strict about not allowing Win9x and NT4 single user
installs. While a up to date system with IE4+shell update might have
$localappdata, the HKCU to HKCR mapping and uninstall entry will not
work (And who uses those systems on a shared machine to develop these
days anyways?)


Now for a couple of questions:

A) Why are we using WriteRegExpandStr to write the UninstallString and
InstallLocation uninstall entries? You can't use %appdata% etc in the
directory page and I could not get /D= to accept it either so is there
any scenario where $InstDir contains a path that needs to be expanded?

B) Do we need HK*\Software\NSIS\ ? We might as well just store the
version along with the uninstall data. Even if we stop writing it for
fresh installs we would have to keep updating it if it already exists
I'm guessing, but are these entries actually used by anyone other than
the installer itself?

Re: [NSIS-devel] makensis.nsi in a post UAC world

[Amir S. <ki...@gm...>]

Haven't had a chance to look at the code, but I totally vote yes on all of
them.
Gotta make sure it'll be easy for other to use those in the future too.

On Mon, Mar 21, 2011 at 2:57 PM, Anders <and...@us...>wrote:

> Our current installer should be put out of its misery IMHO, we are a
> installer project after all so our installer should not suck!
>
> I took the currect nsi from SVN and modified it a bit:
>
> +Single User & All Users install types (UAC prompts are not cool)
> +Safer filetype uninstall logic (Only remove the stuff we installed,
> leave 3rd party changes alone)
> +Filetypes:PerceivedType for XP+ (Automatic support for all my text
> editors in the context menu, WIN!)
> *Separated Startmenu and Desktop shortcuts into sections (I'm actually
> still using the older nsis\nsis+examples folder+readme's shortcuts on
> my system, but I guess they were removed for a reason?)
> *Desktop shortcut is unselected by default (Desktop shortcuts suck ass
> (Hello Adobe Reader!), bundling that with the startmenu shortcut
> section is nuts)
>
> http://pastebin.com/YQia1FeL
>
> It probably needs more testing, what do you guys think?
>
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> Nsis-devel mailing list
> Nsi...@li...
> https://lists.sourceforge.net/lists/listinfo/nsis-devel
>

[NSIS-devel] makensis.nsi in a post UAC world

[Anders <and...@us...>]

Our current installer should be put out of its misery IMHO, we are a
installer project after all so our installer should not suck!

I took the currect nsi from SVN and modified it a bit:

+Single User & All Users install types (UAC prompts are not cool)
+Safer filetype uninstall logic (Only remove the stuff we installed,
leave 3rd party changes alone)
+Filetypes:PerceivedType for XP+ (Automatic support for all my text
editors in the context menu, WIN!)
*Separated Startmenu and Desktop shortcuts into sections (I'm actually
still using the older nsis\nsis+examples folder+readme's shortcuts on
my system, but I guess they were removed for a reason?)
*Desktop shortcut is unselected by default (Desktop shortcuts suck ass
(Hello Adobe Reader!), bundling that with the startmenu shortcut
section is nuts)

http://pastebin.com/YQia1FeL

It probably needs more testing, what do you guys think?

Re: [NSIS-devel] TargetMinimalOS

[Anders <and...@us...>]

Sorry about not saying anything before, I just saw it in the commit logs and
thought I'd chime in (I have not been able to setup a rss feed for the
mailing list so I will probably miss out or be late to the party)

Re: [NSIS-devel] TargetMinimalOS

[Wizou <sou...@wi...>]

Couldn't you give your objections before I changed UnicodeInstaller into 
TargetMinimalOS ?
I exposed you my intentions on June 9th

For static stubs, it could be interesting to have static stubs that can 
do some more intelligent things if the script author accepts it will run 
only on some versions of Windows

NT4 & 9x have indeed version 4.0, I don't know where I read 4.1
It's not a matter of "which is better", it's just a matter of 
determining which APIs will be available for the static stub associated 
with the version given to TargetMinimalOS.

I have considered the minimal target version for Unicode is 2000 because 
NT4 Unicode support is far from being correct and complete. (for 
example, it uses UCS2 unicode instead of UTF-16).
But if you have a NT4 system at hand, you can test if the Unicode stub 
works on it.




Anders a écrit :
> Why does TargetMinimalOS exist at all?
>
> First off, for the foreseeable future, we are stuck with static stubs, 
> so 5.0 is the same thing as 6.0 etc
>
> Also, the proposed version numbers do not really make sense. 4.1=9x? 
> Why? Both NT4 and Win9x are v4 and existed side by side, it's hard to 
> say which is "better" (NT has a better kernel, Win98+ has better shell 
> & comctrl support out of the box)
>
> So IMHO we should just have a UnicodeTarget property.
>
> And while we are on the subject, what is the minimal target version 
> for the unicode build, NT4 or 2000?
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> ------------------------------------------------------------------------
>
> _______________________________________________
> Nsis-devel mailing list
> Nsi...@li...
> https://lists.sourceforge.net/lists/listinfo/nsis-devel
>   

[NSIS-devel] TargetMinimalOS

[Anders <and...@us...>]

Why does TargetMinimalOS exist at all?

First off, for the foreseeable future, we are stuck with static stubs, so
5.0 is the same thing as 6.0 etc

Also, the proposed version numbers do not really make sense. 4.1=9x? Why?
Both NT4 and Win9x are v4 and existed side by side, it's hard to say which
is "better" (NT has a better kernel, Win98+ has better shell & comctrl
support out of the box)

So IMHO we should just have a UnicodeTarget property.

And while we are on the subject, what is the minimal target version for the
unicode build, NT4 or 2000?

Re: [NSIS-devel] Updated documentation

[Wizou <sou...@wi...>]

in fact I didn't have Html Help Compiler
but I just realized I don't need it, halibut generates HTML files

Seems everything is fine in my documentation changes.
Don't hesitate to suggest another way of presenting the Unicode support.

Also, I wrote Unicode support starts with v2.50, so that we can either 
release more ANSI versions, or just choose to jump directly to v2.50 as 
a mark of "major release".



Amir Szekely a écrit :
> Halibut is automatically built with the build system to compile the 
> documentation.
>
> On Fri, Jul 9, 2010 at 6:13 PM, Wizou <sou...@wi... 
> <mailto:sou...@wi...>> wrote:
>
>     I updated NSIS documentation for Unicode support.
>     However I don't have Halibut installed here so I hope I didn't mess up
>     and the result is correct.
>
>
>     ------------------------------------------------------------------------------
>     This SF.net email is sponsored by Sprint
>     What will you do first with EVO, the first 4G phone?
>     Visit sprint.com/first <http://sprint.com/first> --
>     http://p.sf.net/sfu/sprint-com-first
>     _______________________________________________
>     Nsis-devel mailing list
>     Nsi...@li...
>     <mailto:Nsi...@li...>
>     https://lists.sourceforge.net/lists/listinfo/nsis-devel
>
>