[Pythonmac-SIG] Private frameworks - BINGO!

[tmk]

Yo,

On Friday, Aug 23, 2002, at 22:58 Europe/Brussels, Mark Day wrote:

> On Friday, August 23, 2002, at 01:22 PM, Jack Jansen wrote:
>
>> Just after sending my previous mail I though I'd have a look at how 
>> OmniGraffle links to its frameworks (by using "otool -l"), and it 
>> uses the "@executable_path/../Frameworks/" construct we've discussed 
>> here before.
>
> I wonder if you could make the frameworks be a peer of the top-level 
> applications, and put enough "../"s in the the above path?  So, a tree 
> looking like:
> Python 2.3/
> Python 2.3/Frameworks/
> ...
> Python 2.3/PythonIDE.app/
> ...
>
> Presumably, the user could move the whole Python 2.3 folder around, 
> but can't move the items inside the folder unless the frameworks were 
> in one of the standard locations.
>
> But when would you move/copy the frameworks to one of the standard 
> locations?  Via some menu item in the interpretter or IDE?  Ask them 
> on first launch if they're "just trying it out" or "I'm hooked; keep 
> it around for me" (probably too annoying)?

I really like the idea though not the idea of having the frameworks 
visible they should be buried either under the app wrapper or the 
chosen Library domain. End user should not be able to easily fool 
around with frameworks.

How about building everything like the Omni folks do ( with 
Python.app/Frameworks/...)

Then the install becomes simple. At first the user has two options

1. "Test install". For testing purposes as a self-contained app with 
private frameworks. *BUT* the installer displays a message explaining 
how to make the install permanent (which should be doable easily ie via 
a simple command or menu option)

2. "Permanent install". Here we have 3 sub-options the installer would 
ask in what domain to install python (with the machine domain as the 
default)

= tmk =