Re: Is GridLY the future?

2015-04-27 Thread Werner LEMBERG
>>> Sometimes people are scared by a maybe too rough tone, though. >> >> It *is* a problem, and not only about code quality. More than once >> I abandoned a patch before the quality of the code was even >> considered but because of fruitless discussions about use cases, >> when for example using L

Re: Is GridLY the future?

2015-05-02 Thread Janek Warchoł
Hi, 2015-04-28 7:49 GMT+02:00 Werner LEMBERG : > >>> Actually I'm quite convinced that this situation has a notable >>> impact on the overall development activiyt. > > I don't think so. Have you ever observed the development of Emacs or > the Linux kernel, for example by reading the `emacs-devel'

Re: Is GridLY the future?

2015-05-02 Thread Werner LEMBERG
> The behaviour that discouraged me from working on LilyPond for some > time was not obviously unacceptable (i.e. it wasn't some ad hominem > attack, nor anything else unanimously condemned by others). Rather, > it was the general attitude of some people who sometimes seem to > oppose changes onl

Re: Is GridLY the future?

2015-05-02 Thread Urs Liska
Am 03.05.2015 um 06:28 schrieb Werner LEMBERG: The behaviour that discouraged me from working on LilyPond for some time was not obviously unacceptable (i.e. it wasn't some ad hominem attack, nor anything else unanimously condemned by others). Rather, it was the general attitude of some people

Re: Is GridLY the future?

2015-05-03 Thread Werner LEMBERG
>> This is what I meant with `defending your code'. And sometimes it >> simply happens that there is no concensus. > > I hope you simply didn't read Janek's comment carefully enough. The > main point in his last sentence is not about the alternative but > about an attitude of rejecting suggesti

Is GridLY the future? (Was: Do we really offer the future?)

2015-04-22 Thread Gilles
Hello. I think you could vastly benefit from using openLilyLib's GridLY library. Of course thst's only viable for new projects. That looks interesting just from a quick reading of https://github.com/openlilylib/openlilylib/tree/master/ly/gridly I stumbled upon that page only through a web s

Re: Is GridLY the future? (Was: Do we really offer the future?)

2015-04-22 Thread Urs Liska
Am 22.04.2015 um 21:29 schrieb Gilles: Hello. I think you could vastly benefit from using openLilyLib's GridLY library. Of course thst's only viable for new projects. That looks interesting just from a quick reading of https://github.com/openlilylib/openlilylib/tree/master/ly/gridly I st

Re: Is GridLY the future? (Was: Do we really offer the future?)

2015-04-22 Thread Thomas Morley
2015-04-22 21:41 GMT+02:00 Urs Liska : > > > Am 22.04.2015 um 21:29 schrieb Gilles: >> >> Hello. >> >>> I think you could vastly benefit from using openLilyLib's GridLY >>> library. Of course thst's only viable for new projects. >> >> >> That looks interesting just from a quick reading of >> http

Re: Is GridLY the future? (Was: Do we really offer the future?)

2015-04-23 Thread Urs Liska
Am 22.04.2015 um 22:58 schrieb Thomas Morley: The main objective of openLilyLib (old and new) is providing a platform for >extending LilyPond without having to integrate everything in the core. This >is a) because not every extension should bloat the core and b) even when >something would fit w

Re: Is GridLY the future? (Was: Do we really offer the future?)

2015-04-27 Thread Janek Warchoł
2015-04-23 12:37 GMT+02:00 Urs Liska : > > Am 22.04.2015 um 22:58 schrieb Thomas Morley: >> I don't think it's a problem to get new functionality into LilyPond, >> _if_ it's coded properly. >> Sometimes people are scared by a maybe too rough tone, though. >> >> [...] > > It *is* a problem, and not

Re: Is GridLY the future? (Was: Do we really offer the future?)

2015-04-27 Thread Janek Warchoł
2015-04-28 7:27 GMT+02:00 Janek Warchoł : > I agree with Urs - in my opinion LilyPond is not developer-friendly > enough. Actually it's one of the reasons why I was away for so long - > the friction in the community caused me to loose some motivation to > work on LilyPond. And I'm not the only on