Re: "Porting" scripts to Win32

In general, windows apps tend to keep all their files in one place. Either in the applications subdirectory, or in subdirectories underneath it. It's a different philosophy from the unix "spread yourself all over the disk" approach which I never quite understood.

Comment on Re: "Porting" scripts to Win32

Replies are listed 'Best First'.
Re: Re: "Porting" scripts to Win32 by MidLifeXis (Monsignor) on Feb 21, 2004 at 16:06 UTC
<MontyPython>Fud Fud Fud Fud Fud Fud Fud Fud...</MontyPython> You have "files" in %WINDIR%, %SYSTEMDIR%, the registry, the application files, the menu structure, the quicklaunch folder and other places in Windows. It does not matter upon which OS your application is installed on, but how your application is designed. For example, you could just have one configuration variable in %OS_OF_CHOICE_CONFIG_AREA%, and have that point to your application directory. Now you just have to get your executable able to be accessed through some sort of a user interface ($PATH, %PATH%, menu structure, etc). In addition, Windows is based on the model of including all functionality you need for your application in one executable (shared libs / dlls as an exception), whereas Unix is build on the reusable tools model. There are more interdependancies, so you either need to have a fixed location for common tools, or you need to have some infrastructure to be able to find the tools you need. The re-use model requires that you be able to find the tools. Of course, I am probably just falling for a troll :) --MidLifeXis	[reply]

Replies are listed 'Best First'.

Re: Re: "Porting" scripts to Win32
by MidLifeXis (Monsignor) on Feb 21, 2004 at 16:06 UTC

You have "files" in %WINDIR%, %SYSTEMDIR%, the registry, the application files, the menu structure, the quicklaunch folder and other places in Windows.

It does not matter upon which OS your application is installed on, but how your application is designed. For example, you could just have one configuration variable in %OS_OF_CHOICE_CONFIG_AREA%, and have that point to your application directory. Now you just have to get your executable able to be accessed through some sort of a user interface ($PATH, %PATH%, menu structure, etc).
In addition, Windows is based on the model of including all functionality you need for your application in one executable (shared libs / dlls as an exception), whereas Unix is build on the reusable tools model. There are more interdependancies, so you either need to have a fixed location for common tools, or you need to have some infrastructure to be able to find the tools you need. The re-use model requires that you be able to find the tools.

Of course, I am probably just falling for a troll :)

--MidLifeXis

[reply]