On Mon, Jan 13, 2014 at 9:26 AM, Edward K. Ream <[email protected]> wrote:
> > A new @headlines node (a child of the @auto-view node for the @auto file) > will contain > ...pairs of lines, much like @clones:: > > unl: <a unl> > head: <the custom headline> > > The unls in the @headlines node must use standard headlines! > There is an interesting coordination problem between the read and write code. If the unl's really do specify standard headlines, then switch the headlines is easy *in the read code*. But then, how is the *write* code going to know what the standard headlines were *before* the switch? Otoh, the the write code writes unl's with the custom headlines, how is the read code going to know how to do the switch? Here is the present plan: 1. The contents of the @headlines node will be pairs of lines: standard: <standard unl, as created by the importer> custom: <unl, with the switched headline> 2. The read code will patch an ivar, say v._standard_headline, of the vnode, giving the standard headline of the vnode, as reported by the importer. The write code will use this field if the body text hasn't changed. Otherwise, the write code will have to call the importer to get the proper updated standard headline. And there is an important complication that has just become apparent. At present, the unl's written to @organizer: nodes use *custom* headlines, not standard headlines. If that remains true, the unl's will have to be converted to standard unl's in the read pass. That can easily be done using the data in the @headlines nodes, but it must, in fact, be done! It may be easier to use standard unl's in @organizer: nodes. That can easily be done as discussed in point 2 above. In short, this whole project is about proper bookkeeping ;-) Edward -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
