Personally I'd prefer to see any effort that goes into an installer go into:
1) Calendar - I'd like to see this working. 2) Further speed and reduced memory enhancements. 3) Further work on some of the quirks in email and newsgroups. 4) Moz actively being built on OpenWatcom (since it appears to be the only C compiler with a future). Adding an installer at this point makes me a little nervous anyway. I've been trying to figure out how to move a profile directory and can find no good way to do it which is extrememly annoying so when I hear the words installer and dependancies I start having visions of entries going into the .ini files or other cfg files that lock program and/or data location which is not what I want...I want to be able to move the Moz program directory and the profile directory whenever I want with minimal problems. If I want to move the profile directory to another server, I should be able to. WarpIN is still very actively being worked on and I'll bet that the author would like to see a list of the issues that cause the below statements. Regards, Nick Michael Kaply wrote: >We looked at WarpIn and honestly it just didn't do the type of things we >needed to do for the Mozilla installer. > >Even the most basic of dependencies didn't work, and the quality (polish) >wasn't there. > >We'd prefer to use the Mozilla look and feel so we are consistent with the >other platforms. > >Mike > >"J. Robinson" wrote: > > > >>Michael Kaply wrote: >> >> >> >>>1. XPINSTALL wizard (mozilla/xpinstall/wizard/os2) >>> >>>This is the code that produces a pretty install. We have some code >>>there, but it was an attempt to port the Windows code and never really >>>came to anything. >>> >>> >>If I recall correctly at one time the suggestion had come up to try >>using WarpIn as the Mozilla installer on OS/2. >> >>I know (at least from the documentation) that WarpIn can create a few >>different types of installs: >>1) Pure WarpIn package (requires a pre-installed version of WarpIn to >>install) >>2) A simple stub .exe install (it will search the user's system for a >>pre-existing WarpIn and automagically use that for installing, so the >>.wpi extension doesn't confuse end-users). >>3) A minimal stub .exe install (contains a minimal version of WarpIn so >>can do the whole self-extracting install, but the user needs a copy of >>WarpIn itself if they're like to do a "clean un-install"). >>4) A full .exe install (This packages an entire version of WarpIn with >>your archive, so that the .exe will install both simultaneously). >> >>Was the concept of using WarpIn shelved, or was it just due to developer >>time? This could certainly be a project I'd be interested in looking at >>it it hasn't been written off. >> >>Jeff >> >>-- >>---------------- >>Whatza JamochaMUD? >>http://jamochamud.anecho.mb.ca >> >>Or other stuff: http://www.anecho.mb.ca/~jeffnik >> ----------------------------------------------------------- >> >> >> >> > > >
