[mythtv] Extending mythnotification UDP interface?

Jean-Yves Avenard jyavenard at gmail.com
Wed Jul 3 12:22:12 UTC 2013

On 3 July 2013 22:09, warpme <warpme at o2.pl> wrote:

> Jya,
> Big thx for notify extension. It is cool thing.
> So cool that I want to use it for following, additional cases:
> notification-new-mail
> notification-disk-attached
> notification-disk-detached
> notification-disk-full
> notification-cpu-overheat
> notification-incomming-call-start
> notification-incomming-call-end
> notification-outgoing-call-start
> notification-outgoing-call-end
> notification-archive-disk-connected
> notification-archive-disk-disconnected
> Names should be self-explanatory.
> I know 0.27 is in features freeze.
> For approaching above with minimal effort, I think 2 phases might be worth
> to consider:
> Short-term: add to UDP interface possibility to provide all fields
> (coverart,album,artist,time,info,progress). Only in UDP. mythutil can stay
> like today.

I'll look into it.

the telnet interface has already been extended

> Long-term: add to notification-ui.xml window definitions/translations for
> above.

I don't see how any of what you listed require extending the current theme
schema... everything can be done already.

Forget the name of the field such a author, etc... it's just a placement

> Only real functional difference between short-term and long-term is
> possibility to define particular(per notification type) widow size/layout
> in long-term solution. Not big deal remembering that short-term ext.app.
> can already feed type-relevant dedicated icon/picture using UDP interface.
to me a notification has to stay small and non-intrusive...
though, we could easily amend the MythNotification structure to allow to
specify your own theme to load and go from there.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-dev/attachments/20130703/e4663b3d/attachment.html>

More information about the mythtv-dev mailing list