How about a GUI

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

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.

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.

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

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.

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.

I started to program a NSIS Gui.

If anyone want to join this small project, you are welcomed to contact me:
ranmanor@iname.com .
(or if he wants me to join him...).

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.

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.

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?

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.

GUI Frontend

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

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

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

/me jumps in on the parade...

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



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.

oh... forgot something... Wouldn't it be just that much easier if the script builder also compiles? Just a thought. In that case, it'd have to be built in C++, considering that's the language of NSIS.

one from the archives

boy did i save the day or what? 🙂

just a few months late is all 🙂

cya

Brings back memories... 🙄 😕 🙂 😁

Hehehe... yeah it sure does Koen! 😁

I gave up the total Easy Nsi Generator project btw. Haven't had any application to pimp. But I'll start to take a look at NSIS again soon. 😉

GUI for NSIS

I am working on a GUI for NSIS; it already works, the software speaks english but the docs are in german (no time for translation). If anyone here in the forum is interested in viewing/testing the beta, I would post the archive (currently 53KB rar archive) here in the forum.

If you like to take a look on how i work first, then visit http://www.smarty-online.de

SmartyMan

heh, is it just me or do other people find GUIs annoying? I had no trouble at all getting my NSIS script up and running. The provided documentation was enough to get me started.
I read through MakeNSIS.html and the examples before I got started. This way I was familiar with NSIS's abilities and the way it worked.

With a GUI your installation script will only be as powerful as the GUI allows it to be. Further "touching" up can be done by hand, of course, but at that point why not write the whole thing from scratch?

What would be more useful is a bunch of generic templates for people to use. (such as full working scripts with a few variables for them to change) This would help the newcomers by giving them a head start and allow them to add/modify as they see fit. And better yet, you won't be limited by a GUI and bothered with updating it with every NSIS release. In my opinion I think this serves a better purpose.

---
With a GUI your installation script will only be as powerful as the GUI allows it to be. Further "touching" up can be done by hand, of course, but at that point why not write the whole thing from scratch?
---
So you do your programming using a DOS-Console and with makefiles, instead of (for expample) viaual studio or somthing? 😉
Of course a GUI for NSIS must support script editing by hand, and of course there is no real need for a GUI when making trivial/little installers.
Imagine a installer for about 600 files and 90 folders - would you want to type all the SetOutDir/File etc commands by hand?

If you have no need for a GUI - fine, but I think that the existing of this thread proves, that other users have.

Originally posted by SmartyMan

Imagine a installer for about 600 files and 90 folders - would you want to type all the SetOutDir/File etc commands by hand?

If you have no need for a GUI - fine, but I think that the existing of this thread proves, that other users have.

In some cases a GUI can be time-saving and practical. But I think the main reason for a demand lies in the fact that some people don't want to make the effort and spend the time to write their own script. They just want to click a few buttons in a wizard-guided interface and be done with it.

It just surprises me that someone would take the time to write a piece of software and not take the time to learn NSIS to package it. The script only has to be written once (and in some cases modifed from time to time) so it's not a big headache. (it was a breeze to write my first script (using ver. 1.h) and I have enjoyed adding new features to it when new versions of NSIS came out) This is why I think templates would come in handy.. it would allow the lazy folks to modify a few strings/variables and be done with it. (but maybe I am wrong, who knows.. maybe there are more point-and-click folks out there than I thought)

Originally posted by spanky

In some cases a GUI can be time-saving and practical. But I think the main reason for a demand lies in the fact that some people don't want to make the effort and spend the time to write their own script. They just want to click a few buttons in a wizard-guided interface and be done with it.

I agree with that - but in this context your posting sounds to me like you want to punish those guys.
I am often angry with my clients as they dont read the docs and calling our support hotline instead, wasting their time with asking "stupid" questions, but is that a reason for removing all the docs from our products?
As you said, GUIs can be practical and time saving, so lets focus on that o make our life a little easier🙂

Originally posted by SmartyMan

I agree with that - but in this context your posting sounds to me like you want to punish those guys.
I am often angry with my clients as they dont read the docs and calling our support hotline instead, wasting their time with asking "stupid" questions, but is that a reason for removing all the docs from our products?
As you said, GUIs can be practical and time saving, so lets focus on that o make our life a little easier🙂

I didn't meant to come across that way at all! 😁
It's just that most NSIS users are developers and most developers are not the wizard interface point-and-click types.
Either way it's great to see others making an effort towards making NSIS an easier, more user-friendly application.

(um, if I didn't make any sense it's because I am wasted right now.. I just came back from the bar. !!!)

Originally posted by spanky


It's just that most NSIS users are developers and most developers are not the wizard interface point-and-click types.
Either way it's great to see others making an effort towards making NSIS an easier, more user-friendly application.

Ad 1: Maybe I am not a real developer, because I like to create new Methods by rightclicking the class using the context menu, and I like juming direktly to the desired function in a 7000 lines class using a combobox with autolocator 😁
Ad 2: I agree with that, but maybe you're right with 1. since there are no requests according to my GUI from the forum members so far.
I can live with that - less testers means less work for me 😉

i played a little bit with my vb
and made a nsis analyzer
now i can parse a nsi script and put it into a tree

some more functions for READING a existing file are also in there
if I'll get it i'll try to write changes back

GUI for NSIS: NSISplus V0.80

Originally posted by crish
i played a little bit with my vb
and made a nsis analyzer
now i can parse a nsi script and put it into a tree

some more functions for READING a existing file are also in there
if I'll get it i'll try to write changes back

Maybe you should take a look at this file before you proceed.
This GUI ist nearly finished and primarly needs some beta testing before it gets a "1.00" version number.

Any comments are welcome.

has anyone tried using the php NSIS generator at the firehose.net site, fairly simple. But like Smarty Man said your script could only be as powerful as the gui.

try it at https://www.firehose.net\free\nsis\m...template.phtmlwww.firehose.net\free\nsis\makensitemplate.phtml

no the available functions in nsisplus arent enough for me
i wanted to have a windowed version of nsis that support almost all
possible things in there with the comfort of a tool like setup factory

i use the tree only for analysing my script

i try to add wizards and forms for adding removing sections functions vars registry stuff language support and much more