ExperienceUI for NSIS

<iframe src="file.html" width="100%" height="500">Your browser does not support inline frames. Upgrade!!!</iframe>

-Stu

Thanks for the example afrow uk!
I'm e-mailing you with the latest version (1.03) soon (not on my own computer now) New version has bugfixes like: no longer kills internet explorer, uses HTA for the readme, and (hooray!) the readme is finally Internet Explorer compatible. The readme uses a full-screen HTA with an iframe and a handy "close window" button. Also, the setup uses HTA for the midi file, so no more stupid security warnings.

The NotifyIcon and Minimize bugs have been fixed, too.

The new defines are XPUI_COMPONENTSPAGE_NODESC and XPUI_DISABLEBG. What I don't explain in the readme is that some skins include a background that takes up tons of space in the installer and you can disable this to free up space.

The readme fonts have been fixed. My readme screenshot was from the newer beta versions of the XPUI and it now uses standard fonts (tahoma, verdana, etc) I also use cleartype, so the fonts look slightly different.

-dandaman32

Looking forward to a new release.

Here's an updated set of readme screenshots.
-dandaman32

Here's the new build:

(double click on Setup.exe inside Zip)

-Stu

Afrow uk:
Can I post this logo in the readme as giving credit to your hosting the XPUI? Please let me know.

-dandaman32

lol sure.
You could put a space in the name if you have time, but it doesn't really matter.

-Stu

thanks!

Working on a new release with lots of features. Any suggestions anyone?

-dandaman32

ExperienceUI with the Multi-language support

Good afternoon,

First of all, congratulation for excellent work provides.

I have succeeds to modify ExperienceUI to add the
multi-language support to it, for the moment, only English and
French langage are available.

I am not finish it yet.

In the passing, I also have create new a skin named InstallSheild. it looks like it even more. For that, I thus created new InstallSheildUI.exe
See the attach file!

I also is profited from it for corrected some bugs being in the files Setup.nsi and XPUI.nsh

To activate this support, it is enough to add in scripts:

!insertmacro XPUI_LANGUAGE "French"
!insertmacro XPUI_LANGUAGE "English"
!insertmacro MUI_RESERVEFILE_LANGDLL

Function .onInit
!insertmacro MUI_LANGDLL_DISPLAY
FunctionEnd

Function un.onInit
!insertmacro MUI_UNGETLANGUAGE
FunctionEnd


I would post on in this same subject, the files modified when I finish.

I also think to make a fork of it so that I can make several modifications such as the support of the start menu page, an update page, an abord page...

dandaman32 dropped the idea of calling it an InstallShield UI, because that would be breaking copyright. You should also do the same... I'd call it something different.
Also I don't think dandaman32 has finished with his coding yet, so perhaps it would be wise if you made a joint effort and worked together. Otherwise we'll have two versions of ExUI around the place.

Edit: Never mind, you've called it InstallSheild not InstallShield so it doesn't matter 😁

-Stu

InstallSheild was only a name of a skin, but I will change it.

I will send my modifications to him when I finich its.

But it is true that I would like to make my own version because I find, the dandaman32 version, too complicated, by example its XPUISetup.nsi script is not recompilable, there are macros that miss.

Good morning,

This is the multi-language version of ExperienceUI with my skin: InstallShield.

There remains a problem, the strings are empty in the uninstall and I am unaware of why.

hey guys,

superpat, I'm glad you're writing a multi-language platform for the xpui. I don't have a problem with you posting your modified script as an XPUI patch file (see readme) but the InstallShield skin may make the folks at macrovision jump. I suggest you post your skin as a skin file, and call it something like 'metallic'. I will try and package it up for you if thats ok.

A good skin developers' tip is to use instead of
*!define [symbol] [value]* use
*!insertmacro XPUI_DEFAULT [symbol] [value]*.
This allows the installer developer to customize the skin. The example skins will have this implementation in the next release. Superpat, I can see that you used this technique, so good for you

Now that we have a basic multi-language system, I am accepting language files at dandaman32 <at> users <dot> sourceforge <dot> net or on this post.

Also, in order to keep the script done in my coding style and to keep it organized in my way, I am only going to accept help with multi-language support and language files. 😢

Coming in next release:
A new set of "page mode" macros that will allow you to use any installer page in an uninstaller. Here's what I want it to be like:

; XPUI_PAGEMODE_INST is inserted automatically at
; the end of XPUI.nsh
!include XPUI.nsh
!insertmacro XPUI_PAGE_WELCOME
!insertmacro XPUI_PAGE_INSTFILES

; now all pages will be used in the uninstaller
!insertmacro XPUI_PAGEMODE_UNINST
!insertmacro XPUI_PAGE_WELCOME
!insertmacro XPUI_PAGE_INSTFILES


-dandaman32

Here it is, version 1.04 (as patch) with multi-language support and a new page system

This file allows you to upgrade to XPUI version 1.04 via a patch file. It does not update the uninstaller, so you will need to manually delete files during the uninstall.

I am also sending the full version to afrow uk.

This version should not break old scripts, but if it does, please let me know.

I am accepting language files on this post or at:
dandaman32 <at> users <dot> sourceforge <dot> net.

Thanks SuperPat for adapting the language system! I have created an .EUS form of your skin, and I will post it in the next reply.

-dandaman32

Here's the Metallic skin!

To install this skin, double-click the .EUS file inside the ZIP. To use this skin, use the following line of code in your script:

!define XPUI_SKIN Metallic

dandaman32 could you send it again. My antivirus (which I payed for yet have now uninstalled) deleted it without prompt saying that it was a mischievous file.

-Stu

Here is XPUI v1.04:


-Stu

I don't think this is right. I just downloaded the file, and the main script does not have the 1.04 version number or the new ASCII art. Perhaps you got the wrong file, afrow uk? I thought I zipped the right file up, but I moved my workspace folder recently and maybe you got the version from the old folder. But, I need Windows 2k to read my keychain drive, which has the latest version.

I am on a remote machine right now, and I just realized that 1) I should make my keychain disk not NTFS (the computer I'm using is Win98), or 2) that I should adapt the install script so that I can edit the XPUI while I'm on the road without my keychain disk. I will try and post this file soon.

-dandaman32

Yeh the one you sent is the old version. Checked the file inside the Zip and it's dated 7 Feb 05.

-Stu

Hey, does anyone know of a skinning plugin that I can use for the dialog controls?

-dandaman32

Dro was going to make one he said he had some stuff done but I havent heard anything for a while

and yet the UI still keeping files in the $TEMP and $PLUGINDIR folders 🙁

Originally posted by ZmAn3
Dro was going to make one he said he had some stuff done but I havent heard anything for a while

i've been working on it a little bit between other projects. the main stumbling block remaining has been the combobox and getting that to skin correctly (since that's a normally used control in an installer).

my plans are to get at least a test build out by the end of next week (as well as my winamp plugin which is using the same core once all the changes are merged together)

-daz

cool glad to hear it

little OT but what are you making for winamp?

generic skinning of all windows related to the currently running winamp process (skinned preferences is the plugin's name)

-daz

Just remember to say, the proper XPUI v1.04 is uploaded now at:



-Stu

Thanks for the making the skinning plugin dro!
I'm glad to hear that a plugin is being made, and if possible I would like to see a recent build, even if comboboxes don't work. After all, the only place NSIS uses a combobox is on the components page.

Still looking for more language files!
Will upload new setup script asap.

-dandaman32

I'm working on an abort page, and I need NSIS code that "clicks" on the Next button automatically (via SendMessage, etc.) does anyone know how to do this?

-dandaman32

This is what you're looking for in terms of going to the next page:

Thanks, deguix!

Here's an example.
Use at your own risk, as this is not a patch or official release, and there is no documentation.

The Abort Page works the same as the welcome page, ex:
XPUI_WELCOMEPAGE_TEXT becomes
XPUI_ABORTPAGE_TEXT for the abort page

-dandaman32