> I do this by using leo hooks.  When a check box is clicked or text
> typed a hook is called to notify of a change, the controller will
> respond by calling another hook with the new current state of the save
> flags/text, widgets register with this hook if they want to track
> changes.

Like Ville, I'm not following this in detail.  However, this comment
reminds me that Leo's find tab isn't fully hooked up yet.   Thanks for
this reminder :-)

> This allows complete decoupling of the gui from the core.  It does not
> matter even if a gui exists or not.

Leo's core and gui code must often communicate.  At present, Leo's
core never knows which gui it is talking to.  In this sense, Leo's
core is already fully "decoupled" from the gui plugins.  This is what
I mean when I say that Leo's core is "gui-independent".

> I think this is a good model to use for this type of interface.

Yes.  I've lost track of how many guis I've written for Leo. As Leo
has evolved, the dependencies on the gui in Leo's core have been
reduced to an absolute minimum.  At present, the only gui-specific
code in Leo's code is code to put up emergency dialogs that inform the
user that the gui plugin can't be loaded, or that the proper version
of Python can't be found.

> I have attempted to hook this into the leo core, but I am having a
> little trouble sorting it out at the moment. The text widgets in the
> leo find pane seem to work well enough, but not the checkboxes.(I
> haven't wrapped the text widgets yet but that should be easy enough).

The text widgets in the find pane are not known to Leo's core.  The
interface is a bit tricky, but I'll deal with that.

> If you think this approach is worthwhile I will finish it off and also
> do a spell check panel.

It would be quite helpful if you used QDesigner to put the standard
Spell-tab widgets into the Spell tab.  Don't worry about how to hook
up those widgets.  That's my job.

> I have abandoned my tree efforts

A wise decision.  The tree widget code in the qt plugin is well beyond
the demo stage.  The last code will be a significant optimization, as
discussed in another thread.

Edward

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to