On Mon, Apr 23, 2018 at 1:46 PM, vitalije <[email protected]> wrote:
> here is a complete code in experimental outline. Superb code. Many thanks for it. > > Perhaps you can do better job regarding the undo/redo functionality. I can't dive into undoer code right now so I have re-implemented everything from scratch. Perhaps Leo's undo code could be rewritten along the same lines. Many years ago the late Bernhard Mulder proposed simplifying the undo code, but I didn't understand how it could be done. > PS: I have just manually tested copying, pasting with/or without retaining clones and undoing/redoing. It's a great prototype. I'll study it carefully. > The pasteFromString variant is missing, but it would be trivial to add. Just skip everything undo/redo related. In general, we don't want to force a major refactoring of code just because some client code wants to tweak existing core code. In this case, however, you have made a strong case for re-imagining everything. We will also need a paste-as-xml command, so that people can paste the xml-version of an outline into an external editor. But there would be no need to read copied xml back into Leo itself. Assuming the prototype can be integrated into Leo, we could consider using json as an alternative format for .leo files. The existing sax-based read code must remain indefinitely, to support Leo's xml-based file format, but the json format might be preferable. Terry, do you have any comments? 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
