Cannot locate Scripts

[Juan Conejero]

I have a PI installed into a subdirectory (exclusive for all astronomical applications), and it works perfectly.

That's the key concept: give the user freedom to install anywhere. PI just works on any directory you install it (provided you have the required permissions to write on it), and that's true on any supported platform. One of my goals with PI is being as OS-agnostic as possible.

For development purposes, I frankly prefer C:\PCL instead of "C:\Program Files\PCL". One of the reasons is that PixInsight is not a program, it's much more than a program (it provides source code, headers, binary files, documentation, etc.), so putting it into a "Program Files" thing is inaccurate to say the least. And spreading its contents across a web of system folders is, in my opinion, a poorer choice. So why not just PCL, anywhere?

[Carlos Milovic]

Also, if we buy new computers to run PI faster, why not placing it at the root?

[Andres.Pozo]

Because we are special
More seriously, having PI close to the root is convenient for developers.

I am a professional developer and one of the few things that I am sure of is that the software that I write must be designed for the users and not for me...

What is the installation directory of PixInsight in the Unix clones? ¿"/"?

In my opinion, there is NO reason for installing in C:\PCL in Windows.

[georg.viehoever]

C:\PCL can also be an issue due to security problems. Most installers take care to set the right permissions in C:/Program Files, but most fail to do so for other places...

Georg

[Niall Saunders]

I still think that Juan should just rewrite PixInsight to be the Operating System- given his track record he would make a far better job of it than Microsoft or Apple anyway

[Carlos Milovic]

I second the motion