diff -r 000000000000 -r d5ce4c64ef88 Docs/ExperienceUI/pages/patch.htm --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Docs/ExperienceUI/pages/patch.htm Tue Oct 16 00:07:41 2007 -0400 @@ -0,0 +1,108 @@ + + + ExperienceUI Documentation Content Frame + + + + + + + + + + + + + + + + + + + +
+ +

The ExperienceUI's Patching System

+ +

+ Like all computer programs, the ExperienceUI has its bugs. Since version 1.02, however, the ExperienceUI has included a patching + system that can update any file that is related to the ExperienceUI or any NSIS component. The patch files are simply ZIP archives + with a special file, CONTENT.DAT, that tells where everything goes. This method of distributing updates allows for very small files; + files that do not require a setup program, just a shell extension in the Registry. The patching system also allows installation of + new components, such as extra features or skins. There is even a separate format made just for skins!
+
+ Installing a patch or skin is very easy. All you have to do is click on the file in Windows Explorer, and the installer handles the rest. + You can also write your own patches or skins. See the next section for more information. +

+ + +

Writing patch files

+ +

+ Writing an ExperienceUI patch or skin is very simple. If you have WinZip® or even Windows 98/ME/XP's integrated ZIP features and a + basic text editor, you have the tools required to build a patch or skin for the ExperienceUI. Here's how:
+
+

    +
  1. Gather up your files.
    +
    + Make a new ZIP file, and put all of the files you want to install into the archive's root directory.

  2. +
  3. Create a CONTENT.DAT information file.
    +
    + Create a new text file, call it CONTENT.DAT, and open it in Notepad, WordPad, emacs, or any other text editor.

  4. +
  5. List your patch's files.
    +
    + Type [EUI-Patch] or [EUI-Skin] (including the brackets) at the top of your file. Hit enter.

    + Now type NumFiles=# and replace # with the number of files in your patch, not including CONTENT.DAT.

    + Make a few more new lines, and then type File1=<filename> and replace <filename> with the first file + in your patch/skin. Hit Enter.

    + Type in File1 Path=MyPath for the folder to extract the file to. If you are extracting the file to the ExperienceUI's + installation root directory, create this field, but leave it blank. Hit Enter one more time.
    + If you're writing a patch, type File1 Desc=My Description String and replace My Description String with a description + of the file. This key does not apply to skins.

    + Now, add one more File1/File1 Path/File1 Desc section to the install script file (aka CONTENT.DAT) for + each file in your patch/skin, each time replacing the 1 with a number one higher than the previous file entry.
    +
    + When you're done, the file should look somewhat like this:
    +
    + + [EUI-Patch]
    + NumFiles=3
    +
    + File1=XPUI.NSH
    + File1 Path=
    + File1 Desc=ExperienceUI main script
    +
    + File2=English.NSH
    + File2 Path=Language Files
    + File2 Desc=English Language string table
    +
    + File3=Plus.bmp
    + File3 Path=Readme\Images
    + File3 Desc=Documentation section expand button, mouse out

    +
  6. + +
  7. Add the CONTENT.DAT file to your ZIP archive.
    +
    + This next step should be a little easier. Fire up your zip utility, and + add the CONTENT.DAT file you just created to the ZIP file.

  8. + +
  9. Rename the file.
    +
    + Open up Command Prompt, usually done by going to Start > Run, typing CMD, and pressing Enter, and change to the + directory where your ZIP file is. Type in the command REN <file>.zip + <file>.eup for a patch or REN <file>.zip <file>.eus for a skin.
    +
    + That's it! To test your skin/patch, just double-click it. After testing it, you'll be ready to distribute it over + the Web. +
+

+ +
+ + + +
+ + + +