|
From: Mojca M. <moj...@gm...> - 2007-05-07 19:49:11
|
On 5/7/07, Ethan Merritt wrote:
> On Monday 07 May 2007 11:02, Timoth=E9e Lecomte wrote:
> > Dear gnuplot (especially on MacOS) enthusiasts,
> > Dear Joe, Mojca, who tested wxt on MacOS since its early ages ;),
> > Dear Nigel, whose remarks inspired me for this mail,
> >
> > I have worked a little more on wxt for MacOS this last days.
Dear Timoth=E9e,
Thanks a lot for all your effort.
I really don't have any idea about the "dirty details" of
implementation, so I might be the wrong person to ask about the
opinion. But I'm still willing to test (and looking forward to the day
when I will be able to use the working version of it :).
> Not really. I think the prefered options are
>
> (4) Fix the upstream package in OSX
>
> It seems pointless to spend all that time re-arranging gnuplot only
> to the benefit of gnuplot users. The equivalent amount of work on
> the OSX equivalent of the GTK layer would presumably benefit ports
> of many other applications to OSX as well.
I wouldn't object the improvement of native GTK handling on Mac (I
would really like to see Mono working on Mac), but that's probably
off-topic here and outside the scope ...
> (5) Use X11 + wxWidgets on OSX rather than the apparently broken
> native OSX layer (that's possible, right?)
If I had to use X11, I would prefer to stick with AquaTerm, even
though it's functionality (esp. mouse) is limited. X11 is really the
last resort to consider. (I never use this word, but X11 really
"s*cks" on Mac.)
It's as if one would suggest using wine for running gnuplot with
windows interface on linux instead of using X11 or wxt.
It really is important to have some native driver unless there is no
other choice.
---
Thanks again for the marvellous work you do,
Mojca
|