EclipseNSIS

thanks

EclipseNSIS 0.9.5 and EclipseNSIS InstallOptions Editor 0.9.4 released

EclipseNSIS 0.9.5 and EclipseNSIS InstallOptions Editor 0.9.5 are both available for download now.
See the EclipseNSIS home page for details.

Changes:

EclipseNSIS

• Upgraded to Eclipse 3.2 - no longer compatible with Eclipse 3.1.
• Added Export as HTML command.
• Var elements now shown in Outline view.
• Added NSIS Command Wizard for adding NSIS commands to script.
• Added drag & drop support to NSIS Script Wizard and EclipseNSIS Editor.
• Added support for REG_BIN and REG_EXPAND_SZ in NSIS Script Wizard.
• Added support for Library installs in NSIS Script Wizard.
• NSIS Script Wizard can now save output to filesystem in addition to the workspace.
• Added registry key and registry value browsers to NSIS Script Wizard.
• Added command to insert registry value into NSIS script.
• Added filtering to outline view.
• Added startup plugin to check file associations.
• Bug Fixes
  o 1416349
  o 1443239
  o 1464413
  o 1466390
  o 1474161
  o 1521533
  o 1556289
  o 1587717
  o 1591254
  o 1649681
• Feature Requests:
  o 1441231
  o 1452422
  o 1587982
• Other minor bug fixes.

EclipseNSIS InstallOptions Editor

• Upgraded to Eclipse 3.2 - no longer compatible with Eclipse 3.1.
• Added Export as HTML command.
• Added new control editing commands in source editor.
• Control type can now be changed in the design editor.
• Added support for automatic Team checkout in design editor.
• Fixed handling of escaped characters in INI file.
• Added Quickfix support in Source editor.
• Other minor bug fixes.

Notes:
Java 6 is now officially supported. Windows Vista is nominally supported, but I have not tested it on this platform, since I do not have it installed. Support for Windows 98 & ME is deprecated in this version and will be removed in the next version because of stability issues.

As always, I am looking for any and all bugs you may find. These may be entered in the EclipseNSIS project SourceForge Bug tracker. Feature requests may also be entered.

cool!

did you add support for the new commands that come with nsis 2.24? (FOCUS flag for InstallOptions, new predefines etc...)

Since NSIS 2.24 is not yet released, I haven't added support for it. Once it is released, I may release an update for it.

Awesome! Is it possible to tune-up bitmap controls a bit? For example shift bitmap icon a bit to the left/right to unhidden digits showing size when dragging borders. Maybe even display actual bitmap (specified in text label) instead of an icon? But the first thing I would ask is to enable these bitmaps in preview - perhaps it just the matter of copying them along with preview script in temp directory.

Is it possible to tune-up bitmap controls a bit? For example shift bitmap icon a bit to the left/right to unhidden digits showing size when dragging borders.

I don't quite understand what you mean by this.

Maybe even display actual bitmap (specified in text label) instead of an icon? But the first thing I would ask is to enable these bitmaps in preview - perhaps it just the matter of copying them along with preview script in temp directory.

Displaying the actual bitmap is not really feasible.
You see, the TEXT property of the bitmap refers to the location of the bitmap on the target system- so if you are setting its value to a local file name on your system, you are making a mistake. There is no way to know what bitmap is going to be there at the named location on the target system, so showing the "actual" bitmap is not possible.
However, I will implement some sort of visual cue of the size and location of the bitmap/icon controls in the preview.

Originally posted by iceman_k
I don't quite understand what you mean by this.

I mean that while you drag the border of bitmap control there is an icon inside which does not allow you to see the size of the box clearly.

Displaying the actual bitmap is not really feasible.
You see, the TEXT property of the bitmap refers to the location of the bitmap on the target system- so if you are setting its value to a local file name on your system, you are making a mistake. There is no way to know what bitmap is going to be there at the named location on the target system, so showing the "actual" bitmap is not possible.
However, I will implement some sort of visual cue of the size and location of the bitmap/icon controls in the preview.

Aha.. Is it possible then in EclipseNSIS to parse installoptions .ini and detect the errors like this one - when user specified bitmaps in installoptions, but forgot to include them into .nsi file to extract to $PLUGINSDIR ?

The logic seems to be pretty simple for previewer - the only problem is to remind user to extract the bitmaps to $PLUGINSDIR as needed.

However, how can EclipseNSIS know which .nsi file the .ini file will be used with? The same .ini file can be used with potentially unlimited number of .nsi files.
Also, it is possible that the image file for the bitmap is not part of the installer, e.g., it is already present on the target system or it will be downloaded from some web site, etc. So, it is unlikely that what you are asking will ever happen. However, since (I assume) the developer is actually testing the installer before releasing it, (s)he will see that the bitmap file is missing and correct the problem accordingly.

Indeed, EclipseNSIS can't figure out what .nsi is used to display given .ini, but it could parse .nsi files, detect all included .ini and then walk through bitmaps and throw a warning (suppressable) if the file referenced in bitmap is not included in .nsi or extracted to plugins dir. Is that possible?

Just for testing design I wish I knew Java to make a patch to cover my basic scenario when .bmp files referenced from .ini are included in preview .nsi file to be unpacked in $PLUGINSDIR later and displayed during preview. How can I iterate over the list of bitmaps in .ini and run a filter just before preview .ini will be processed?

Originally posted by ********
Indeed, EclipseNSIS can't figure out what .nsi is used to display given .ini, but it could parse .nsi files, detect all included .ini and then walk through bitmaps and throw a warning (suppressable) if the file referenced in bitmap is not included in .nsi or extracted to plugins dir. Is that possible?

You still don't get what I mean.
The TEXT property of the bitmap field in the ini file refers to the RUNTIME location of the bitmap file. Even if the ini file is parsed, EclipseNSIS is not going to know how the bitmap file is going to get to that runtime location.
A typical usage scenario for InstallOptions is as follows:

File /oname=$PLUGINSDIR\setup.ini setup.ini

File /oname=$PLUGINSDIR\setup.bmp c:\My Local Directory\MyCoolBitmap.bmp

WriteIniStr $PLUGINSDIR\setup.ini "Field 5" Text "$PLUGINSDIR\setup.bmp"

installoptions::show $PLUGINSDIR\setup.ini

Parsing the ini file to look at the bitmap is not going to serve any purpose.

EclipseNSIS InstallOptionsEx Editor?

What do you think about an EclipseNSIS InstallOptionsEx Editor?
Is would be very useful for me.

InstallOptionEx unofficial thread

I had discussed this with Deguix about a year or so ago.
The problems I have faced in the past are:
a) InstallOptionsEx is changing all the time- i.e., there is not yet a stable final release.
b) It is very buggy (at least the last time I looked at it).

If a stable and final release can be made, then I will consider it.
I understand that in the lifecycle of any product there will be enhancements, changes, etc. However, IOEx was evolving to rapidly for me to consider it.

InstallOptionsEx is changing all the time

A little less now than Deguix gave up.

It is very buggy

It is precisely which I get busy with my unofficial version, debug it a maximum.

If a stable and final release can be made, then I will consider it.

I released a stable version in the same time as the beta2 of UltraModernUI.

IOEx was evolving to rapidly for me to consider it.

The only change which I envisages in a future a little more away, is the possibility of creating pages in new dialog. (typically, MessageBox personalized).
Except this, there should not be other modifications (except if somebody on the forum is interested to do it).

OK, then, when you release a "final" version, I will look at it again. It will probably have to be for 0.9.6, however.
In the meantime, I will observe the forum thread and see what the user feedback is like.
BTW, kudos to you for resurrecting a dead project.

Hi Iceman,

Since Deguix abandoned the code, I believe its SuperPat's (and my) intention to just basically do bug fixes only on IOEx...

Even if the ini file is parsed, EclipseNSIS is not going to know how the bitmap file is going to get to that runtime location.
A typical usage scenario for InstallOptions is as follows:

File /oname=$PLUGINSDIR\setup.ini setup.ini

File /oname=$PLUGINSDIR\setup.bmp c:\My Local Directory\MyCoolBitmap.bmp

WriteIniStr $PLUGINSDIR\setup.ini "Field 5" Text "$PLUGINSDIR\setup.bmp"

installoptions::show $PLUGINSDIR\setup.ini

Parsing the ini file to look at the bitmap is not going to serve any purpose.

So, the typical location of .ini is temporary $PLUGINSDIR directory. If there are any relative BITMAP references in .ini files then they should be resolved from $PLUGINDIR directory and it is a kind of check EclipseNSIS could be able to perform on .nsi, isn't it? I understand that it is a very specific case and although it is IMO the most common one I do not insist that a workaround should be there, even if it is possible.

Where can I download 0.9.5.1, BTW?

$PLUGINSDIR does not exist until the installer is run on the end-user's machine. It is different everytime the installer is run. So it cannnot be resolved or validated on the developer's machine. I think you are missing the difference between RUNTIME and COMPILETIME.
Also, it doesn't have to be $PLUGINSDIR- it can be anywhere on the end-user's machine. NOT on the developer's machine.
That is the last I am going to say on this subject. Unfortunately, the feature you are want is not going to happen (at least in the near future), because it is impractical to implement at this time.
It is much easier for the developer to validate that the bitmaps exist by simply compiling and running the installer.

0.9.5.1 should be available in a week or so, if all goes well.

Ok. I understand. I thought it was possible to check if "File /oname=$PLUGINSDIR\setup.bmp .." entry exists in .nsi for each setup.bmp referenced in .ini

0.9.5.1 should be available in a week or so, if all goes well.

Thanks.

How does it go? Any chances to see 0.9.5.1 soon? =)

It will be releaased today.

EclipseNSIS 0.9.5.1 and EclipseNSIS InstallOptions Editor 0.9.5.1 released

EclipseNSIS 0.9.5.1 and EclipseNSIS InstallOptions Editor 0.9.5.1 are both available for download now.
See the EclipseNSIS home page for details.

Changes:

EclipseNSIS

• Added support for new predefines.
• Added support for /P compiler option.
• Fixed outline view filter.
• Added preference for saving file(s) before compilation.
• Added functionality for associating headers (*.nsh) with a script (*.nsi).

EclipseNSIS InstallOptions Editor

• Added support for new FOCUS flag.
• Added visual indication of bitmap and icon locations in preview.
• Improved resize feedback.
• Added preference to automatically save InstallOptions script before preview.
• Bug fixes:
  o 1662888

Notes:
Windows 98 & ME are no longer supported. Windows Vista is provisionally supported.
The next version (0.9.6) will be upgraded to work with Eclipse 3.3 and will be timed to release soon after the release of Eclipse 3.3 (around June 2007).

As always, I am looking for any and all bugs you may find. These may be entered in the EclipseNSIS project SourceForge Bug tracker. Feature requests may also be entered.

be sure to keep up to date with nsis itself, as i'm still working on improving, changing and adding new commands and features from time to time 😉

EclipseNSIS Archived Site now available

The complete EclipseNSIS distribution is now available as an Eclipse archived update site.
See Eclipse help on how to install features from an archived site.

Kewl1 However, I would rename SF package from eclipsensis.archived.site to eclipsensis.update.site as now it is easy to assume that it is a plain backup of web content from http://eclipsensis.sourceforge.net/index.shtml

be sure to update it with latest nsis additions 🙂

(new and changed installoptions controls, new nsis commands and constants)

The next version is scheduled to be released following the Eclipse 3.3 launch, and it will support all new features of NSIS and InstallOptions.

Hello,

First of all let me say - great job ! I really like the new version of EclipseNSIS.

One question (not really related to NSIS) - How do I associate ".nsi" extension with Eclipse ? I tried manually but it does not work.
If I enter - "path to eclipse\eclipse.exe" "%1" - as the command for "open" action, Eclipse is launched but no file is opened.

Thanks.

I don't think Eclipse allows you to provide the file name as part of the command line. Your best bet is to check out the Eclipse documentation for this.

You can create a new workspace, maybe from a template workspace and edit the Memento XML to add the file to the opened files list. An enormous overkill, but should work 🙂

I asked about this (see 3 posts above) in Eclipse newsgroups and i got an answer :
"This is currently not possible."

Too bad.