Re: Cleaning up GSoC project ideas

On 02/02/2017 04:10 PM, Urs Liska wrote: However, I suggest that we either remove such orphaned projects or at least compress and move them down to the bottom of the page. A concise page with actual and current projects is quite important for attracting students, I think. Sorry for the delay

Re: Cleaning up GSoC project ideas

Am 06.02.2017 um 15:40 schrieb Paul: > On 02/02/2017 04:10 PM, Urs Liska wrote: > >> However, I suggest that we either remove such orphaned projects or at >> least compress and move them down to the bottom of the page. A concise >> page with actual and current projects is quite important for

Re: Contemporary notation (Re: GSoC projects list)

Jeffery Shivers writes: > I've thought about this a lot, and I agree that OLL would be the > obvious means to implement a *contemporary notation* package with > LilyPond. > > A huge problem we will face with doing this, which will always be a > problem no matter how

Re: Contemporary notation (Re: GSoC projects list)

Am 06.02.2017 um 15:10 schrieb Jeffery Shivers: > I've thought about this a lot, and I agree that OLL would be the > obvious means to implement a *contemporary notation* package with > LilyPond. > > A huge problem we will face with doing this, which will always be a > problem no matter how

Re: Contemporary notation (Re: GSoC projects list)

> Man, that sounds to me like making explosives available to as many users > as possible. I mean, I recognize that there is a need apparently to be > served, but this rather sounds like a call to expanding that need. Hm, no. There is an absurd amount of weird *needs* from composers nowadays who

Re: Contemporary notation (Re: GSoC projects list)

I've thought about this a lot, and I agree that OLL would be the obvious means to implement a *contemporary notation* package with LilyPond. A huge problem we will face with doing this, which will always be a problem no matter how accessible/robust the library, is that there will very often be

Re: Contemporary notation (Re: GSoC projects list)

Sorry, I responded to David before reading your response, but I see that we kind of said the same things. > Indeed this should be discussed thoroughly before actually investing > substantial energy in implementation. But for now I'd defer this to a moment > if there should be a student interested

Re: Automatic LyricExtenders (issue 313240043 by perpeduumimmob...@gmail.com)

It's not really clear to me where I am supposed to go from here with what I proposed. I lean towards going back to creating my own version of this again since this one contains so much stuff that does not ring a bell with me.

Re: Automatic LyricExtenders (issue 313240043 by perpeduumimmob...@gmail.com)

Hi, Am 06.02.2017 um 20:08 schrieb d...@gnu.org: > https://codereview.appspot.com/313240043/diff/21/scm/define-grob-properties.scm#newcode188 > > scm/define-grob-properties.scm:188: (collapse-length ,ly:dimension? "An > automatically generated > collapse-width maybe? Length is more like a

Re: Contemporary notation (Re: GSoC projects list)

Hi all, personally, I think, it is as always in software development that addresses a wide audience: the challenge to find an appropriate level of abstraction. If you want to support *any* kind of notation, then just use a painting or CAD software. Obviously, you do not want to

HTML 4.01 requires "type" attribute for "script" element (issue 315540043 by d...@gnu.org)

LGTM https://codereview.appspot.com/315540043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Automatic LyricExtenders (issue 313240043 by perpeduumimmob...@gmail.com)

On 2017/02/06 11:02:56, akobel wrote: Version 2017-02-04 by David Not "by David" but "by Kurt". David merely rebased Kurt's new version. https://codereview.appspot.com/313240043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: GSoC projects list

Am 06.02.2017 um 08:48 schrieb Werner LEMBERG: >> So essentially per now we will have only 4/5 projects left: >> >> * Improving internal chord structure >> * Adopting SMuFL >> * Adding glyph variants >> * openLilyLib testing and documentation >> >> I find this list quite disappointing,

Re: GSoC projects list

>> . a figured bass mode similar to (jazz) chord mode to display >> figured bass as chords > > What do you mean exactly? Determining the chord name from the > figures and displaying it? This also, but mainly displaying the figured bass chord as notes (which is essentially equivalent). >> .

Contemporary notation (Re: GSoC projects list)

One thing I'm missing about our projects list is actual *notation* projects. Currently (i.e. when the current wave of purges has been completed) there is no project that adds to or improves LilyPond's notation. All projects are important items, but maybe this isn't really attractive to students.