Hello Sunjammer and LsMoNKi,
basicly i understanded what you want/mean. But i am not able to create XML/XSL - files from the HTML-file. When anyone create the XML/XSL - files from the HTML-file then i try to implement it in N²E.
Thank you for your help!
Fiffi
Nsis-gui
70 posts
I didn't expect you to 😉 - Someone with more knowledge of XML than me would need to do that (well I can find out how if needs be) and an appropriate structure for the XML would need to be defined... that would probably take a couple of attempts. It's a good little side project for anyone who's interested (if I get time I'll attempt this).
has anyone look at NSIS WOrkbench, or Slate Blue? Slate Blue is open source, VB :P
Workbench is delphi tho, maybe ask him.
search the forums for the answers.
Workbench is delphi tho, maybe ask him.
search the forums for the answers.
Some info I made about both products a while back :-
well, if the help file is rewritten in XML, it may replace the original HTML one in the NSIS pack... 😁 !
The only problem is that old browser are not able to understand XML language 🙁 🙁 🙁 !
The only problem is that old browser are not able to understand XML language 🙁 🙁 🙁 !
The XML file would still be valuable if we were to distribute with NSIS the HTML generated from the XML because the XML can be parsed more easily by computer programs. It's common for programs to distribute files in different formats, we have an even better excuse in this case since the XML format isn't just meant as an alternative format for humans to read as would a PDF be for example. Distributing both would solve the old browser problem and provide the XML benefits at the same time.
Most developers have recent browsers anyway 😁
Few Internet browsers have full support for XSL at the moment.Source: http://www.w3schools.com/xsl/xsl_browsers.asp
---------------------------------------------------------------------
Internet Explorer 5 is Bad
XSL in Internet Explorer 5 is NOT compatible with the official W3C XSL Recommendation.
When Internet Explorer 5.0 was released in March 1999, the XSL standard was still a W3C Working Draft.
Since the final W3C XSL Recommendation is different from the Working Draft, the support for XSL in IE 5 is not 100% compatible with the official XSL standard.
This restriction applies to both IE 5.0 and IE 5.5.
---------------------------------------------------------------------
Internet Explorer 6 is Better
Internet Explorer 6 fully supports the official W3C XSL Recommendation.
The XML Parser 3.0 - shipped with Internet Explorer 6.0 and Windows XP - is based on both the W3C XSLT 1.0 and the W3C XPath 1.0 Recommendations.
---------------------------------------------------------------------
Netscape 6
Netscape 6 isn't fully supporting the official W3C XSL Recommendation.
---------------------------------------------------------------------
Internet Explorer MSXML Parser
MSXML Parser 2.0 is the XML parser that is shipped with IE 5.0.
MSXML Parser 2.5 is the XML parser that is shipped with Windows 2000 and IE 5.5.
MSXML Parser 3.0 is the XML parser that is shipped with IE 6.0 and Windows XP.
According to Microsoft, the MSXML Parser 3.0 is 100% compatible with the official W3C XSL Recommendation: "MSXML 3.0 offers a significant advancement over MSXML 2.5: server-safe HTTP access, complete implementation of XSLT and XPath, changes to SAX (Simple API for XML), higher conformance with W3C standards, and a number of bug fixes."
Hello LsMoNKi,
i am thinking about the best technique to implement the NSIS-script-help. My problem is that i don't know anything about XML/XSL.
Is anywhere a MS-VC++ example which uses XML/XSL? Or can you help me?
Thank you for your help!
Fiffi
i am thinking about the best technique to implement the NSIS-script-help. My problem is that i don't know anything about XML/XSL.
Is anywhere a MS-VC++ example which uses XML/XSL? Or can you help me?
Thank you for your help!
Fiffi
I'm new in xml/xsl too. Maybe somebody can help you.
However a good point to start is Expat, a xml parser library written in c.
However a good point to start is Expat, a xml parser library written in c.
Originally posted by Sunjammeri just love the review of Slate Blue, very heartwarming to see such nice words about my product 🙂
Some info I made about both products a while back :-
http://www.clantpa.co.uk/nsis/wiki/index.php/SlateBlue
i guess it is to be assumed that people would say this, because Slate Blue is, as you so succinctly put it, 'unfinished'.
🙂
As an unfinished program there was quite a bit for me to comment on and I guess some if not all of the points I raised would be addressed if there were to be another version.You've written something bigger & better for NSIS than I have so I felt a little guilty reading that page again but after downloading and playing with Slate Blue once more I can't really fault what I said.
Maybe the comments I made will be of interest to anyone who develops a new NSIS editor or similar program. On that front I think people interested in writing a new editor *should* download and try Slate Blue because it has a few interesting ideas, the NSIS dll that can be used for compilation for example.
Maybe the comments I made will be of interest to anyone who develops a new NSIS editor or similar program. On that front I think people interested in writing a new editor *should* download and try Slate Blue because it has a few interesting ideas, the NSIS dll that can be used for compilation for example.
i think sometime i may finish up Slate Blue, but in Delphi rather than VB.
one thing that I find interesting is that Workbench uses almost all premade components, that comes with sytax coloring, etc etc, while I had to write mine from scratch. of course it'll be a little buggy 🙂
and i do think that should someone decide to write a new GUI, they should look at both GUI's out there to gain some good ideas. the DLL is kind of a moot point, however, because it is rarely updated (or was when I was writing SB).
no harm done really 🙂 i take all the comments, negative or positive, as a way to improve my software.
look for a new version out before years' end i hope 🙂
one thing that I find interesting is that Workbench uses almost all premade components, that comes with sytax coloring, etc etc, while I had to write mine from scratch. of course it'll be a little buggy 🙂
and i do think that should someone decide to write a new GUI, they should look at both GUI's out there to gain some good ideas. the DLL is kind of a moot point, however, because it is rarely updated (or was when I was writing SB).
no harm done really 🙂 i take all the comments, negative or positive, as a way to improve my software.
look for a new version out before years' end i hope 🙂
As N²E 's developpment has just began, we try to get ideas about features !
The first thing we've done was to see all existing editors (StateBlue, Workbench, NSISplus...) and get their good and bad things... we'll of course get the *best* of them 😁 😉
We'll try to bring new features too 🙂
The first thing we've done was to see all existing editors (StateBlue, Workbench, NSISplus...) and get their good and bad things... we'll of course get the *best* of them 😁 😉
We'll try to bring new features too 🙂
There's another editor called Venis and yet another called NSIS Assistant.
The only reason that the NSIS Workbench isn't open source is that it
uses commercial components, some don't have freeware alternatives of
the same quality although one or two could be changed to freeware
components/coded by hand.
Not sure if aiming to create a rival for innosetup
never mind Wise/Installshield is realistic, definitely can't imagine
it being better (partly due to NSIS "shortcomings" like installing
locked files), but I suppose aim high! To get anywhere near to
rivalling them it needs to be run both in editor and gui/wizard mode
and be able to swap between the two modes as required, not easy.
Also creating an open source app is good but the reason "because NSIS
is" isn't IHO. Finally of course one person writing an app is one
thing coordinating a group of coders is a completely different
ball game requiring a lot of planning and documentation.
Marc
uses commercial components, some don't have freeware alternatives of
the same quality although one or two could be changed to freeware
components/coded by hand.
Not sure if aiming to create a rival for innosetup
never mind Wise/Installshield is realistic, definitely can't imagine
it being better (partly due to NSIS "shortcomings" like installing
locked files), but I suppose aim high! To get anywhere near to
rivalling them it needs to be run both in editor and gui/wizard mode
and be able to swap between the two modes as required, not easy.
Also creating an open source app is good but the reason "because NSIS
is" isn't IHO. Finally of course one person writing an app is one
thing coordinating a group of coders is a completely different
ball game requiring a lot of planning and documentation.
Marc
Sunjammer, I've just seen your page, glad you like the Workbench. Also liked your comment "hmm looks cute, I bet it's useless" :-) But cute and useful must have done something right!
Not sure if aiming to create a rival for innosetupI'm not sure that it needs to be like them to be better, personally I can't stand InstallShield and it's user interface and wizards. I think the reason NSIS attracts some people is just that, it *isn't* InstallShield. As for the others, well I've never used InnoSetup so I can't comment, but I can't remember seeing a Wise installer I liked the appearance of (mind I can't remember one giving me any trouble either).
never mind Wise/Installshield is realistic, definitely can't imagine
it being better
partly due to NSIS "shortcomings" like installingAt least with an open source app we have the ability to correct these shortcomings. Admittedly this is no use to people who have no coding ability or no interest in being a coder.
locked files
It's nice to see some opinions that are different however, most of what has been said so far has been by people agreeing one way or another 😁
As for NSIS Workbench, yeah I liked it. The sign of a good app is one I actually find myself using, NSIS Workbench made the grade on that test.
Originally posted by mkeeleyof course not, but open source would be nice. and i'm sure we could get a hold of the components you used 🙂 legally, of course.
Also creating an open source app is good but the reason "because NSIS
is" isn't IHO.
but, whatever you wanna do man, it's your software.
good work, btw 🙂
I could try and remove as much of the commercial components as I can but by the sounds of it people like the idea of starting their own project from scratch, and why not.
I haven't quite worked out what the aim for the new project is other than aiming to be a rival for... If it's a similar type of program to the Workbench then that, whilst not pointless, seems a bit of a waste of coding effort and trying to get mine open source but requiring certain commercial components to be able to develop it isn't such a bad idea. If the project is more ambitious which would really mean a two way editor/gui in the same way as Wise then that's something that would need to be started from scratch.
One final comment is that I think work needs to be done on the NSIS installers GUI, the bit the user sees. Unless things have changed then it looks practically the same as it always had. When it was first released it looked OK but these days looks distinctly old fashioned and I personally wouldn't use it for anything other than distributing freeware. Definately could do with a make over (unless someones done, this haven't kept up to date with the forum recently).
Marc
I haven't quite worked out what the aim for the new project is other than aiming to be a rival for... If it's a similar type of program to the Workbench then that, whilst not pointless, seems a bit of a waste of coding effort and trying to get mine open source but requiring certain commercial components to be able to develop it isn't such a bad idea. If the project is more ambitious which would really mean a two way editor/gui in the same way as Wise then that's something that would need to be started from scratch.
One final comment is that I think work needs to be done on the NSIS installers GUI, the bit the user sees. Unless things have changed then it looks practically the same as it always had. When it was first released it looked OK but these days looks distinctly old fashioned and I personally wouldn't use it for anything other than distributing freeware. Definately could do with a make over (unless someones done, this haven't kept up to date with the forum recently).
Marc
As of the NSIS 2 KiCHiK branch you have XP styling, replaceable dialogs, and I believe he and Rainwater (think it was Rainwater) are sposedly working on some kind of InstallShield look. I've seen some very tasty looking dialogs (or at least images of) posted on this forum recently using KiCHiK's changes so I think things are either better than you think, or else you just really hate the NSIS style 🙂
The customisable GUI is good news, not sure I've found the screenshots you're referring to though. The default interface is the main reason I'm not using NSIS and therefore why I've not really considered doing a Workbench+
If it's the set of pages and the controls that are on them that you don't like you won't be impressed 'cause although you can tailor and add to what is there thru resource hacking the NSIS underneath still expects the same controls.
Hard to say without seeing an example, but if they look fairly similar to the latest Wise/Installshield versions then that would be fine. Even little things like not having Cancel as the first button would be a start though. I know changing minor things like that are easy enough, assuming you have VC++, but you shouldn't really have to.
I'm working with KiCHiK on an interface like InstallShield/Windows Installer. 😁
This new UI should be ready very soon 😉
If it's the set of pages and the controls that are on them that you don't like you won't be impressed 'cause although you can tailor and add to what is there thru resource hacking the NSIS underneath still expects the same controls.It's now possible to add new elements to the dialogs (which can be controlled by the script).
This new UI should be ready very soon 😉
Funky!
Guys,
You have been discussing about a frontend I think that I have a brilliant idea ;-).
All the "front-ends" that I have seen for NSIS are just better text editors, loaded with more-and-more functionality suited for NSIS script developing.
How about a "Object Oriented" front end, where the user gets to see the different stages of the installer (say a tabbed interface) where he gets to type in the necessary modification for the different texts, looks, etc.
e.g: if, say, he chooses "XP style" on, the the picture changes from the default look to a "XP style" image.
What this does is that it gives a wizard-like appeareance to the "front-end". This will make users switch from the easy-to-use interfaced installers to NSIS !!! Yay !!!
The script editor also will have to be a part of this "NSIS Designer" so that any modifications in the settings in one place will reflect in the script in the script editor, kinda like ISTool for innosetup.
How 'bout that idea !!!
- Shantanu
You have been discussing about a frontend I think that I have a brilliant idea ;-).
All the "front-ends" that I have seen for NSIS are just better text editors, loaded with more-and-more functionality suited for NSIS script developing.
How about a "Object Oriented" front end, where the user gets to see the different stages of the installer (say a tabbed interface) where he gets to type in the necessary modification for the different texts, looks, etc.
e.g: if, say, he chooses "XP style" on, the the picture changes from the default look to a "XP style" image.
What this does is that it gives a wizard-like appeareance to the "front-end". This will make users switch from the easy-to-use interfaced installers to NSIS !!! Yay !!!
The script editor also will have to be a part of this "NSIS Designer" so that any modifications in the settings in one place will reflect in the script in the script editor, kinda like ISTool for innosetup.
How 'bout that idea !!!
- Shantanu
Hello friends,
Sorry for the late reply, but i was in holiday.
This evening i reply...
Fiffi
Sorry for the late reply, but i was in holiday.
This evening i reply...
Fiffi
include a general presentation of the project... features could be added then, for future version (😁) !
-- most important --
Needed developers:
==================
Base skills:
------------
-good skills at MS-VC++ and MFC
Additional(, but we need one person with this skills...) skills:
------------------------------------------------------------------
-XML/XSL
-UNICODE (and when the application is not complete UNICODE...)
-CVS at soucreforge...
-- most important --
Needed developers:
==================
Base skills:
------------
-good skills at MS-VC++ and MFC
Additional(, but we need one person with this skills...) skills:
------------------------------------------------------------------
-XML/XSL
-UNICODE (and when the application is not complete UNICODE...)
-CVS at soucreforge...
NSIS Editor - Venis 1.0.3
Hello everyone,
I have just added a new feature to Venis so now I can say it is more than just a text editor. http://www.spaceblue.com/venis/
I added a new MessageBox Wizard. I designed the dialog for future use, if I get positive feedback.
To use the MessageBox Wizard, you drag the new "MessageBox Wizard" icon to the line of your choosing in your NSIS code. Then when you drop the MessageBox wizard (let go of the mouse click), a MessageBox Wizard appears.
The MessageBox Function Wizard will put the function arguments together for you. The text message for the message box will be properly quoted using the first logical quote that was not used in the message in this order: ", ', `. The Select button allows you to select one message box option at a time. Each option is appended to the current options. Return checks are selected in the same fashion. At any time you may press the F1 key to open the makensis.htm file to the specified MessageBox section.
Please check it out and give me some feedback. http://www.spaceblue.com/venis/
Thanks,
Angelo
Hello everyone,
I have just added a new feature to Venis so now I can say it is more than just a text editor. http://www.spaceblue.com/venis/
I added a new MessageBox Wizard. I designed the dialog for future use, if I get positive feedback.
To use the MessageBox Wizard, you drag the new "MessageBox Wizard" icon to the line of your choosing in your NSIS code. Then when you drop the MessageBox wizard (let go of the mouse click), a MessageBox Wizard appears.
The MessageBox Function Wizard will put the function arguments together for you. The text message for the message box will be properly quoted using the first logical quote that was not used in the message in this order: ", ', `. The Select button allows you to select one message box option at a time. Each option is appended to the current options. Return checks are selected in the same fashion. At any time you may press the F1 key to open the makensis.htm file to the specified MessageBox section.
Please check it out and give me some feedback. http://www.spaceblue.com/venis/
Thanks,
Angelo