On Sun, 9 Dec 2012, Berend Hasselman wrote:
On 07-12-2012, at 14:55, Allin Cottrell wrote:
> On Fri, 7 Dec 2012, Henrique Andrade wrote:
>
>> I'll take a detailed look at these instructions. Maybe I can insert
>> images, if you believe this can improve the understanding.
>
> Thanks, Henrique. Yes, I think screen shots would help.
>
> Up till now I've pretty much been assuming that Mac users know
> how to install software from a dmg, but it seems that's not so
> for many users. Also a first-time gretl installation on ML is
> admittedly a bit complicated since you have to install three
> separate packages.
>
> I suppose we could think about bundling GTK in the gretl dmg,
> which would cut out one step.
I've read the instructions
They look ok to me.
It would be a good idea to emphasize that on Mountain Lion
Finder windows have a tendency to open behind other windows
(on Snow Leopard they most often don't do that)(in general
Finder on Mountain Lion sometimes acts strangely especially
when opening a window the first time after login).
Yes. I did try to make that point but maybe it could be
emphasized more heavily. (Also, on earlier OS X mounting a dmg
produced an icon on the Desktop -- one that's easily
recognizable as a mounted image once you've seen it a couple
of times. But that's now gone in Mountain Lion.)
I have made an installer package from the initial "virgin"
GTK+.framework that will install the framework in
/Library/Frameworks of the system disk.
It can be downloaded with: curl -O
http://bhh.home.xs4all.nl/Gretl/GTK2-framework.pkg
That's great, thanks! I'll experiment with that myself.
I would separate the instructions into two sections:
1. First time install: installing XQuartz and GTK+.framework
2. Installing Gretl.
OK.
The first sentence of the instructions contains a spelling
error: instaling ==> installing.
Yep, I spotted that after posting the instructions.
If the GTK Framework is put into the gretl dmg the
instructions would be more involved I think. So I would
suggest to not include the framework in the gretl package.
Makes sense to me. (However, just to be clear: if we _were_ to
roll GTK into the gretl package then presumably we'd retarget
everything using install_name_tool so that the whole lot could
be installed anywhere: the GTK-related dylibs would go under
Gretl.app's Contents/Resources/lib.)
Allin