[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MacOS X development and support

From: Janek Warchoł
Subject: Re: MacOS X development and support
Date: Mon, 5 Mar 2012 17:42:06 +0100

On Mon, Mar 5, 2012 at 11:08 AM, David Kastrup <address@hidden> wrote:
> James <address@hidden> writes:
>> Hello,
>> On 5 March 2012 07:45, Phil Holmes <address@hidden> wrote:
>>> ----- Original Message ----- From: "Graham Percival"
>>> <address@hidden>
>>> To: "Colin Hall" <address@hidden>
>>>>> Let's drop Lilypad. It's getting in the way of regular releases.
>>>> Disagree.
>>> Disagree.  I'm with Colin.  I've already said that I can't see the point of
>>> it on Windows: it's a cut-down version of notepad.  If it's the same on Mac,
>>> I don't see the value.
>> \PointAndClickOn
>> That was a great feature for a 'mac user' like me. While I can run CLI
>> in, getting another editor to work with pointAndClick was
>> fruitless and frustrating (at least for 2.12 and 2.13.x when I had my
>> mac).
>> So I'm with Graham on this one.
> As far as I understand, in spite of the initial activities of core
> LilyPond developers, LilyPad is basically an external application that
> we just wrap and don't actively codevelop (meaning that its overlap with
> actual LilyPond development nowadays is rather minimal).
> The principal goal is setting up the user with an environment where he
> can start working right away.
> We could pick a different target for that purpose.  Personally, I want
> to get to a state where Emacs will make a compellingly useful part of
> the music creation toolchain.  But it would still not be something you
> would want to install as part of an installer for LilyPond.  It's more
> like it would be nice to have some functionality looking for an
> installed version of Emacs and integrating with it.
> I think Frescobaldo might be a nice fit by now (as far as I understand,
> it does no longer require KDE, merely Qt).  It does quite more than
> LilyPad, integrates nice with a GUI, and still does not obscure working
> with LilyPond, like the applications NtEd and similar do.

generally +1.
I'd do this in this way: when the installer installs LilyPond, ask the
user if he wants to install Frescobaldi too.  Thus, we won't make our
installer larger and won't have to compile Frescobaldi on our own.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]