dandaman32
23rd January 2005 00:19 UTC
Readme bug (again):
The readme bug there is actually normal. By using that frame system, I am (a) making a fashion statement and (b) I think it looks cool because it doesn't crowd up the page with scrollbars.
Depending on how many people like this arrangement I may or may not take out the activex control. I still think it looks cool... :p
-dandaman32
PS here's a readme update (adds a "tips" section). Once again only for firefox. This update requires XPUI version 1.02 with the patching system, so if you don't have it, get it. This is how I intend to distribute all patches from now on except, of course, for the occasional complete system release.
dandaman32
26th January 2005 19:55 UTC
Yes, I got the image. I've never used iframes before, so if you could give me an example that would be great.
The only Firefox plugin I have is Flash, and the page looks normal to me, so I don't see what the problem is. Here is a screenshot of the readme in my Firefox.
-dandaman32
Comperio
27th January 2005 00:46 UTC
dandaman32, looking at your screeshot and the one from Afrow, both appear to be the same. But, after looking closer, I can see that the font type (and possibly the size) are different. The window sizes also appear to be different. So if I were to guess, I'd say that is likely where the problem is.
(As a side note, I have to say that I think the boring "TEXT.HTM" file is much easier to read than the README file. And, when you think about, the main purpose of the readme doc is to find out how to use the interface--it's not supposed to look pretty!)
dandaman32
29th January 2005 15:25 UTC
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
SuperPat
14th February 2005 13:54 UTC
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...
Afrow UK
14th February 2005 14:14 UTC
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 :D
-Stu
SuperPat
14th February 2005 14:32 UTC
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.
dandaman32
15th February 2005 21:05 UTC
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. :cry:
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
dandaman32
19th February 2005 17:46 UTC
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
dandaman32
21st February 2005 20:37 UTC
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
DrO
22nd February 2005 14:58 UTC
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
dandaman32
24th February 2005 01:16 UTC
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
dandaman32
26th February 2005 17:09 UTC
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
- NSIS Discussion
- ExperienceUI for NSIS
Archive: ExperienceUI for NSIS
dandaman32
8th March 2005 22:06 UTC
I have just created a website using two awesome hosts. My main page is http://dandaman32.95mb.com
and the download link is here at FreeWebTown
Thanks for hosting all this time, Afrow UK! Your help is greatly appreciated!
-dandaman32
dandaman32
22nd March 2005 01:44 UTC
New version: 1.05
I have finished work on version 1.05:
Now includes Start Menu and Abort pages, and includes various script bugfixes. Download here.
-dandaman32
dandaman32
2nd April 2005 19:02 UTC
Version 1.06 Sneak Peek
The next release is almost done. I have written a Finish page with reboot, run, and docs support, and the XPUI.nsh file will now be split into several different components. This will allow easier modification to the system, and it makes the whole thing more organized. This will also allow you to add your own macros, etc to the XPUI using the Components\Contrib folder. An example of both features can be found in the attached file.
-dandaman32
CuteBird_HL
2nd April 2005 22:56 UTC
its very beautiful,thank you dandaman32.
CuteBird_HL
5th April 2005 23:52 UTC
Re: New version: 1.05
Originally posted by dandaman32
I have finished work on version 1.05:
Now includes Start Menu and Abort pages, and includes various script bugfixes. Download here.
-dandaman32
I found a problem about v1.05,if you did't select create shoutcut.
dandaman32
7th April 2005 20:09 UTC
Thanks. Will be fixed in the next release.
-dandaman32
dandaman32
15th April 2005 22:54 UTC
I have asked the webmaster to (finally) rename this thread to "ExperienceUI for NSIS".
-dandaman32
kichik
15th April 2005 22:55 UTC
Why ask the webmaster when you can ask the moderator?
Title changed.
DrO
15th April 2005 22:55 UTC
you could have asked any moderator to do that for you ;)
-daz
Anders
16th April 2005 03:20 UTC
I have not tried it in a while, are files still not deleted in the temp and plugin folders?
dandaman32
18th April 2005 01:37 UTC
Originally posted by KiCHiK
Why ask the webmaster when you can ask the moderator?
Thanks. Still new to winamp forums. :o
As of version 1.05, a few changes to the GUI De-init process include automatic temp file removal. Skinners still need to write their own temp file delete macros, though.
-dandaman32
dandaman32
27th April 2005 16:57 UTC
Here's version 1.06! :D
http://www.freewebtown.com/dandaman3...1.06/Setup.exe
-dandaman32
Dick4
29th April 2005 23:03 UTC
awesome...I like this UI...thanks Dan!
saivert
3rd May 2005 08:33 UTC
Rename Setup.exe to ExperienceUISetup.exe please!!!!! This is not CD-ROM software.
And I hate it. InstallShield??? What the heck... Wasn't NSIS made to be a fresh seed in the installers garden?
Anyway: Hope you can fix the start-up problems with the installer, and writing a plugin to playback MIDI files instead of using a HTML Application (.HTA) for it.
And why does the installer start minimized, and why does it minimize all other applications?
dandaman32
20th May 2005 01:58 UTC
Version 1.07 is out, with mostly bugfixes
Download it: http://www.freewebtown.com/dandaman3...1.07/Setup.exe
-dandaman32
MichaelFlya
20th May 2005 02:29 UTC
Wow Nice.. Any thoughts on Integrating it as an Option for
zip2exe.exe. I Haven't Found the need to Use zip2exe.exe
yet but Just seems like it would be Nice as Part of it.. heh...
-MichaelFlya-
dandaman32
20th May 2005 02:34 UTC
Sounds like a good idea, however, I know very little C (basic syntax, comments, nothing more) and that's it. Probably Kichik can do it if you ask him
-dandaman32
deguix
20th May 2005 04:09 UTC
You could create a Zip2Exe with NSIS, but it's a lot better be working on Experience UI.
I like your UI, but it has some problems:
- The installer window can't center automatically on my screen (800x600). When I drag it to another position and I click on one of the buttons on the bottom right corner, it seems that the window comes back to the original position.
- After the first time the background image is drawn (outside the installer window), and after the above problem happens, the background image is not redrawn right and the old window's image is still there, until I redraw manually moving the installer window over it.
- More redrawing problems: when I drag the installer window outside the screen and put back, the text from static controls (labels) disappear.
- Is the tray icon supposed to disappear after the installer is loaded? It doesn't appear to be loading. Also, maybe because of this I can't left-click the Windows start button.
- I think you could use nsExec to run the temporary bat script.
I need to restart my computer to see if all of these are true, which I can't right now.
WinXP Home Ed. SP2
NSIS 2.06 latest dev. snap.
deguix
20th May 2005 11:47 UTC
Yep, confirmed, except for:
Also, maybe because of this I can't left-click the Windows start button.
NotifyIcon really has problems with WinXP. It lacks the handling of some newer notification icon messages and notifications.
saivert
20th May 2005 13:35 UTC
Still something...
WIndows XP introduced a feature for programmers that used the Notification Tray icon API that allows one to hide and show the icon. Previously people deleted the icon and readded it when "showing" and "hiding" which meant the icon would appear at a different place next time it was "shown". And you can also check for the validity of the icon under WinXP. In WInXp such icons also has a GUID where you assign a unique ID (generated by yourself). The GUID feature is mostly used by the "hide unused icons" feature.
And I still have to say this one more time: Why do people want their installers to look that fancy. I though people actually didn't even like an installer except if it was as invisible as possible.
I personally have never likes InstallShield. It loads slow and it displays these huge screens that are supposed to "shock you and amaze you so much that you just have to see it through and use the application that it installs on your in their mind super-computer" but fails.
Dick4
20th May 2005 17:04 UTC
The first thing a client sees of your product is the installer and you want that to be functional but also impressive. I myself would be satisfied if all my installers were just self extracting zip files...but my clients are impressed by pretty colors and buttons...nothing cartoony, but "modern" looking. ModernUI does this to a certain extent but this really makes it on par with the rest of the industry.
I've actually still got one installer left that I use InnoSetup for because it looks more like Installshield and IMO looks better than ModernUI.
deguix
20th May 2005 20:20 UTC
And I still have to say this one more time: Why do people want their installers to look that fancy. I though people actually didn't even like an installer except if it was as invisible as possible.
I personally have never likes InstallShield. It loads slow and it displays these huge screens that are supposed to "shock you and amaze you so much that you just have to see it through and use the application that it installs on your in their mind super-computer" but fails.
Yep. That's why I also don't like InstallShield, for these things and for packing my registry and harddisk with hidden stuff. The greatest headache is when a program you installed can't be uninstalled because there is a problem with the installation, and so you would need to uninstall it by hand.
The first thing a client sees of your product is the installer and you want that to be functional but also impressive.
That's because they like installers that entretain them until they reach to the product (because they want to use the product as quickly as possible). I would love to have a great looking installer, but not occupying most or all of my screen, for example.
saivert
21st May 2005 01:54 UTC
More 2 cents or maybe a quarter.
And what is the point in making such a huge "hack" (excuse me for calling it that) for NSIS, when most if not all is based on slowly executing code (NSIS compiled code is custom bytecode parsed by a run-time bytecode executer routine). Not that NSIS code is slow all the time but when used in a way such as in ExperienceUI it will be slow.
This just bloats the installer even more. If you want InstallShield then use InstallShield. Don't settle for the next best (excuse me Mr. NSIS but I say this to state my point).
I ofcourse love NSIS and even though InnoSetup comes with source (I downloaded that too of course) I only use NSIS because of it's powerful scripting language and the way you can exploit it to make small applications and not only installers.
Dick4
21st May 2005 02:05 UTC
heh...its funny because I make small applications out of NSIS as well...the functionality of its scripting language is great. I can make a compliled EXE that does what I would have to write a vbscript or similiar to do...
dandaman32
21st May 2005 19:43 UTC
Still looking for a skinning plugin... I think it was DrO that said he would make one but that has not happened. If anyone else wants to make on that would be great.
"The installer window can't center automatically on my screen (800x600). When I drag it to another position and I click on one of the buttons on the bottom right corner, it seems that the window comes back to the original position." -deguix
Will make the installer not change position for 800x600 and lower in the next release.
"After the first time the background image is drawn (outside the installer window), and after the above problem happens, the background image is not redrawn right and the old window's image is still there, until I redraw manually moving the installer window over it." -deguix
This is probably a LockWindow bug. That code was always a little unstable, but worked fine for me. You can disable it by defining XPUI_NOLOCK.
"when I drag the installer window outside the screen and put back, the text from static controls (labels) disappear." -deguix
I noticed that too. Bringing up the start menu over it seems to make it normal again. It does this because of the overlap that is needed for the controls.
"Is the tray icon supposed to disappear after the installer is loaded? It doesn't appear to be loading. Also, maybe because of this I can't left-click the Windows start button." -deguix
NotifyIcon has quite a few bugs. For now use the /SafeMode switch, but eventually I can remove it completely. The icon is supposed to stay there after the installer starts, so it can minimize the setup to the tray. It also gives file copy status in a percentage.
I also cannot use nsExec for the bat script, because it waits for it to finish. That is very slow on my machine, even though it is 1.8GHz.
If you don't want to wait for a new release, you may be able to fix these yourself, since the setup script has been improved to compile inside the ExperienceUI installation folder. All of these bugs *except* the drag problem should be fixed in 1.08.
Also is the updater working properly? I have only been able to test it from my machine.
Still looking for language files!
Also would like a
small MIDI plugin...
-dandaman32
dandaman32 <at> users <dot> sourceforge <dot> net
playwin2
23rd May 2005 00:11 UTC
If you got Wheel Mouse then scrolling(I mean using wheel) in the Readme and Lic. box is a problem, they just disappeared in my system.
saivert
23rd May 2005 09:18 UTC
Skinning for NSIS
I have written a plug-in that allows one to use Winamp skins to skin the NSIS dialogs. It uses the code from wa_dlg.h and my own code for the skinning of the frame (which was hidden in the Winamp core, but I think I replicated the code very good).
I yet have to upload it (it's on my home computer somewhere).
But I will post here when I have done so.
RobGrant
23rd May 2005 13:00 UTC
Blimey guys if you don't want to use an installer that looks like this then just don't use it, you've got options. Why complain about it on the thread where it's gradually being made or, indeed, why comment negatively at all?
Well done dandaman, nice work. Looks very pro and will make managers happy :)
DrO
23rd May 2005 13:20 UTC
Originally posted by RobGrant
Blimey guys if you don't want to use an installer that looks like this then just don't use it, you've got options.
unfortunately that's the standard of a large number of internet users who rather put down something, moan and bitch about things rather than help and sort things out (which is more beneficial).
and as Rob says, it's good to replicate the interface and style of other installers since it shows how good NSIS is
-daz
dandaman32
23rd May 2005 18:08 UTC
"I have written a plug-in that allows one to use Winamp skins to skin the NSIS dialogs." -saivert
Thanks for writing this, saivert. Though it sounds good, it is probably a better idea to allow using just plain bitmaps instead of a winamp skin.
-dandaman32
vbgunz
24th May 2005 04:13 UTC
I agree with RobGrant & DrO. I personally don't use ExperienceUI for NSIS but admire the fact an option is being made available. What would life be without options?
Although I do not use this ExperienceUI I have been keeping tabs on it. Anyhow, keep up the good work dandaman32!
deguix
12th June 2005 13:01 UTC
There are more problems with redrawing:
- More redrawing problems: when I drag the installer window outside the screen and put back, the text from static controls (labels) disappear.
This only happens if its a custom page from the skin.
- When uninstalling ExperienceUI, if I just click next, the header color doesn't get redrawn. Also, when click back to return to the first uninstaller page, the image also doesn't get redrawn. This stays there for the rest of the uninstallation process. This only happens if you run the uninstaller from the setup program.
- The warning "This uninstaller removes all..." cuts the last word "continue?". It doesn't have enough space vertically.
- Is the tray icon supposed to disappear after the installer is loaded? It doesn't appear to be loading.
It reloads after a certain time has passed.
Other types of problems:
- Do you think it's good deal to install ExperienceUI in two locations, one on NSIS dir, another on Contrib/ExperienceUI? I don't think the copying is necessary.
- Can't you make an unified header file for the installer of Experience UI so that I can, for example, only need to change the version in just 1 place?
- There are some problems also in compiling the scripts of your installer. For example, the line "ChangeUI all tinyui.exe" (number 7) gives this error: "Can't find IDC_LIST1 (1016) in the custom UI!".
- There is also a problem with the StartMenu page on the ExperienceUI installer. If I click on a region on the listbox that don't have items, it gives the folder name "566878", exactly as the define XPUI_LICENSEBKCOLOR value.
The updater is ok, I just need now an updated version of the ExperienceUI to test it more...
dandaman32
1st July 2005 23:35 UTC
There is now an official ExperienceUI website:
http://experienceui.95mb.com
News, updates, inside info and more!
-dandaman32
Yathosho
2nd July 2005 00:26 UTC
should place some screenshots on that website too
Joost Verburg
2nd July 2005 19:32 UTC
Did you contact the company behind InstallShield to make sure that what you are doing is legal? I think it is likely that this design is copyrighted.
Anders
2nd July 2005 19:39 UTC
Originally posted by Joost Verburg
Did you contact the company behind InstallShield to make sure that what you are doing is legal? I think it is likely that this design is copyrighted.
I guess I could ask the same question about the MUI. msi, inno setup and the modern ui look pretty much the same
Joost Verburg
2nd July 2005 19:52 UTC
Originally posted by Anders
I guess I could ask the same question about the MUI. msi, inno setup and the modern ui look pretty much the same
That's because the Modern UI is based on the standard Windows wizard style, just like these other installers. This is the design Microsoft recommends, it can be used by any application.
The only reason I'm asking this question is because I don't want the author of this UI to get into troubles because of legal issues.
onad
2nd July 2005 22:32 UTC
Well, what about mobile phones then, they all look somtimes extreamly the same... :)))
Indeed the EXACT same grapics if taken from InstallShield is not allowed, e.g. the PC image on the first screen. But to create something that looks a lot like it can not be forbidden, really. NSIS Modern looks like an MS installer and is also allowed.
It is good to discuss it however.
Joost Verburg
3rd July 2005 12:15 UTC
The question wheather two designs are too similar is a difficult one. But it looks like exactly the same design is used, which I think cannot be legal unless permission is given.
The design of the Modern UI is indeed similar to MS installer, but that's because it uses the standard MS wizard design. MS allows everyone to use this style, because they want Windows application to have a uniform look.
ZmAn3
4th July 2005 12:48 UTC
i made some that are as close as i can get if you want them
http://www.emeraldcpu.com/nsisgfx/
- NSIS Discussion
- ExperienceUI for NSIS
Archive: ExperienceUI for NSIS
Joost Verburg
4th July 2005 14:27 UTC
I think it would be a good idea not to include a "InstallShield" skin at all.
dandaman32
5th July 2005 02:59 UTC
Love the graphics, ZmAn3. Could you post PSD or PNG? (to allow for transparency)
"Did you contact the company behind InstallShield to make sure that what you are doing is legal? I think it is likely that this design is copyrighted." -Joost Verburg
Does InstallShield have a left info panel?
Does InstallShield have a skin platform that changes the skin with one line of code?
Does InstallShield have a 100KB overhead?
Of course, the answer to all of those is
no. The ExperienceUI was created to make NSIS look
similar InstallShield, not to duplicate it. Besides, who would want NSIS to look exactly like InstallShield anyway? NSIS coupled with the ExperienceUI is provided as an
alternative to InstallShield.
Here is one example:
KDE (the K Desktop Environment; free;
http://www.kde.org) is a graphical environvent for Linux, just like Windows 95 is a graphical interface for DOS. KDE has a "widget style" called Redmond. The skin looks exactly like the Windows 95/98/ME/2000 visual style. Have the rascals of Redmond taken any legal action against the KDE project? Obviously not. And Microsoft almost certainly knows about KDE.
"should place some screenshots on that website too" -yathosho
Still working on it. Have been on vacation for the last week or two, so I have not worked on the ExperienceUI a lot. Also busy writing stuff for
Aha-Soft
-dandaman32
Joost Verburg
5th July 2005 12:33 UTC
Originally posted by dandaman32
[B]Does InstallShield have a left info panel?
Does InstallShield have a skin platform that changes the skin with one line of code?
Does InstallShield have a 100KB overhead?
It is not relevant whether it provides additional features or has technical differences. "Features" are not copyrighted, but graphics are. Whenever you're using any graphics designed by InstallShield, it is probably not legal.
That's why I think it's better to include only custom designed skins.
saivert
5th July 2005 13:31 UTC
Splash gfx
I created a nice splash graphic based on one of the images made by ZmAn3:
saivert
5th July 2005 13:32 UTC
Disregard Previous post
Sorry. Had to quote the filename when uploading. Here it is:
dandaman32
5th July 2005 16:29 UTC
The next release will replace the old graphics with ZmAn3's new ones. The Left Branding image is the only one that I am concerned about, because the other two images (header/bottom) are my own.
ZmAn3, if you wish you can send me a pm with your full name in it, otherwise just your screen name will be in the acknowledgments section. I still need your images in a PNG (Portable Network Graphics), TGA (Targa) or PSD (Photoshop) format in order to use them in a skin other than "Windows XP", as it looks like I will be unable to apply the transparency myself.
-dandaman32
dandaman32
5th July 2005 19:19 UTC
Patching system update available:
http://www.freewebtown.com/dandaman3...atchUpdate.exe
This update will be included in version 1.08.
Also: New update wizard (attached) - Required in order to update to ExperienceUI 1.08 automatically
-dandaman32
ZmAn3
5th July 2005 19:40 UTC
screen name is fine.
here you go
www.emeraldcpu.com/nsisgfx/nsisgfx.zip
dandaman32
9th July 2005 19:43 UTC
Love those pix, thanks ZmAn3!
-dandaman32
saivert
11th July 2005 05:41 UTC
What about making a NSIS for MSI platform. You code using NSIS language but end up with a fully-featured Windows Installer after compilation. Would only require rewriting the NSIS compiler to be a processor for NSIS in order to build the MSI database. And then create stub exe/dll files for the functionality in NSIS that is NOT present in Windows Installer service.
Joost Verburg
11th July 2005 12:15 UTC
It would of cource be a great feature to allow users to choose between the NSIS VM and NSIS-based MSI engine.
It is however not a simple thing, so unless someone wants to help the NSIS developers to add such a feature, I think other things (64-bit and Unicode support etc.) have priority.
dandaman32
11th July 2005 23:13 UTC
NSIS and MSI don't mix
originally posted by saivert
What about making a NSIS for MSI platform.
NSIS was made to combat the slow Windows Installer platform, not to embrace it! Why should NSIS use the MSI system when its own VM platform it faster and smaller? Also MSI is Windoze only (duh) while the NSIS VM can be easily ported to Linux.
originally posted by Joost Verburg
I think other things (64-bit and Unicode support etc.) have priority.
64-bit support would definitely be a good feature. I have not yet moved up to 64 bit, but many have.
Of course dual core CPUs have just hit the market big time, and a lot of gamers/speed lovers have already adopted it. By the time Longhorn hits the shelves, all mid-grade PCs will have at least 2 cores, so eventually dual core will be a must.
Still another nice feature would be Linux ports and such, as Linux (read: Linspire) is spreading like Firefox did.
-dandaman32
JasonFriday13
12th July 2005 04:44 UTC
About the systray bug: I have windows millenium edition and I have seen this problem with coolplayer coolplayer.sourceforge.net when it crashes and it disappears if you hover your mouse over it.
saivert
16th July 2005 20:05 UTC
@dandaman32:
Okay. I drop the thoughts about NSIS and MSI then!!!
But: Microsoft only stamps Windows XP Logo on software which is distributed using the Windows Installer system. So I guess logo certification isn't such a big deal for NSIS users??
How would you utilize dual processing power in NSIS? Put the workload of decompressing the files on one core and the installer logic on the other? Will it make installation that much faster?
@JasonFriday13:
When an spplication crashes the Taskbar isn't notified about it and thus can't remove any icons. When you interact with the taskbar notification icon for a no longer exisitin application the taskbar will know the application no longer exist as the window handle of the application is no longer valid.
onad
17th July 2005 00:29 UTC
If you need to adhere to some strange corporate standards and use MSI, there is a what to do and still sneakly use NSIS:
1) Create a minimal MSI script, brrr...
2)Create an MSI extention
http://codeproject.com/tips/msicustomaction.asp
3)
Wrap your finised NSIS .EXE in a resource in the DLL
Extract the resuorcedata and run NSIS, in the end delete te temp file and close MSI, done...
Boss happy since you use MSI, you happy since you still use NSIS
There are as always more ways, but this is a start for the persistent ones,.
Better to convince your boss, if you have one, MSI is not always handy...
saivert
17th July 2005 14:00 UTC
Sounds nice. I think I want to make such a MSI wrapper...
onad
18th July 2005 00:23 UTC
Ha saivert, you are realy a Major Dude, let's see who is first with the MSI crap ;) I have to make my DLL in Delphi since I'm not a C guy anymore since my Amiga time.
Dead_Overlord
18th July 2005 04:57 UTC
Broken Links
The download links in http://experienceui.95mb.com/contact.htm is all broken!
Help me download this nice UI, OK?
saivert
18th July 2005 23:52 UTC
MSI crap Compo
So we have a competition going? I did not expect that. OKay. Sounds fun.... I have MS VIsual Studio .NET 2003 with latest Platform SDK installed, so I consider this a head start. I have already downloaded the sample from CodeProject and compiled it successfully. All I need now is a way to get the binary data from the installer database, then write it out.
Is all parts of the MSI database compressed ?? I see some MSI installers just use CAB archive and someone made using "InstallShield for Windows Installer" can't be extracted at all using a standard CAB extractor.
Dead_Overlord
19th July 2005 15:25 UTC
Please Help-me
Hi!
Firt all the links in the page http://experienceui.95mb.com/ are broken and is unable to download ExperienceUI.
I have found a webpage (http://guerin45.free.fr/UltraModernUI/), this is the page of an UI named UltraModernUI, this UI is based on ExperienceUI, this page has working links and i have downloaded it, it have a lot of bugs, but is realy great!
What is the problem here... Where is the location to download the most recent release of this nice look UI?
Thanks to all developers, this is a great project!
Thanks to all NSIS Fans!
DrO
19th July 2005 18:47 UTC
http://www.freewebtown.com/dandaman3...1.07/Setup.exe is the direct link to 1.07 and the site works fine here. looks like you connection or something may be a bit flakey
-daz
Superpat
19th July 2005 19:08 UTC
Hello,
I am the developper of UltraModernUI, I have just release a new plugin for NSIS named skinned button which allows to skin the buttons. It's based on the wansis plgin of saivert
You will find on this French forum a topic relating to it with some screenshots.
The topic:
http://www.winampfr.com/forum/viewtopic.php?t=9312
The plugin:
http://guerin45.free.fr/UltraModernU...dButton1.0.exe
saivert
20th July 2005 15:29 UTC
Great! Finally my wansis plug-in comes to use elsewhere as well. Just use the source code all you want, but give credit where credit is due (and YES I see you did that).
Hopefully, this experienceUI thing will get popular soon. At least within certain corporations who think full-screen installers are golden.
rsegal
20th July 2005 16:58 UTC
Originally posted by onad
If you need to adhere to some strange corporate standards and use MSI, there is a what to do and still sneakly use NSIS:
1) Create a minimal MSI script, brrr...
2)Create an MSI extention
http://codeproject.com/tips/msicustomaction.asp
3)
Wrap your finised NSIS .EXE in a resource in the DLL
Extract the resuorcedata and run NSIS, in the end delete te temp file and close MSI, done...
Boss happy since you use MSI, you happy since you still use NSIS
There are as always more ways, but this is a start for the persistent ones,.
Better to convince your boss, if you have one, MSI is not always handy...
As well what you could do here is create your NSIS installer then create a MSI package containing that NSIS installer using WiX
http://sourceforge.net/projects/wix/
saivert
20th July 2005 22:46 UTC
Nice! I will try both WiX and the CustomAction DLL. And love to test the SkinnedButtons plug-in. Thank you so much!
ZmAn3
20th July 2005 22:55 UTC
super pats installer is not full screen i belive
plus you can change to his UI with one line of code which is nice.
DRO where is your skin plugin ??
DrO
20th July 2005 23:00 UTC
i've given up on the project and there's no point in finding the code when wansis has virtually the same effect as my initials builds did. also my efforts have to go elsewhere (since i don't have all the freetime like the young people/students around)
-daz
saivert
20th July 2005 23:06 UTC
@DrO: Hi DrO!! So you did work on a skinning plug-in for NSIS?? What plans did you have for yours?
-nxs
ddod
21st July 2005 22:19 UTC
1
Joost Verburg
25th July 2005 20:42 UTC
The UltraModernUI (http://guerin45.free.fr/UltraModernUI/) concept looks promising. Maybe you guys can work together on this project instead of creating similar things separately.
One thing I really like about the UltraModernUI is that it keeps the original MUI settings. I've learned from user feedback that compatibility is a very important thing (people using the NSIS 2 betas really didn't like the fact that they had to update scripts when the MUI setting system was still under development).
Now we have the standard of MUI settings, I think it would be a very good thing to keep these as a core for even more fancy UIs and add new ones whenever required (like the UMUI settings of the UltraModernUI).
I would also recommend the authors of ExperienceUI and UltraModernUI to work together on a set of custom designed skins. Using copyrighted artwork like those of InstallShield will be a problem when the NSIS developers may decide to include a UI in the NSIS package and could also get your end-users into trouble.
SuperPat
25th July 2005 23:41 UTC
Hello,
I am the developper of UltraModern UI.
I decided to launch the UltraModernUI project mainly because ExperienceUI did not take again the original macros and defines and because I think that it is easier to take again an already functional architecture rather than to rewrite all.
And also because I had had this idea, few years ago, and that at that time, my knowledge in NSIS was insufficient.
In this connection, I search somebody who could make an another skin near the installshield but different. Skins which we could share between our two projects.
Joost Verburg
26th July 2005 00:00 UTC
It is indeed a very good idea to keep using the same setting standards, that is in my opinion the most important thing when creating a new UI.
Maybe you can contact the author of ExperienceUI to see whether you can work on a single UI toghether. You are both doing something nearly identical so merging the projects would save a lot of time and effort.
saivert
26th July 2005 04:13 UTC
Yes, but ExperienceUI does not follow the same macro system that ModernUI uses. So UltraModern UI author should convince ExperienceUI author to rewrite ExperienceUI to use same macro as ModernUI. Everybody should follow the macro system that our almighty Joost Verburg designed. Do it and do it now!!
dandaman32
15th August 2005 23:02 UTC
ExperienceUI 1.08 is ready...[edit] and macro system is still the same.
Will rewrite macros/defines for 1.09 or 1.1, depending if I skip 1.09 or not, see below.
I am considering skipping 1.09 or making it a non-public beta of 1.1. If I do make 1.09 a non-public beta, e-mail me, I will accept first four testers. When the first four testers have been accepted, I will announce on this thread.
Anyway, grab 1.08 here:
http://experienceui.95mb.com/downloads.htm
-dandaman32
JasonFriday13
16th August 2005 01:11 UTC
Yes, I agree. I have used the modern UI for my interface (InstallSpider UI for NSIS) and slightly changed the internal workings so that my UI operates with different bitmaps. I didn't need the header bitmap or the wizard bitmap, this has been replaced as branding image. The interface also looks different.
DrO
16th August 2005 01:20 UTC
heh, first time i've looked at this for a while and just noticed you seem to be using my helpbutton plugin :) and despite the debate over the ui previously in this thread the overall working of the installer is pretty slick as things go i think (i'm pretty amazed in that it's all done by nsis and that's even from looking at the nsis and code for this one :up: )
-daz
dandaman32
26th August 2005 01:02 UTC
Website change:
http://xpui.sourceforge.net (seriously!) since 95mb sucks anyway...
Site features development roadmap now, and 1.09 will not exist, 1.1 milestone 1 will be a nonpublic alpha.
-dandaman32
dandaman32
26th August 2005 02:30 UTC
just a teaser here...
Here's a demo setup with running the (for now) unreleased Bryce M1 with wansis. This shows the ExperienceUI's ability to remove all of its internal skinning support to allow 3rd-party skinning plugins. The script I used is included, just for those of you that get to test Bryce M1.
Speaking of which, the first four e-mails I get requesting permission to beta-test will get an activation key and an encryption key to unlock the new ExperienceUI alpha.
This little puppy uses WAnsis and ZmAn3's Forum theme. I also did some of my own images for the bottom panels and such.
Sorry I couldn't attach this in a ZIP, only 7z compressed it <100KB, so you'll need 7-zip.
Hope this sample keeps y'all busy!
-dandaman32
dandaman32
28th August 2005 01:33 UTC
Codename "Bryce" M1 is available! Because 1.1M1 is non-public, you will need to e-mail me. The first four people I get emails from will receive activation keys, so anyone can help test the ExperienceUI version 1.1.
Please note that if you don't get a reply in 3 days, you're out. I will post to the forum here as soon as the fourth tester is enlisted.
The WAnsis teaser installer I posted yesterday is included with this distro, and it has several updates. Also there is some primitive documentation, to get you started. If you are not too experienced with the XPUI, I recommend that you back up the text.htm file before installing this.
Once you have received a confirmation e-mail, you may use this link to download M1.
For security (which I normally stink at) the installer will require an activation key and a decryption key. The activation key is time sensitive (it works for 2 days) and the encryption key (made with DcryptDll) is used to unlock XPUI.nsh and MUIConvert.nsh.
-Dan
- NSIS Discussion
- ExperienceUI for NSIS
Archive: ExperienceUI for NSIS
dandaman32
1st September 2005 16:52 UTC
Jenner Modesto has just taken the leap of faith and sent a Brazilian Portuguese translation of the ExperienceUI to me. Anyone else available for translation? Looking for all NSIS-supported languages, mainly Spanish, French, German, Simp. and Trad. Chinese, Japanese. If anyone is willing to do this or if anyone knows of someone who can, please contact me.
-dandaman32
JasonFriday13
2nd September 2005 22:12 UTC
I have just recently downloaded the experience ui teaser. I tried running the program on my windows me machine and I got a fatal error saying 'WAnsis has encountered an error in wansis.dll and will now close.' Any ideas?
dandaman32
3rd September 2005 05:39 UTC
You'll need to contact saivert, he wrote wansis. In the mean time I will look for a problem in the script (possible /NOUNLOAD problem?). Did this error occur before or after the main program ran?
EDIT: This could be a Windows Mucky Edition bug...get Win2k or XP!
-dandaman32
DrO
3rd September 2005 09:44 UTC
it causes issues as well on XP/2K systems as well. had someone a few days how basiacally couldn't use that plugin as soon as the title contained mutliple words which is pretty lame.
-daz
dandaman32
4th September 2005 05:26 UTC
If problems continue I will have the ExperienceUI issue a warning when a setup is compiled with WAnsis.
-dandaman32
JasonFriday13
5th September 2005 23:11 UTC
It comes up with the main window (showing the titlebar), then it gives the error. I have had the wansis plugin on normal installers (tests) and it works just fine.
dandaman32
7th September 2005 20:28 UTC
Still three beta testing positions open, any volunteers? I can't release M2 until 2 weeks after the fourth beta testing position is filled.
-dandaman32
dandaman32
5th October 2005 06:35 UTC
Finally, something better than this thread!
There is now an official ExperienceUI forum:
http://xpui.sourceforge.net/forum/
-dandaman32
dandaman32
18th October 2005 01:54 UTC
If some of you have been having problems signing up for the new ExperienceUI forums, that problem has been fixed now. Looks like an STMP server problem.
-dandaman32
dandaman32
22nd October 2005 00:49 UTC
Bryce M3 is available:
http://xpui.sourceforge.net/index.php?sec=downloads
-dandaman32
dandaman32
8th November 2005 18:23 UTC
The ExperienceUI has grown into quite a large and complex project, and I believe that it has outgrown this forum thread.
The official ExperienceUI forum can be found at http://xpui.sourceforge.net/forum/.
If you have any ExperienceUI-related questions, comments, or raves, please use the forum or e-mail me.
You can always download the ExperienceUI at http://xpui.sourceforge.net/index.php?sec=downloads
And of course, if you've never heard of the ExperienceUI until 5 minutes ago (and I know that most NSIS stuff gets discovered in these forums) you can visit the ExperienceUI website to learn more about skinning the entire installer window.
Moderator, please close this thread.
-dandaman32
closed on user request - DrO