Announcement

Collapse
No announcement yet.

ExperienceUI for NSIS

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ExperienceUI for NSIS

    I have created a new UI for NSIS. It's formally called the InstallShield UI for NSIS, but for now I'll just call it the ISUI.

    I don't have a web site (yet) but I am going to email KiCHIK about it and it should be released soon. I would appreciate help writing an extensive multi-language support system, so if anyone would like to pitch in on that it would be great.

    Because of file size limitations on the Winamp forum server, I can't include the setup program here, but KiCHIK should post the file on http://nsis.sourceforge.net.

    I can, however, include the screenshot utility (see attached file)

    Any ideas, comments, and suggestions are welcome at dandaman32 <at> users <dot> sourceforge <dot> net.

    -dandaman32
    ExperienceUI for NSIS | Latest project: Enano CMS
    Do not PM me on the Winamp forums, I hardly ever check my messages here; you are more likely to get my attention through the ExperienceUI forum.

  • #2
    Send to afrowuk at tiscali dot co dot uk and I can host it for you until Kichik does.

    -Stu

    Comment


    • #3
      Here we are everyone!

      http://myweb.tiscali.co.uk/imker/dow...ISetup_1.0.zip

      -Stu

      Comment


      • #4
        For the design and implementation, I give you 10/10! This is truly amazing!

        Now onto the scripting side of it. Firstly you can fix the problem of having to !include your header file after !defines by using !macro's instead. Have a look at my Self-Extractor header file. Every setting is set via an !insertmacro (which are hidden in-turn by more !defines).

        The problem with the text.htm page not being displayed inside your ISUI Readme.html page (on IE), is because you've set a classid that defines a page 'Print' button, whereas you want to display an HTML document! Remove the classid code and it'll work in IE.
        Also you do not need ActiveX for this.

        -Stu

        Comment


        • #5
          is there an .nsi example file forthcoming that uses the isui ?
          or, do you allready have one in there...
          looks great

          Comment


          • #6
            is it just me or does the installer leave some files in the temp dir ($plugindir not deleted?) not sure if the problem is with the nsis super packer(whatever the fuck that is) or the installer itself
            IntOp $PostCount $PostCount + 1

            Comment


            • #7
              I like design (yes, 10 points), but:
              1) some windows flashes on installer launch and later on page changes, looks bad;
              2) it stealed my IE window, where I already wrote a big part of this post;
              3) ICQ window (was hidden) suddenly appeared on a short time in the left bottom corner of screen and later in it's normal position (screen right border), but ICQ lost it's XP stype (window corners). I reloaded ICQ and repeated installation start, ICQ bevaviour was absolutely the same as in the first time.
              Like Anders I see 4 plug-ins in tmp dir (incuding nsExec).
              Installer bugs looks dangerous.
              Good news - antivirus check OK.
              Win2K Server Rus

              Comment


              • #8
                I don't think this is legal. The interface is probably copyrighted and you are using a registered trademark of a company.

                Unless you have permission for both things, it would recommend you not to release this UI in the current format. Hosting it on the NSIS site or NSIS archive is therefore also not possible.

                However, it could be a nice start for a custom UI, if you design your own graphics and use another name.

                Comment


                • #9
                  That's a very good point
                  I don't think including notepad.exe in your installer is a good idea either (you should make a shortcut instead through the installer)!

                  -Stu

                  Comment


                  • #10
                    Well... is cool alright... but the installer left this window after I cancel the installer..

                    And the temp folder still having some files, not plugindir...
                    Attached Files

                    * PC: Intel Core 2 DUO E6550 @ 2.33 GHz with 2 GB RAM: Archlinux-i686 with MATE.
                    * Laptop: Intel Core 2 DUO T6600 @ 2.20 GHz with 4 GB RAM: Archlinux-x86-64 with MATE.

                    Comment


                    • #11
                      *sorry double post*

                      * PC: Intel Core 2 DUO E6550 @ 2.33 GHz with 2 GB RAM: Archlinux-i686 with MATE.
                      * Laptop: Intel Core 2 DUO T6600 @ 2.20 GHz with 4 GB RAM: Archlinux-x86-64 with MATE.

                      Comment


                      • #12
                        Thanks for bug reports everyone!

                        I've written fixes for many of these, and some other behaviors are intentional.

                        First, I include Notepad to serve as an "example" program. One bug that I noticed is that I had a setup.nsi for Notepad, but it got overwritten when I extracted the setup.nsi file for the main ISUI setup program. This bug was fixed by renaming the ISUI installer setup.nsi to ISUISetup.nsi. The Notepad setup is now setup.nsi.

                        Second, the temp files bug was fixed by a macro (ISUI_TEMPFILES_DELETE) in version 1.01. This is about to be sent to Afrow UK. Sorry about this...I've had some bad experiences with the $PLUGINSDIR variable, and I just had to use $TEMP instead.

                        Third, the flashes. This is unavoidable, but nearly nonexistent with fast machines. This is because NSIS resets all of the control colors for the pages when you click Next or Back.

                        Fourth, the mystery window. (for lobo lunar) The ISUI 1.0 setup program has to minimize all open programs, and your window had the #32770 class (probably) and the setup tried to "minimize" it. This bug is fixed in 1.01 by using a customized "show desktop.scf" file.

                        Last, the name and UI. First, I did (sorry) start with the Modern UI and added lots more features, but in respect for the NSIS license I did give credit where credit is due ("If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.")

                        Thanks for hosting afrow uk, and thanks once again to all who gave bug reports! Your input is greatly appreciated!

                        I dont know how attatchments work yet because i'm new to the winamp forums. obviously the screenshot app didn't go through. sorry.

                        The new version's setup is known to crash sometimes, but this is because of the MSIBanner plugin (sorry, lobo lunar). This has been proven by creating a test program without the ISUI implementation. If you get problems, try again or restart your pc and this should go away. If it doesn't, run setup with the /SafeMode cmd line switch to disable optional plugins.

                        Any other comments are welcome on this post and and at my email (see above)

                        -dandaman32
                        Last edited by dandaman32; 15 January 2005, 19:01.
                        ExperienceUI for NSIS | Latest project: Enano CMS
                        Do not PM me on the Winamp forums, I hardly ever check my messages here; you are more likely to get my attention through the ExperienceUI forum.

                        Comment


                        • #13
                          p. s. i also dropped the nsis superpacker
                          ExperienceUI for NSIS | Latest project: Enano CMS
                          Do not PM me on the Winamp forums, I hardly ever check my messages here; you are more likely to get my attention through the ExperienceUI forum.

                          Comment


                          • #14
                            I am aware that you put notepad in for editing scripts, but the fact that you included the exe would be illegal...
                            Also being that you have included the Windows XP version of notepad means that it probably won't run properly on Win9x anyway!
                            Just make a shortcut to notepad.exe instead:
                            CreateShortCut "$SYSTEM\notepad.exe"

                            And you'd better create your own UI design. Else Macrovision (the InstallShield company) might be on your back pretty soon...

                            -Stu

                            Comment


                            • #15
                              why MSIBanner gives problems?
                              It uses the same thread procedure like Banner does...

                              * PC: Intel Core 2 DUO E6550 @ 2.33 GHz with 2 GB RAM: Archlinux-i686 with MATE.
                              * Laptop: Intel Core 2 DUO T6600 @ 2.20 GHz with 4 GB RAM: Archlinux-x86-64 with MATE.

                              Comment

                              Working...
                              X