Pavel Sanda wrote: > Jean-Marc Lasgouttes wrote: > >>>> One idea would be to allow every Flex inset to be a branch inset, in the > >>>> sense that it would appear in the branch menu and could be turned on > >>>> and off. > > > > I would really prefer to avoid this. I think we have to keep some semantics > > to our object and avoid the "let's everything be possible" syndrom. > > You would like to avoid this only at the UI level or at the coding level?
JMarc, do you have opinion about this? P > If I understand correctly the two possibilities are: > 1) > Style My_Purple_FootNoteB > Branch Allow 1 //-> branch My_Purple_FootNoteB appears in branches > .. > End > > 2) > Style Branch::Purple_FootNote //if style found branch automatically obtains > TeX wrapping > TeXBefore > TeXAfter > End > > I'm fine with anything which allows me to create branches like "green-text > emphasized" > or "blue-footnotes" without need to embed such constructs into each of branch > insets > and both of the proposals seems to provide this. I'm not expert in the layout > machinery > to see what is more elegant, though 1) looks less work. > If you are concerned about UI level only, we wouldn't define Branch Allow 1 > for our > generic insets... > > > OTOH, it might make sense to merge the concepts of notes and branches. > > People may want to print with and without some notes also. I am not sure > > though what the merged inset would be called. And if you cannot find a good > > name, your concept is not clear enough :) > > If we prefer to keep semantics of our objects than merging branch and note > does > not look like a particularly good idea. At least the original concept of > branch > is not just some note around. It looks rather as insufficient feature list of > notes than that we need to merge both concepts. > > Anyway this topic is not directly related, the merge can happen independently > of particular mechanism we choose above. > > Pavel
