Re: [openlilylib] Discuss restructuring
Am 06.07.2014 17:15, schrieb Paul Morris: Uns Liska wrote Starting by tagging the existing snippets sounds fine to me. But not tagging directly but collecting suggestions first. Then decide about a set of tags and apply them during the move. Ok, sure. Something to consider: since you are planning on writing a script to walk through the library and give some output about what files have what tags, it might make sense to go ahead and start that and then you'd have it as a tool to help with the process of editing the tags. Hm, I think I _must not_ start with such a script right now, since I know that this - although being not too complex - will eat up too much of my time and concentration. But your message triggered a little bit of thought, and I came to the conclusion that we should use a website (i.e. openlilylib.org) for the documentation. The script will have two stages: parsing the content of the library and generating documentation from the resulting internal representation. I think generating complete HTML pages isn't more complicated than generating Markdown, but the results are better to use: We have more control over the layout and formatting options than on a Github Wiki, _and_ we have a self-contained HTML site that can also be deployed locally. For example, it would be nice to know what tags have already been entered for all of the files (which is how their authors were tagging them). This raises yet another questions: the relation between pre-selected and free-form tags. Maybe a good compromise would be to have a (new) field snippet-category where only a number of predefined entries are valid (and if someone wants to add a category this should be discussed) and the existing field tags where free-form tags can be used. For this it would make sense to have a list with all used tags available and encourage authors to reuse existing tags rather than adding new ones (particularly it doesn't make sense to have singular and plural forms of the same tags). (I guess this might mean moving the files first and then working on the tags?) Yes, that would mean that. Maybe we can have a compromise. A script parsing the content of the tags field from all files shouldn't be hard to write. So we could: - agree upon an initial set of categories - agree upon a naming convention for tags (e.g. the same dashed-lowercase-scheme as for filenames). - reconsider the metadata structure (which fields are mandatory, which optional, default values?) - move all files in one go (that is: one commit for each snippet, as the files are not only moved but also renamed) - clean up and tag the snippets. One by one and using pull request. (I think this should be done _with_ review and not be left to the authors' discretion) Urs -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/openlilylib-Discuss-restructuring-tp163922p164086.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [openlilylib] Discuss restructuring
Am 07.07.2014 09:55, schrieb Urs Liska: Maybe we can have a compromise. A script parsing the content of the tags field from all files shouldn't be hard to write. So we could: - agree upon an initial set of categories - agree upon a naming convention for tags (e.g. the same dashed-lowercase-scheme as for filenames). - reconsider the metadata structure (which fields are mandatory, which optional, default values?) I have updated the snippet-template file which contains a suggestion for all required and optional metadata fields. It can be inspected at https://github.com/openlilylib/openlilylib/blob/reorganization/library/snippet-template.ily Best Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [openlilylib] Discuss restructuring
Am 07.07.2014 10:37, schrieb Urs Liska: Am 07.07.2014 09:55, schrieb Urs Liska: Maybe we can have a compromise. A script parsing the content of the tags field from all files shouldn't be hard to write. So we could: - agree upon an initial set of categories - agree upon a naming convention for tags (e.g. the same dashed-lowercase-scheme as for filenames). - reconsider the metadata structure (which fields are mandatory, which optional, default values?) I have updated the snippet-template file which contains a suggestion for all required and optional metadata fields. It can be inspected at https://github.com/openlilylib/openlilylib/blob/reorganization/library/snippet-template.ily ... and I have created a proof-of-concept pull request: https://github.com/openlilylib/openlilylib/pull/40 Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SPAM] Re: [openlilylib] Discuss restructuring
Hi Urs and all, I followed the discussion only roughly, but I think it is a step in the right direction. I'd like to bring up the scheme-modules, I came up with. They need a fixed folder-structure and need to be updated according to the path they are stored in. Should we have a dedicated folder for scheme-modules or shall we store them for example in includes? Best, Jan-Peter Am 05.07.2014 14:28, schrieb Urs Liska: Am 05.07.2014 10:31, schrieb Urs Liska: Thanks. I think we will have to reconsider our metadata section and then do the transfer in that reorganization branch. I strongly suggest to excusively do that using pull requests, even among the members with push access. One more thing I would suggest to implement is some more standardization for the examples files. These should have formalized headers that are created by pulling in the fields from the definitions file. This should be quite easy to implement: Create one file with the redefinition of \booktitlemarkup and place this somewhere outside the user-accessible files. Then each examples file can simply include this with a relative path and there you go. (- This implies that our metadata considerations take this into account too) I have updated the Wiki page https://github.com/openlilylib/openlilylib/wiki and added a note about the reorganization process in the README.md on the restructuring branch. Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SPAM] Re: [openlilylib] Discuss restructuring
Am 07.07.2014 11:37, schrieb Jan-Peter Voigt: Hi Urs and all, I followed the discussion only roughly, but I think it is a step in the right direction. I'd like to bring up the scheme-modules, I came up with. They need a fixed folder-structure and need to be updated according to the path they are stored in. Should we have a dedicated folder for scheme-modules or shall we store them for example in includes? I had thought about this too, but as I don't completely understand what's going on there I didn't look further so far. If that's OK with you I'd suggest to handle the scheme-modules only after the conversion of the snippets. Or does the conversion of some snippets already depend on that issue? I thought of putting them in /includes/scheme-modules Does that fit? BTW: I'm not sure about all the lalily stuff. Would you consider merging that among all the other snippets or should that rather have a dedicated folder below /library (i.e. beside oll, templates etc.)? Best Urs Best, Jan-Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
frescobaldi meta key?
Hi, the default keyboard shortcut for toggling the music view on/off uses the META key. Which key is that?Is is possible to maximise/restore the music view? Thanks, Gerard ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SPAM] Re: [openlilylib] Discuss restructuring
Am 07.07.2014 11:46, schrieb Urs Liska: I followed the discussion only roughly, but I think it is a step in the right direction. I'd like to bring up the scheme-modules, I came up with. They need a fixed folder-structure and need to be updated according to the path they are stored in. Should we have a dedicated folder for scheme-modules or shall we store them for example in includes? I had thought about this too, but as I don't completely understand what's going on there I didn't look further so far. If that's OK with you I'd suggest to handle the scheme-modules only after the conversion of the snippets. Or does the conversion of some snippets already depend on that issue? The module naming will change inherently and that will affect some snippets. But that should be easy to identify as I seem to be the only one doing such nasty stuff ;) I thought of putting them in /includes/scheme-modules Does that fit? That's fine. Shall I prepare the scheme stuff? I would propose a root folder like suggested in the include files folder BTW: I'm not sure about all the lalily stuff. Would you consider merging that among all the other snippets or should that rather have a dedicated folder below /library (i.e. beside oll, templates etc.)? I might put snippets originating from lalily - templating, edition-engraver and such - into a folder 'lalily'. In fact, I might reconstruct the whole lalily-complex in that folder and probably make it more convenient to use only parts or the whole workflow. Best, Jan-Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SPAM] Re: [openlilylib] Discuss restructuring
Am 07.07.2014 12:01, schrieb Jan-Peter Voigt: Am 07.07.2014 11:46, schrieb Urs Liska: I followed the discussion only roughly, but I think it is a step in the right direction. I'd like to bring up the scheme-modules, I came up with. They need a fixed folder-structure and need to be updated according to the path they are stored in. Should we have a dedicated folder for scheme-modules or shall we store them for example in includes? I had thought about this too, but as I don't completely understand what's going on there I didn't look further so far. If that's OK with you I'd suggest to handle the scheme-modules only after the conversion of the snippets. Or does the conversion of some snippets already depend on that issue? The module naming will change inherently and that will affect some snippets. But that should be easy to identify as I seem to be the only one doing such nasty stuff ;) I thought of putting them in /includes/scheme-modules Does that fit? That's fine. Shall I prepare the scheme stuff? I would propose a root folder like suggested in the include files folder OK, then you can move the files to /includes/scheme-modules. Just keep in mind: Create a new branch from the head of `reorganization` and open a pull request, but not against `master` (which will be presented by default) but against `reorganization`. BTW: I'm not sure about all the lalily stuff. Would you consider merging that among all the other snippets or should that rather have a dedicated folder below /library (i.e. beside oll, templates etc.)? I might put snippets originating from lalily - templating, edition-engraver and such - into a folder 'lalily'. In fact, I might reconstruct the whole lalily-complex in that folder and probably make it more convenient to use only parts or the whole workflow. I would be fine with having /library/lalily next to /library/oll, but I'd prefer having some other opinions on this. Best Urs Best, Jan-Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: frescobaldi meta key?
It depends on the platform. For example, on Windows this is usually the Windows key if available. Maybe you can tell us what platform you're using? On Mon, Jul 7, 2014 at 5:49 PM, Gerard McConnell gerine...@gmail.com wrote: Hi, the default keyboard shortcut for toggling the music view on/off uses the META key. Which key is that?Is is possible to maximise/restore the music view? Thanks, Gerard ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- Abel Cheung New GPG Key fingerprint: F43B 7F88 3D7B 4B58 928E 0151 EC2B E414 3B03 A8AC Old GPG Key fingerprint: 671C C7AE EFB5 110C D6D1 41EE 4152 E1F1 C671 86FF ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
LilyPond meeting 2014?
Hi all, It's been almost two years since the Waltrop 2012 LilyPond Meeting, in which i had the pleasure to participate. What about organizing another meeting this year? - who'd be interested? - where? (David, are you interested in being the host again?) - when? (i suggest 15-17 August) If the meeting will take place within 1500 km from Warsaw (e.g. at Waltrop) and there will be at least 4 other participants, count me in :) best, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond meeting 2014?
I'll be definitely unavailable Aug 10-24. This doesn't mean that other dates would work, but that's what I can say right now. Apart from that I have an idea about a beautiful and appropriate location in Stuttgart I could ask for. I'd be more than happy to join this year, but I can't promise anything. Urs On 7. Juli 2014 16:24:34 MESZ, Janek Warchoł janek.lilyp...@gmail.com wrote: Hi all, It's been almost two years since the Waltrop 2012 LilyPond Meeting, in which i had the pleasure to participate. What about organizing another meeting this year? - who'd be interested? - where? (David, are you interested in being the host again?) - when? (i suggest 15-17 August) If the meeting will take place within 1500 km from Warsaw (e.g. at Waltrop) and there will be at least 4 other participants, count me in :) best, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [openlilylib] Discuss restructuring
Uns Liska wrote Hm, I think I _must not_ start with such a script right now, since I know that this - although being not too complex - will eat up too much of my time and concentration. But your message triggered a little bit of thought, and I came to the conclusion that we should use a website (i.e. openlilylib.org) for the documentation. The script will have two stages: parsing the content of the library and generating documentation from the resulting internal representation. I think generating complete HTML pages isn't more complicated than generating Markdown, but the results are better to use: We have more control over the layout and formatting options than on a Github Wiki, _and_ we have a self-contained HTML site that can also be deployed locally. Yep. Uns Liska wrote This raises yet another questions: the relation between pre-selected and free-form tags. Maybe a good compromise would be to have a (new) field snippet-category where only a number of predefined entries are valid (and if someone wants to add a category this should be discussed) and the existing field tags where free-form tags can be used. For this it would make sense to have a list with all used tags available and encourage authors to reuse existing tags rather than adding new ones (particularly it doesn't make sense to have singular and plural forms of the same tags). Is your idea that the snippet-category would be restricted to a single category per snippet and would be used for a table of contents in the documentation? While the tags would be used for an index? With the table of contents / categories being more standardized and predefined than the index / tags? A question this raises: Will categories also appear in tags field? Or rather, will categories be included as entries in the index? Basically, can I look in the index for the categories as well as the tags? (If not then the index is not as helpful because the primary topics that snippets fall under is not in the index.) So I think it makes sense for the categories to also appear in the index. Another way to do this would be to have only a tags field and have the first tag entered in that field be the primary tag which is used for the table of contents. It would need to come from a predefined set of tags. I'm not sure if that's better or not. Uns Liska wrote (I guess this might mean moving the files first and then working on the tags?) Yes, that would mean that. Maybe we can have a compromise. A script parsing the content of the tags field from all files shouldn't be hard to write. So we could: - agree upon an initial set of categories - agree upon a naming convention for tags (e.g. the same dashed-lowercase-scheme as for filenames). - reconsider the metadata structure (which fields are mandatory, which optional, default values?) - move all files in one go (that is: one commit for each snippet, as the files are not only moved but also renamed) - clean up and tag the snippets. One by one and using pull request. (I think this should be done _with_ review and not be left to the authors' discretion) Sounds fine to me. -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/openlilylib-Discuss-restructuring-tp163922p164121.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond meeting 2014?
2014-07-07 16:24 GMT+02:00 Janek Warchoł janek.lilyp...@gmail.com: Hi all, It's been almost two years since the Waltrop 2012 LilyPond Meeting, in which i had the pleasure to participate. What about organizing another meeting this year? - who'd be interested? - where? (David, are you interested in being the host again?) - when? (i suggest 15-17 August) I'd be happy to join you, if my plans meet yours. My decision-making tends to be last minute.. but I'll probably do a bike trip in North Europe from 10th to end of August and Germany will be for sure one of the countries I'll visit. Of course I'll use also the train to jump to the interesting places. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond meeting 2014?
Urs Liska u...@openlilylib.org writes: On 7. Juli 2014 16:24:34 MESZ, Janek Warchoł janek.lilyp...@gmail.com wrote: Hi all, It's been almost two years since the Waltrop 2012 LilyPond Meeting, in which i had the pleasure to participate. What about organizing another meeting this year? - who'd be interested? - where? (David, are you interested in being the host again?) - when? (i suggest 15-17 August) If the meeting will take place within 1500 km from Warsaw (e.g. at Waltrop) and there will be at least 4 other participants, count me in :) I'll be definitely unavailable Aug 10-24. This doesn't mean that other dates would work, but that's what I can say right now. The Waltroper Parkfest URL:http://www.waltroper-parkfest.de runs from August 29th to August 31st. It is an excellent diversion for accompanying guests and participants, though no participants actually were inclined to go there in 2012. For German-speaking participants, let me quote Das Waltroper Parkfest findet 2014 an den letzten drei Augusttagen statt. Highlights des Ostvest-Kulturspektakels auf vier Bühnen sind Auftritte von Juli, Hennes Bender, Brings und Too Strong, sowie eine gemeinsame Show der NDW-Stars Markus, Geier Sturzflug, Hubert Kah und Fräulein Menke. Putting the meeting in parallel with the Parkfest in a similar manner as last time would place it on August 28th to September 2nd, with the start and end days mostly being for arrival and departure. The disadvantage is that the availability of external accommodation may be strained during the Parkfest so one should book soon enough if that is desired. Camping on our premises is possible, and we can accommodate a number of people in the house, particularly if they have sleeping bags of their own. Apart from that I have an idea about a beautiful and appropriate location in Stuttgart I could ask for. I don't know about appropriate but the surroundings here _are_ rather scenic. Judging from the last meeting, nobody can bother with going outside anyway as long as the Internet is up. And we've more than doubled our bandwidth as compared to last time when it was at 1Mbps. This year's bird sightings on the premises include cuckoos, great tits, white wagtails, green woodpeckers, black redstarts, barn swallows, spotted flycatchers, magpies, yellowhammers, buzzards and a number of others. If there is sufficient interest, I'd be quite willing to host another meeting. Waltrop is north of Dortmund in the Ruhr area. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SPAM] Re: [openlilylib] Discuss restructuring
On 7. Juli 2014 16:48:44 MESZ, Paul Morris p...@paulwmorris.com wrote: Uns Liska wrote Hm, I think I _must not_ start with such a script right now, since I know that this - although being not too complex - will eat up too much of my time and concentration. But your message triggered a little bit of thought, and I came to the conclusion that we should use a website (i.e. openlilylib.org) for the documentation. The script will have two stages: parsing the content of the library and generating documentation from the resulting internal representation. I think generating complete HTML pages isn't more complicated than generating Markdown, but the results are better to use: We have more control over the layout and formatting options than on a Github Wiki, _and_ we have a self-contained HTML site that can also be deployed locally. Yep. Uns Liska wrote This raises yet another questions: the relation between pre-selected and free-form tags. Maybe a good compromise would be to have a (new) field snippet-category where only a number of predefined entries are valid (and if someone wants to add a category this should be discussed) and the existing field tags where free-form tags can be used. For this it would make sense to have a list with all used tags available and encourage authors to reuse existing tags rather than adding new ones (particularly it doesn't make sense to have singular and plural forms of the same tags). Is your idea that the snippet-category would be restricted to a single category per snippet and would be used for a table of contents in the documentation? While the tags would be used for an index? With the table of contents / categories being more standardized and predefined than the index / tags? A question this raises: Will categories also appear in tags field? Or rather, will categories be included as entries in the index? Basically, can I look in the index for the categories as well as the tags? (If not then the index is not as helpful because the primary topics that snippets fall under is not in the index.) So I think it makes sense for the categories to also appear in the index. I think that's good. Should be no problem to realize either. Another way to do this would be to have only a tags field and have the first tag entered in that field be the primary tag which is used for the table of contents. It would need to come from a predefined set of tags. I'm not sure if that's better or not. I'd prefer a clear separation in two fields. Makes clearer that we have two things. And makes the idea of using only valid categories easier to digest. Urs Uns Liska wrote (I guess this might mean moving the files first and then working on the tags?) Yes, that would mean that. Maybe we can have a compromise. A script parsing the content of the tags field from all files shouldn't be hard to write. So we could: - agree upon an initial set of categories - agree upon a naming convention for tags (e.g. the same dashed-lowercase-scheme as for filenames). - reconsider the metadata structure (which fields are mandatory, which optional, default values?) - move all files in one go (that is: one commit for each snippet, as the files are not only moved but also renamed) - clean up and tag the snippets. One by one and using pull request. (I think this should be done _with_ review and not be left to the authors' discretion) Sounds fine to me. -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/openlilylib-Discuss-restructuring-tp163922p164121.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond meeting 2014?
On 7. Juli 2014 17:19:50 MESZ, David Kastrup d...@gnu.org wrote: Urs Liska u...@openlilylib.org writes: On 7. Juli 2014 16:24:34 MESZ, Janek Warchoł janek.lilyp...@gmail.com wrote: Hi all, It's been almost two years since the Waltrop 2012 LilyPond Meeting, in which i had the pleasure to participate. What about organizing another meeting this year? - who'd be interested? - where? (David, are you interested in being the host again?) - when? (i suggest 15-17 August) If the meeting will take place within 1500 km from Warsaw (e.g. at Waltrop) and there will be at least 4 other participants, count me in :) I'll be definitely unavailable Aug 10-24. This doesn't mean that other dates would work, but that's what I can say right now. The Waltroper Parkfest URL:http://www.waltroper-parkfest.de runs from August 29th to August 31st. It is an excellent diversion for accompanying guests and participants, though no participants actually were inclined to go there in 2012. For German-speaking participants, let me quote Das Waltroper Parkfest findet 2014 an den letzten drei Augusttagen statt. Highlights des Ostvest-Kulturspektakels auf vier Bühnen sind Auftritte von Juli, Hennes Bender, Brings und Too Strong, sowie eine gemeinsame Show der NDW-Stars Markus, Geier Sturzflug, Hubert Kah und Fräulein Menke. Putting the meeting in parallel with the Parkfest in a similar manner as last time would place it on August 28th to September 2nd, with the start and end days mostly being for arrival and departure. That woukd make it considerably more likely for me. I even know that I could park my kids in that period. The disadvantage is that the availability of external accommodation may be strained during the Parkfest so one should book soon enough if that is desired. Camping on our premises is possible, and we can accommodate a number of people in the house, particularly if they have sleeping bags of their own. Apart from that I have an idea about a beautiful and appropriate location in Stuttgart I could ask for. I don't know about appropriate but the surroundings here _are_ rather scenic. Judging from the last meeting, nobody can bother with going outside anyway as long as the Internet is up. And we've more than doubled our bandwidth as compared to last time when it was at 1Mbps. I'm not going to push my sugestion (as I don't even know if it would actually be available). It was meant as a response to Janek's question *if* you'd be ready. Urs This year's bird sightings on the premises include cuckoos, great tits, white wagtails, green woodpeckers, black redstarts, barn swallows, spotted flycatchers, magpies, yellowhammers, buzzards and a number of others. If there is sufficient interest, I'd be quite willing to host another meeting. Waltrop is north of Dortmund in the Ruhr area. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond meeting 2014?
2014-07-07 16:24 GMT+02:00 Janek Warchoł janek.lilyp...@gmail.com: Hi all, It's been almost two years since the Waltrop 2012 LilyPond Meeting, in which i had the pleasure to participate. What about organizing another meeting this year? - who'd be interested? - where? (David, are you interested in being the host again?) - when? (i suggest 15-17 August) If the meeting will take place within 1500 km from Warsaw (e.g. at Waltrop) and there will be at least 4 other participants, count me in :) best, Janek Count me in, too. Depends on the exact dates, though. Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
