How about a GUI

[PiBe]

I like NSIS, but now it have much variables.
How about to make a GUI, i think it´s a good idea.

[PabUK]

I thought about making one but I don't have the time. Anyone else care to give it a try? It would be very difficult to keep up with all the new versions of NSIS but it would give those people put off by scripts a nice system to work with.

[Koen van de Sande]

Good idea, a GUI. But at the moment, I don't have time to create it. It would't be too hard - but it depends on what you want in there.

First, you need a page with some generic settings (SetCompress, SetDateSave, etc).
Then you need a page with the different sections (a list), and you can modify them. But in such a program, you can't do anything 'cool' with if-statements and such, because it's too complex.

I'll think about it. Is anyone else already working on this? I can't start for another 3 weeks.

[PabUK]

I wouldn't mind helping out if I have the time, but I only program in Visual Basic.

[Bor]

I also thought of it. But if you program it you got to keep in mind the constant adding of features. I mostly program in Delphi.

[Koen van de Sande]

Well, I can do both Visual Basic and Delphi. But creating a good design is very important.
It should contain 'macro' functionality, for example, you can set for an OCX file 'Register' and then it's automatically added to the script. Same for version checking (but that's not implemented in NSIS yet).

After Easter, I'll have time to work on it. Personally, I'd go with Delphi because it doesn't require all those pesky Micro$oft Runtimes.

[RM]

I started to program a NSIS Gui.

If anyone want to join this small project, you are welcomed to contact me:
[email protected] .
(or if he wants me to join him...).

[PabUK]

RM you didn't mention what programming language you are using so how do we know if we can help? Please specify!

I too have started an NSIS project, but not a GUI. Its called NSIS Assistant and is just for editing the script files and compiling them without having to copy makensis everytime you create a setup for a new project.

[RM]

I forgot to mention it, stupid me. =)
I'm using Visual C++ .

I thought making the GUI as a wizard.

If anyone has ideas for the gui, please mail me....
thanks.

[Koen van de Sande]

A wizard is nice, but you should be able to save your project, and open up the wizard again later (to add some files, etc).

You could make a wizard with Tab pages, where every page is a step, so you can easily switch between steps.
Ease of use is important.

But more important is maintaining script integrity. If you make a change to an existing script, it shouldn't mess up the script.

Just my thoughts. I can't help because I don't know C++. Isn't a 'lower-level' language like VB or Delphi easier for these 'GUI-oriented' applications?

[rainwater]

Most likely you would create a project file that would store the settings in a standard format your program can read. Then it could generate the script. But unless you are buiding some type of parser, it wouldnt be able to read .nsi files. It would be sort of a nsi compiler that compiles project files to .nsi not the other way around.

[dallas_k]

GUI Frontend

I Started working on one last Sunday.
Download it from my WebSite. Comments, complaints, etc. are welcome.

[johnni_m]

the Pimpette, great so far, but it would be nice with a open function, everytime you make an update you have to make a new script

[dallas_k]

Yes that would be nice. I will work on that also.

[rm']

/me jumps in on the parade...

It's definetely not a gui, but it's close to a wizard

http://www.easynsigenerator.da.ru

It's done in... believe it or not... Pascal Turbo.


I'm helping Kaboon get in a real GUI... so far, it does the basics... not very extensible though. As of yet, you can only get in a max of 64 installation files, but it's a start. In VB (yes... ms runtimes are evil, but it's all I know). When Kaboon decides to release it, you can all see it.

Sadly, you can't pick up where you left of.