Re: BendSpanner-engraver

[Marc Hohl]

Hi Harm,

Am 14.09.2016 um 23:00 schrieb Thomas Morley:
[...]
> In general I'd vote for those shortcuts, but to fall back to the
> basic commands if needed.

I had some time to re-think my basic approach ... maybe you are right
and I think way too complicated in terms of taking each string into
account. Working with different TabVoices is probably easier in most cases.

> > Some years ago I had long discussions on the devel list concerning
> > the implementation of a string-bend-engraver (that would have had
> > to be done in C++ at this time), especially with Carl Sorensen, and
> > we came to the conclusion that a bend event is something that
> > happens *to a certain string*, therefore it is possible to bend a
> > string, keep it bent, bend another one, release it and then release
> > the first bent string again.
> >
> > This is rather complicated stuff, but some guitarists do stuff of
> > this kind ;-)
>
> I partly disagree, you can bend a single string or an EventChord
> (speaking lilypondish), meaning all strings are bended starting at
> the same musical moment ending at another but same musical moment for
> all strings. This is supported already.

Ok, this was probably a misunderstanding: I can either bend one string
or many strings at once, but you can manipulate the strings
independently ... as you proved with your concept of using distinct
TabVoices, this works already.

[...]

> So I may be wrong, scans of printed TabStaffs would help me a lot.

still searching ... ;-)

> Additionally, I'm not sure, whether we _should_ make every style
> available, though. My limited inside lets me think every tab-editor
> creates his own style ad hoc and on the fly...

Well, my concerns were not about styles, but about usability.
You convinced me that going for different TabVoices is the way to go!

[...]

> The result: they never bothered to learn reading notes. :((

Yes, that's true.

> Ofcourse you know, tabs _do_have disadvantages: choosing other
> strings for fingerings require a _new_ tab , polyphonics are always
> difficult to print. To mention the most prominent ones...

Therefore I go for a combination of normal Staves and TabStaff, and I am
responsible for the current behaviour of the TabStaff: numbers only, no
stems and stuff ;-)


Cheers,

Marc