RE: [misterhouse-users] Separate event, time table driven engine

[Bruce W. <br...@mi...>]

> I have been thinking about this also and I think I have a
> solution.  I have
> added new features to the trigger code in Misterhouse.  Each
> trigger now has
> a name associated with it and there are new routines you can call
> from your
> scripts to create, modify, list, and delete them:
...
>     Generates a web interface for managing triggers (not done yet)
>
> I envision a very nice web interface for managing triggers (written by
> someone better at it than I).  It should be able to generate and recognize
> perl code for the most common events (time_now, time_cron,
> state_now $item)
> and actions (set $item, run voice command, &function).
>
> We can also use triggers in common code scripts to allow the user to
> customize when a command like get_weather runs, and, as Robert
> said, all the
> event stuff can be in one place.  Next we need an interface for managing
> items!

I agree, I think we could create a nice web interface for managing trigger
based events.   I'm game to take a look at this this weekend unless someone
else had the itch.

Bruce