Re: component architecture

["John D. Heintz" <jheintz ripple dyn ml org>]

Tom Tromey wrote:
> 
> John> 2) Script X would register interest in the "file changed" event.
> 
> John> 3) When script X got the "file changed" event it would record
> 
> John> this in my log.
> 
> 
> 
> We'll use the CORBA Event Service as the core of the event manager.
> 
> Basically all of our "additions" will be just convention:
> 
> 
> * Conventions for event types.
> 
> * Conventions for event naming
> 
> * Our service will be located at a particular place in the namespace
> 
> 
> 
> Does this make sense?
> 

I think where I am not clear on this picture is that somewhere there
has to be a bit of code that gets executed when the event for file
editing occurs - but where is this code going to be?

Or for the example of adding a menu option to the editor, some Corba
client script must call that exported method on the editor to add 
the menu.  
Does it need to be called every time the editor is started?
Does that client script need to be a daemon running that listens for
editor_start events, and add the menu when it gets one?



> 
> 
> I can expand on what I think an event ought to be, and why, if anybody
> cares.
> 

If you could explain some of the details of how this would work I
would appreciate it.  Perhaps the group is tired of my questions
and personal email would be better??

John