On Tue, Jan 24, 2017 at 10:34 AM, 'Terry Brown' via leo-editor < [email protected]> wrote:
> > > ------------------------------ > *From:* Edward K. Ream <[email protected]> > Good marketing. And great work, Terry. Not sure how this will fit in > with the pyzo widgets. Eventually I would like to use pyzo widgets so that > we can have a border for use by the debugger. Hmm. Iirc, pyzo uses > scintilla, so maybe this is part of the migration path. > > If there's a pyzo editing widget, I'd hope that can be used as any other > QScintilla / QTextEdit / LeoTextEdit etc. > I'm sure it can be, eventually. However, the pyzo editing widget is a subclass of about 20 classes, so some repackaging will likely be required. Hmm, I wonder if this new widget could be the wrapper, keybinding wise, for > all the edit components. > You mean *your* new widget? I would guess so. Key-binding aside, it's current essentially working as an editor (albeit > just a simple plain text one). The fiddle bits are getting things like > c.frame.body.wrapper.getSelectedText() etc. to work. Not that it's hard > in itself, just how it all ties together. > Right. 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.
