O
omega
Greetings, George. Thank you for providing the answer.
The ShellNew is fine with me. Windows lets you put that anywhere, and add
or delete what you want. (Even when the stubborn MSOffice is involved).
The "application data" directory usage by a program is major peeve for me.
Mozilla is one of the big sinners. Even when you direct profiles elsewhere,
it roots a few files there, in concrete. (In contrast, its nephew, KMeleon,
is clean in this regard.) At least, from your report, 00's dropping there
are limited to a single ini.
And, the essence. No libraries snuck into the system directory. And no
messy constructs shoved over in the "common files" directory. Good news.
I plan to give it no associations. I'd do it this way regardless; but
further, at the site, I think they were saying that the application does
not know how to toggle its control of associations - that once it takes
them, it won't return them.
I don't think they'd change from reasonable, to uncivil (file spew), as part
of new version. So I take your report as valid for my comfort and assurance.
I much appreciate it.
The OO installation issue, it sounds better than I anticipated.
I have tracked an installation of the previous stable version with
InCtrl5, but not the latest one. However, I will attempt an answer as
this is the kind of question I have before installing many a program.
For an office suite, I find it admirably restrained. There is a
single .ini file in <Application Data>, a directory called
<Windows\ShellNew> and that's pretty much all I can discern.
The ShellNew is fine with me. Windows lets you put that anywhere, and add
or delete what you want. (Even when the stubborn MSOffice is involved).
The "application data" directory usage by a program is major peeve for me.
Mozilla is one of the big sinners. Even when you direct profiles elsewhere,
it roots a few files there, in concrete. (In contrast, its nephew, KMeleon,
is clean in this regard.) At least, from your report, 00's dropping there
are limited to a single ini.
And, the essence. No libraries snuck into the system directory. And no
messy constructs shoved over in the "common files" directory. Good news.
This, I suspect, depends heavily upon the choice of file association
one has during the install process. Yes, a lot of keys are added,
mainly in the HKEY_CLASSES_ROOT hierarchy, if you bind it with all the
types it can handle. But that's inevitable, isn't it? Other than
that, use of the registry is sparse.
I plan to give it no associations. I'd do it this way regardless; but
further, at the site, I think they were saying that the application does
not know how to toggle its control of associations - that once it takes
them, it won't return them.
Take the above with a grain of salt. It is possible that they were
remnants of the previous version and do not apply to the latest one.
I don't think they'd change from reasonable, to uncivil (file spew), as part
of new version. So I take your report as valid for my comfort and assurance.
I much appreciate it.
The OO installation issue, it sounds better than I anticipated.