Re: GSoC update; Q's about final/draft modes, and triggering footnotes

2016-07-07 Thread Jeffery Shivers
Absolutely - in fact, using the presence of offset to indicate *I'm a footnote* was just a practical solution since I am sure some projects won't *always* want annotations to become footnotes, and with this check wouldn't need to specify explicitly *when* and *when not*. However, maybe it would

Re: GSoC update; Q's about final/draft modes, and triggering footnotes

2016-07-05 Thread Simon Albrecht
On 05.07.2016 03:31, Jeffery Shivers wrote: Since offset is presumably always going to be used for footnotes, I think *that* should be what triggers the footnote. So, inclusion of `offset = #'(...)` will tell scholarLY that the annotation is a footnote; otherwise it *isn't*. If it's preferred

Re: GSoC update; Q's about final/draft modes, and triggering footnotes

2016-07-05 Thread Jeffery Shivers
​This footnote feature is now up-and-running, for those who are interested. https://github.com/openlilylib/scholarly/tree/footnotes-feature There is an example doc also: usage-examples​/footnote-trigger-test.ly -j On Mon, Jul 4, 2016 at 9:31 PM, Jeffery Shivers

Re: GSoC update; Q's about final/draft modes, and triggering footnotes

2016-07-04 Thread Jeffery Shivers
Now offset and footnote (text) can be set in the properties list. `footnote = "text"` can be explicitly set and used for the footnote text, or, if not set, `message = "text"` is assumed to be the footnote text, if made into a footnote at all. \criticalRemark \with { message = "my

Re: GSoC update; Q's about final/draft modes, and triggering footnotes

2016-07-03 Thread Urs Liska
Am 03.07.2016 um 14:48 schrieb Simon Albrecht: > On 03.07.2016 03:34, Jeffery Shivers wrote: >> I'd appreciate any thoughts on the following syntax for implementing >> footnotes with annotations: >> >> \criticalRemark \with { >> message = "my annotation" >> } #'(1 . 2) "my footnote" Slur

Re: GSoC update; Q's about final/draft modes, and triggering footnotes

2016-07-03 Thread Simon Albrecht
On 03.07.2016 03:34, Jeffery Shivers wrote: I'd appreciate any thoughts on the following syntax for implementing footnotes with annotations: \criticalRemark \with { message = "my annotation" } #'(1 . 2) "my footnote" Slur a4_\the-footnote-hook ( ... vs. \criticalRemark \with {

Re: GSoC update; Q's about final/draft modes, and triggering footnotes

2016-07-02 Thread Jeffery Shivers
> > For greater flexibility, would it be feasible to allow users to create and > name any number of their own modes (rather than having two "hard-coded")? > ​ > Just to put my two cents in, I ​had thought about that as well and almost suggested it in the OP. If a single project could employ

Re: GSoC update; Q's about final/draft modes, and triggering footnotes

2016-07-02 Thread Jeffery Shivers
I'd appreciate any thoughts on the following syntax for implementing footnotes with annotations: \criticalRemark \with { message = "my annotation" } #'(1 . 2) "my footnote" Slur a4_\the-footnote-hook ( ... vs. \criticalRemark \with { message = "my annotation" footnote-offset = '(1 .

Re: GSoC update; Q's about final/draft modes, and triggering footnotes

2016-06-29 Thread Paul
On 06/29/2016 10:03 AM, Urs Liska wrote: Implementation-wise it is basically nothing to add another mode by simply allowing additional values for the "mode" option. Packages can also quite easily implement that by extending the conditionals in their functions to respond to more than two modes.

Re: GSoC update; Q's about final/draft modes, and triggering footnotes

2016-06-29 Thread Jeffery Shivers
> > Both lilypond and LaTeX have steep learning curves ​ One of the conditions of the package ​, in my mind,​ is to make ​its ​ usage possible at ​the ​highest​ ​ level, but configurable at the lowest. ​LaTeX is such a powerful utility, and in this case should really extend our workflows (and

Re: GSoC update; Q's about final/draft modes, and triggering footnotes

2016-06-29 Thread Urs Liska
Am 29.06.2016 um 15:12 schrieb Paul: > Hi Jeffrey, > > It's good to hear about your progress! Just a thought about modes... > > On 06/27/2016 07:50 PM, Jeffery Shivers wrote: >> ***Final/"draft" Modes*** >> OpenLilyLib will ideally be used in final/draft/etc. modes in order to >> toggle between

Re: GSoC update; Q's about final/draft modes, and triggering footnotes

2016-06-29 Thread Paul
Hi Jeffrey, It's good to hear about your progress! Just a thought about modes... On 06/27/2016 07:50 PM, Jeffery Shivers wrote: ***Final/"draft" Modes*** OpenLilyLib will ideally be used in final/draft/etc. modes in order to toggle between fancy/plain settings, or really whatever the user

Re: GSoC update; Q's about final/draft modes, and triggering footnotes

2016-06-29 Thread Graham King
On Mon, 2016-06-27 at 19:50 -0400, Jeffery Shivers wrote: > Hi fellow LP users, > > Firstly, thanks to Urs for all his guidance in the project so far. The > LaTeX package for scholarLY is inching forward still, and hopefully I > will share an initial version after a few more kinks have been

GSoC update; Q's about final/draft modes, and triggering footnotes

2016-06-27 Thread Jeffery Shivers
Hi fellow LP users, Firstly, thanks to Urs for all his guidance in the project so far. The LaTeX package for scholarLY is inching forward still, and hopefully I will share an initial version after a few more kinks have been worked out with a couple of the features. I'll have more substantial