Hi. A little while ago I found myself wishing that diald worked a little differently. I envisioned diald as a programming object and has its own event loop and responds to those events with specific handlers. So, there'd be a start-up event, which is handled by start-up code, and a chat-finished event that would start the chat-finished event handler, and a filter-matched event that would call the filter-matched code and so-on. Of course, there would have to be some sort of simple inheritance involved. By that I mean that I want the ability to extend and/or replace the default event handlers, with say, scripts pointed to by the config file. After a little while it occurred to me that diald might already do this, to some extent, even though it is not at all clear from the documentation. Does anyone know how closely diald matches my description? If it does match, does anyone know if there some documentation available that makes this clear? If it doesn't match, what do you think of my idea? Thanks. - Ben - To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
