yeah, docs on this is sparce at the moment (to say the least).
You can register your fonts via a couple of methods:
1) via the .xpi. Just have the .xpi file's install.js check for the appropriate platform that it is running under, then do the windows registration accordingly. Here are some links to look at:
http://lxr.mozilla.org/seamonkey/source/xpinstall/packager/windows/browser.jst#329 (example on working with windows registry via install.js script)
http://lxr.mozilla.org/seamonkey/source/xpinstall/packager/common/share.t#59 (contains example on how to detect platform via .js script)
http://lxr.mozilla.org/seamonkey/source/xpinstall/src/nsInstall.cpp#273 (contains info on what can return when querrying for platorms via .js script)
2) via config.ini. Given the 'Windows Registry' section that you found, here are the possible OS= key values. You can also OR them together (Win95|Win98):
Win95 debute - original release of win95 only
Win95 - any win95
Win98 - any win98
NT3 - nt3.x
NT4 - nt 4.x
NT50 - win2k
NT51 - winXP
NT5 - any os >= win2k
How are you trying to determine the previous installation path to your application?
Rob Brandt wrote:
Thanks, Sean. Actually, I've made a ton of progress on this, and have gotten the fonts installation working well by making the .xpi for the fonts, then copying them into the PERSONAL_FONTS folder. I've only tested it on my w98 machine, but think it will work on NT/2000/XP too since it seems to know about the fonts folder.What would be really valueble to me in other issues is complete documentation on what goes in to the config.ini file. For example, in the config.ini file for Netscape 7.01 there is a section: [Component Navigator-Windows Registry0] ... ... OS=NT5 To me, that last item suggests that component will only be run on WindowsXP (NT5?). Yet I can find no documentation anywhere that says what the OS= item does, or what the valid values for it are. I can only assume that there other items undocumented that I would find useful. I did try and create a component with that item to see if it would install on w98, and it does, so I'm not "getting it". Having an item that would only run on certain platforms would make my life a heck of a lot easier. I have an application that runs on NT/2000/XP, w95/98/me, OS8-9, OSX, (and w3.1 and 68k macs, although I'm doubting I'll have many requests for that platform, and possibly in the future linux). You can see why I hope that XPInstall would be an ideal candidate for an installer. Another issue I struggled with last night before sleep overtook me was determining the previously defined (in the registry) installation path to my application. Seems like it should work. Doesn't. Thanks for your response. Rob Quoting Sean Su <[EMAIL PROTECTED]>:Have you already created a .xpi file for the fonts? The native windows installer does not actually do the installation of files, but rather it gathers information from the user and system, then passes the .xpi files needing to be installed to the xpinstall engine. I'm not sure how much you know about how the entire process works. Let me know if you need more help on this. Rob Brandt wrote:OK, I've dived in to making my own installer using the stubs. I've focused on the windows version since it's much better commented than the Mac version. I have a mostly working installer. There's a couple of things I don't see how to do. It would be nice if I could see and example of how this works. 1) Install fonts in windows. I see from the config.ini that is used in the Netscape installer that the stub is aware of where the fonts folder is, in PERSONAL_FONTS. But how to get them installed, registered, efficiently? 2) Windows versions: My app has some minor differences between Windows 95/98/Me and NT/200/XP. It would be really nice if config.ini could sense which version it was on, and select the correct package. TIA Rob
