Thoughts on installation of IR

e34m5 · Post by **e34m5** » Wed Jun 09, 2004 9:09 am

The answer is yes.

All we were trying to do is give the new user some guidance. For everyone else when openning the zip file you can select what and where to unzip files to.

Also as Nils mentioned we thought it might help to trouble shoot if files are in an expected place.

But...no big deal..I put the file back to the way it was

Mark Pierson · Post by **Mark Pierson** » Wed Jun 09, 2004 9:20 am

The Robman wrote:Does Winzip allow you the option of not using the built in directory structure?

Yes... in the Extract dialog, there's an option titled "Use folder names". When it's checked, the folder structure within the zip is used from the current folder.

I think it's better to have the apps themselves save pointers to necessary external references in .ini-type files and/or the registry.

Post by **The Robman** » Wed Jun 09, 2004 9:27 am

Paul, just to clarify, I am in favor of using some sort of directory structure, I'm just adding some opinions like everyone else.

I was very happy when the RDFs where allowed to have their own folder, for example, as it meant they didn't have to clog up the IR folder anymore.

As long as Winzip lets you ignore the built in structure, I don't mind what structure you put in there. However, I would still suggest that IR, KM and RM have seperate directories as these applications are all at the same level and are not subordinate to each other.

e34m5 · Post by **e34m5** » Wed Jun 09, 2004 9:29 am

Well...until we start using ini's IR will have to ask the user where some of the external apps are located....

Mark Pierson · Post by **Mark Pierson** » Wed Jun 09, 2004 2:49 pm

e34m5 wrote:until we start using ini's IR will have to ask the user

IR already makes extensive use of registry settings. It shouldn't be too hard to add the few additional ones that are needed for ExtInstall and IRtoWav.

e34m5 · Post by **e34m5** » Thu Jun 10, 2004 6:29 am

Let's clarify...(please don't take offense)....ini's and registry entries are totally different.

Currently the only file that resembles an ini are the RDF's.

IR uses the registry entries to store user specifics like the resizing of the screens, and paths to various folders.

In the IR changes I have done registry entries figure prominently.

I have always viewed ini's as a file that could be used to store values that are required by an app regardless of the user settings.

Mark Pierson · Post by **Mark Pierson** » Thu Jun 10, 2004 6:52 am

e34m5 wrote:IR uses the registry entries to store user specifics like... paths to various folders.

Which is really all that's needed for the ExtInstall and IRtoWav support, correct?

I have always viewed ini's as a file that could be used to store values that are required by an app regardless of the user settings.

Exactly, plus in many cases they can be used by OTHER apps that share common settings.

The advantage of .ini-type files over the registry is that they're less platform specific. BTW, I used the term ".ini-type" to denote a settings file; not necessarily the Windows specific ini type, but something that can be generic (i.e. RM's RemoteMaster.properties file).

e34m5 · Post by **e34m5** » Thu Jun 10, 2004 7:51 am

Ok...we agree.

The issue at hand was to try an create a way that users would have a directory structure that was fairly common.

Many here did not like that idea. So we'll just leave IR as is. What I have done (based on your suggestion) is store the paths in the registry after the first time IR asks the question. Subsequently it only requests the info is the it cannot find the file in the previusoly stored location.