bugDenemo - Bugs: bug #36938, Gui Problems with Score Layout


bug #36938: Gui Problems with Score Layout

Submitter:  John Beattie <jabeattie>
Submitted:  Tue 24 Jul 2012 02:35:11 PM UTC
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Confirmed
Privacy:  Public Assigned to:  None
Originator Name:  Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup

Tue 24 Jul 2012 05:02:10 PM UTC, comment #1: 

Very useful to have these all collected in one place, thank you. They are uncannily similar to my thoughts on the subject, especially how uninviting the score layout view looks. When I thought of it I envisaged a sort of skeletal view of the score with only the music not spelt out in detail. I had the idea that it would be easier to work on those global aspects without having to scroll over the actual music. I still have it in mind that things like the title should look at a glance like the title, I think there is quite a bit that could be done in that direction.

 But this idea is somewhat at odds with the idea of letting users see the structure of things like transposition - a transposed block in a score (a movement, say, or a part) is not explicit, you can only tell that it is transposed by comparing with other parts, or the original input. But creating a box around the transposed section labelled with the transposition makes the user do some deciphering which may not be the thing of interest at a given time.

Still, the score layout has enormous potential for advanced users - setting different page breaks in different parts for example.

Richard Shann <rshann>
Group administrator
Tue 24 Jul 2012 02:35:11 PM UTC, original submission:  

Using 0.9.5 rc2 on Windows

I am going to break the golden rule and use 1 bug to record what could be multiple problems.
They are all cosmetic problems with Score Layout.
They can all be postponed to a later release.
They will probably be fixed at the same time  - one way or another.

1) My first impressions of Score Layout was "I shouldn't be here!".  If that is my impression, what would a non-technical user think? This new feature has the potential to move the user further away from raw Lilypond. You need to make the user want to use this feature. I am not a GUI expert so I can't tell you what to do to achieve this. I can just say it looks wrong and that is more that just the normal case of everybody thinking that the gui should be different (that part follows!).

2) For each staff, you have a graphic showing the clef used in the denemo score. However if you change the clef in the score, it doesn't change in the Score Layout. So you can have different layouts telling different things about the common score. They do change eventually but it might take shut down and restart of denemo.

3) Still on the clef graphic. This is shown as a button. You can press it and nothing happens. I can't think what you could do with such a button so if it is just for information, it shouldn't be a button.

4) When you open up voices the buttons for the Music for voice do not line up. The 1st or only voice is to the right due to the Initial Signatures. The second voice is to the left underneath the Initial Signatures.

5) When you open the Initial Signature, the height of the button for Music for Voice 1 increases. That doesn't look right. A similar thing happens with the graphic for clef, the 2 arrows and the various X boxes but it doesn't look as bad for them. Perhaps fixing 4) will also fix 5).

6)There is something about the X boxes that doesn't look right - yet they do exactly what you would expect them to do so I have no idea what it is that I don't like!

7) Personally I don't mind writing bits of Lilypond. I can & do add scripts and insert directive manually. I don't even mind that I am specifying notes in what I believe is the Dutch notation i.e. bes for b flat. However I am not, or at least should not, be your target user. I am (was) a programmer and a musician (as I expect most of the development team are). The target user should just be a musician whose technical knowledge stops at the point where they load the application. In other words you have to hide the Lilypond syntax as far as possible. The problem with that is the more you hide it, the more you loose of Lilypond's flexibility. I could say that when editing e.g. the composer, the user should only type in the name but I sometimes want /bold or even /column etc. Perhaps you could scan the user's input, if it is just ordinary letter, wrap it in quotes and put the <keyword> =  in front of it. If it contains back slashes then wrap in braces and put <keyword> = \markup  in front.
If you you look at print transpose, you have a way to specify the  transposition where the user only needs to know how to specify the interval. Within Score Layout, the user is expected to edit the start of the Staff block.

John Beattie <jabeattie>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by rshann (Posted a comment)
  • -email is unavailable- added by jabeattie (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2012-07-24 rshann StatusNone Confirmed

    Back to the top

    Powered by Savane 3.13-04b1.
    Corresponding source code