Installer To Do

From World Wind Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 23:19, 31 March 2005 (edit)
Dpatton (Talk | contribs)
(Uninstaller)
← Previous diff
Revision as of 23:20, 31 March 2005 (edit) (undo)
Dpatton (Talk | contribs)
(Uninstaller)
Next diff →
Line 24: Line 24:
*Doesn't uninstall World Wind dings font *Doesn't uninstall World Wind dings font
*Doesn't delete C:\Documents and Settings\<USER>\Application Data\NASA directory and subdirectory and XML files *Doesn't delete C:\Documents and Settings\<USER>\Application Data\NASA directory and subdirectory and XML files
-*Even when "retain cache" isn't selected, doesn't delete+*Even when "retain cache" isn't selected, doesn't delete the 'parent' program installation directory(e.g. C:\Program Files\NASA)
-the 'parent' program installation directory(e.g. C:\Program Files\NASA)+
==On Hold== ==On Hold==

Revision as of 23:20, 31 March 2005

Contents

Open

Installer

  • "Would you like to run NASA World Wind?" dialog at end - launch program after install (requires another language string)
  • modify the first requirement string so that it contains another string with the requirement word. This way languages who may have to rearrange the sentence can. (language changes)
  • "notepad" for releasenotes still seems to get started in background, rather than in foreground -- implement release notes into a exit license page - Cha Ching - http://forums.winamp.com/showthread.php?s=&threadid=136925
  • Button on NOSA page to "print license"
  • World Wind Lite: dpatton: I'd suggest that the "exe andf associated files" be one install, Blue Marbe be another, each add-on their own install, etc. That approach allows for two things - (1) smaller downloads, so less issues for people who get corrupt downloads, and (2) makes it much easier to "just update what you need"
  • Blue Marble JPEG
17:42 <+Llynix> I have BM jpeg here
17:42 <+Llynix> that will save about 10 megs in the installer from what it looks like..
  • Non-solid LZMA compression to fix %TEMP% space problems? [1] Jessi tested and found that World_Wind_1.3_Full.exe compressed non-solid LZMA is 181,585 KB compared with World_Wind_1.3_Full.exe compressed solid, which is 174,808 KB. Penalty of ~ 7 MB.
  • If you download using IE and small cache, and run from the web page, the install extracts then displays an error? (can't reproduce with IE6, 50MB cache)
  • "Installing Managed DirectX assemblies" dialog shouldn't cause a beep when it comes up -- Not on my machine *grin* User:Llynix
  • gillesk's installer polish issues:

after installing managed DirectX, the installer hides in the background - some users do not find it in their (hidden) taskbar ... (Can anyone confirm, it's an ExecWait there and I don't really think there is anything I can do about it.)

Uninstaller

Observed using WinXP, 1.3beta, 1.3.1alpha4 (dpatton)

  • Doesn't uninstall World Wind dings font
  • Doesn't delete C:\Documents and Settings\<USER>\Application Data\NASA directory and subdirectory and XML files
  • Even when "retain cache" isn't selected, doesn't delete the 'parent' program installation directory(e.g. C:\Program Files\NASA)

On Hold

  • Add logfile capability to installer and turn it on by default ([2], also [3])
ok, I do believe there is a command line switch a user can use to flag an logfile. Also the next installer will be patched to debug the wierd writefile bug we have, so hopefully a fix by next version. -- I know me and Jessi discussed that it didn't look like we needed advanced logging for any of our installer issues.
  • "You need DirectX" dialog redirects you to main DirectX page--would be better to direct to a link on our web page that redirects to the current DirectX installer, so less clicks. World Wind main download page should have links to DirectX and .NET download pages, so user can download and install those before installing World Wind, for better user experience. On download page, there should be a warning: installing DirectX and .net might force you to reboot your machine.
  • The directX link links to the latest version, it's the directx main download page. There is no .NET main download page as I could see, however if we could find one that would be even better then a NASA redirect. -- llynix
  • Pretty screenshots in background for installer: [4]
13:38:32 <+Llynix> jessi-nlt: http://cvs.sourceforge.net/viewcvs.py/*checkout*/nsis/NSIS/Contrib/BgImage/BgImage.txt?rev=HEAD&content-type=text/plain
13:38:49 <+Llynix> I do believe that is what we need for setting pretty backgrounds while installing
13:40:42 < [-bull-]> randy can mke a nice background :)
13:41:17 < [-bull-]> maybe from his hawii trip phoos ;)
13:41:50 < [-bull-]> photos
13:42:21 <+Llynix> I'm not even sure if that above is quite the way to do it
13:42:26 <+Llynix> that's part of it.
13:42:35 <+Llynix> but I think we'll ahve to make seperate pages for each screen
13:42:44 <+Llynix> then invoke them at various times during the install
-- Honestly I think we need to look into branding and skinning the installer (see above) first, there is a lot we can do there to make things very sharp looking. User:Llynix

Fixed

  • The .NET dialog doesn't contain a message, only Yes/No/Cancel buttons. strCpy/localization problem http://forums.winamp.com/showthread.php?s=&threadid=208026 (LL Fixed)
  • When the installer puts up a dialog "Installing Managed DX Assemblies" and you click ok, there's nothing onscreen but alpha6 installer CPU usage goes to 60-90%. After 20 seconds MDX installer pops up. During this time there should be an indication of what's going on.
  • We should try to encourage people to install .net and directx before they run the installer... it takes forever to initialize the installer, and making them do it more than once is bad. If we could move the .NET and DirectX checks to before NSIS unpacks data, that would be best. Right now it unpacks all the data then does the checks.
13:45:11 < Llynix> reserve file is what we need for speeding up the installer
  • When installer launches MDX MSI on systems that already have it, user is prompted to uninstall MDX. This shouldn't happen. :)
  • Leaves registry key HKEY_CURRENT_USER\Software\NASA*
  • Add debugging code and defines
Personal tools