I've investigated the usage of chapters and I think they're great, probably what I've been looking for all along. They do a decent job of creating views, however they have a few limitations that could probably be fixed and make them a great alternative to clones:
- They have the same limitation as hoists when switching between nodes. When I try to switch back to a clone that is in a chapter when I've been looking at that clone in a chapter view then I can't get back to my chapter view. - As you've said allow any node to be a chapter without the @chapter directive. Remove the need for a top level @chapters node. - A Chapter-clone-marked-to would be a nice. - By default when I come back to the main view from a chapter it appears to randomly collapse chapters. From a user expectation perspective the expand/collapse state of the outline should not change by default (for clones/hoists/chapters/etc), if collapse behavior is desired it can be enabled through settings. There is no option in the global chapter settings to change collapse behavior. I see the first point as the most important change to be made if hoists or chapters are going to be useful for views. Anyway... I'll stop harking about views. On Thursday, March 3, 2016 at 5:07:39 PM UTC-5, john lunzer wrote: > > > > On Thursday, March 3, 2016 at 4:45:16 PM UTC-5, Edward K. Ream wrote: >> >> >> On Thu, Mar 3, 2016 at 2:42 PM, john lunzer <[email protected]> wrote: >> >>> >>> I do not think auto collapsing the tree should be default, it can be >>> disorienting and can destroy a workflow. >>> >> >> Not sure what tree you are talking about now. >> > > The outline (tree pane). It doesn't seem like a good idea to auto collapse > all the nodes in the outline by default after a cfa/cff/cfm/cffm, > destroying the visual state of the outline. As you would say, that behavior > is automagic (unexpected). This should be an option that should have to be > turned on, but be off by default. It would be no different than auto > hoisting the root of the cloned nodes after a cfa/cff/cfm/cffm, which I > think creates even greater focus without destroying the state of the > outline. And would like to see that as an option too after a > cfa/cff/cfm/cffm. > > Additionally would there be a barrier to remembering if a clone is inside > a hoisted node or not so that when you switched between a clone inside a > hoist to a clone outside a hoist it would return to the hoisted view when > you switched back again? > > >> >> This is pretty much what chapters *should* do. At present there is a >> completely brain-dead restriction that chapters must be children of an >> @chapters node. And we probably don't need @chapter nodes either: *any *node >> should be able to be the "base" of a chapter. >> >> > I have never investigated chapters, I shall do so and see if they help. If > there are restrictions on them that you think inhibit their usefulness then > those should probably be removed. > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
