[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [FR-devel] Source Browser [was Editor API?]
From: |
Philipp Meier |
Subject: |
Re: [FR-devel] Source Browser [was Editor API?] |
Date: |
Fri, 6 Sep 2002 12:48:23 +0200 |
User-agent: |
Mutt/1.4i |
On Thu, Sep 05, 2002 at 10:55:55AM -0700, Curt Hibbs wrote:
> Laurent Julliard wrote:
> >
> > > It may be possible to synchronize the source with
> > > the source browser automatically. But, to achieve this,
> > > the Editor pane creation event and the Editor pane change event
> > > must be hooked. I hope Editor API discussion solves this problem.
> > >
> >
> > THis is a good example of what the Editor API could bring. Which
> > probably means enhancing the EditPane plugin to allow another plugin
> > to listen an a subslot of the EditPane slot where events are posted.
> > However I'm not sure this is really appropriate to trigger the source
> > browser update each time a new character is typed. May be the simple
> > mechanism I explained above is enough in practice.
>
> A Possible Design Idea...
>
> In my Java version of the databus, the way I have done this sort of thing is
> have a listener-filter that listens to the high-frequency/low-level events
> on a slot, performs some sort of analysis (normally using a state-machine),
> and then posts some appropriate low-frequency/higher-level events to a
> different slot. Listeners on this alternate slot then perform the
> appropriate actions when they are notified.
The filter criteria could be the idle time (2 sec or like that) after typing the
last character. This is how many editors work.
-billy.
--
Meisterbohne Söflinger Straße 100 Tel: +49-731-399 499-0
eLösungen 89077 Ulm Fax: +49-731-399 499-9
pgp_3vTP69uqg.pgp
Description: PGP signature