Vitalije, On Fri, May 8, 2020 at 7:51 AM vitalije <[email protected]> wrote:
> *What next?* > > The main purpose of this prototype was to prove my claims about how Leo > architecture should change. Which parts should be moved to View, which > should be moved to Model and which should be moved to the Controller. > > The classes and methods that belong to VIew are Position, outline > commands, chapter commands, hoist commands. But how to achieve that. > > Let's imagine an object containing all these methods. Each GUI can create > an object with these methods. QtGUI will return an object much like the > MyGUI from the prototype. The other GUIs can return an object constructed > from the current implementation of these commands in Leo. That way those > other GUIs won't have to change much. > Could you explain more on how that would work? The outline commands, for example, currently live as methods on c. But with your new code they would be available at c.guiapi.xxx. The code which currently calls these outline commands (minibuffer commands and keystroke callbacks?) would be changed to instead call these c.guiapi.xxx methods? And the wrapper objects on the other GUIs would make calls to the old methods on c so their old behavior is retained? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAO5X8CwxA7PBS-Z6eNkmQuDvnYXRX%3DrJ%3D2LUgLd4qSbsObMCxg%40mail.gmail.com.
