Martin Vermeer wrote:

Note that you would have to store "all possible branches" into the doc
header.

Yes.

Feel free to do the necessary extra work :-)

I expected something like this... but I don't want to steal your hobby horse :-)


 <Text field>       <Choice box with options "Disabled", "Margin note",
                     "Plain text", "Footnote">

Russian Plain text
English Disabled
Draft Margin note
__________ ______
__________ ______
... ...



For the explicit branches, you would only want the output options "Disabled" and "Plain text". And that could be handled by radio buttons.

Why this restriction? Maybe someone wants to print explicit branches like "Draft" or "Comments" in the margin. We have all the power to do this, so let's use it.

I see that you want to be able to use "named margin notes" (i.e.
output only in draft mode). How useful is this? Remember you can put a margin note inside a Draft branch inset. They nest.


I don't want to use "named margin notes", I want to use "named branches that are represented as margin notes". Sounds like a purely philosophical discussion but it's a another step to separate logic from representation.

Thanks for your response.

Michael




Reply via email to