lilypond-user
[Top][All Lists]
Advanced

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

Re: Naming convention brainstorming


From: Jacques Menu
Subject: Re: Naming convention brainstorming
Date: Mon, 2 Feb 2015 11:25:50 +0100

Hello folks,

I’d use « data entry mode », as opposed to « presentation fine-tuning ».

JM

Le 2 févr. 2015 à 09:04, Urs Liska <address@hidden> a écrit :

Hi all,

thank you for your feedback. I've got the following suggestions:
  • Content mode (as opposed to presentation)
  • Entry mode
  • Working mode
  • Crafting mode
  • Sandbox
  • Debug-structure

When collecting that list I realized that "entry mode" got three "votes" - while I had already decided to settle on this term. I think this is the most generic and unbiased way of expressing the idea, although even this one is not perfect. What would perfectly match the essence would be "edit mode" - but that is highly ambiguous so it is practically useless.

Best
Urs



Am 01.02.2015 um 00:41 schrieb Urs Liska:
Hi all,

for quite some time now I've been using a concept that is very useful, but finally I'd like to give it an authoritative name to be used in different places.

I'm talking about the working, thinking and compiling mode when I'm working on the _content_ of a score and not it's final visual appearance. This mode is characterized for example by
- not caring too much about layout
- not caring too much about engraving quality
- being interested in visual feedback about manual interventions
  (e.g. coloring annotations or the result of custom functions)

Originally we talked about it as "draft mode" but this doesn't seem to hit the spot. Nor do "devel mode" or "preview mode".

I would really like to find the right term now because I want to make that kind of an authoritative term for a configuration option in a redesigned openLilyLib and sort of a general library specification in that context. There should be a common configuration option that library authors can (and are encouraged to) respect in their functions. Say I have a library function "\crossVoiceTie" that does all the work for me with a hidden voice etc. Then this should highlight that tie or the hidden noteheads when that special mode is active.
This approach has proven extremely useful and I'd be happy to promote this as a more general best-practice.

So what are your feelings about this mode of working *before* finishing an engraving to publication quality?

Thanks for any opinions
Urs


_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user


reply via email to

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