[mythtv] API Framework has been committed (May break existing users of mythXML).

Wes Brown thewbman at gmail.com
Tue Mar 22 22:46:28 UTC 2011


I think this is a great idea.  Works great on my machine.  I am not
an actual MythTV developer so I don't have any say on this becoming
official, but I do want to show my support.  Writing my app for Palm webOS (
http://code.google.com/p/webmyth/) I ended up writing a small python script
to get access to a lot of MythTV features.  I have since added native
support for the app to communicate the actual mythprotocol on the device
(and do more complicated MySQL and remote operations).  So to use the full
app remotely the user has to forward ports 80, 3306, 6543, 6544 and 6546.
 Cutting out 6544 for XML would be nice both to reduce the number of ports
and to allow usage through a proxy that blocks all ports besides 80.  (My
app would still require the other ports for full functionality, but the
majority of things could be done through XML).

[Somewhat off-topic, but adding the list of upcoming recordings to MythXML
would be great.  I am not sure if it is deliberately not part of MythXML or
just nobody has decided to do it themselves.  Being able to show upcoming
recordings I think is key to a good MythTV app and having an XML interface
for it would simplify that for any apps on any platform.]

 - wes

On Mon, Mar 21, 2011 at 9:44 PM, David Whyte <david.whyte at gmail.com> wrote:

> On Thu, Mar 10, 2011 at 2:26 AM, David Blain <MythTv at theblains.net> wrote:
> > For those not following IRC, I committed the API Framework last night.
> >
> >
> Hi David,
> Congrats on the great work.  I have been working a little on the
> ability to expose MythXML to the external world via a MythWeb module.
> My goal was to be able to write an app for my android phone, that
> could access mythTV data via my mythweb server and not have to forward
> more ports etc on my router or have to interpret the mythTV protocol
> within the app.  A stretch goal was to produce something that could
> eventually be included in mythTV so that others could use the same
> app, but against their mythTV installation or develop their own app
> maybe on different platforms too.
> A write up and downloadable version of the module is at
> https://sites.google.com/a/thewhytehouse.org/mythtv/modification/mythxmlmoduleformythweb
> Obviously, the module I have developed will have to change a little,
> but I just wanted some feedback on whether what I was doing was
> redundant/unwanted.  I am also unsure of how to get it before the
> developers eyes.  Should I just raise a ticket as it is, with the
> couple of minor problems it has (i.e. no mythweb translation etc) or
> does it need to be fully finished and polished before it gets there?
> Any feedback is welcome...
> Regards,
> Whytey
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.mythtv.org/pipermail/mythtv-dev/attachments/20110322/a2d80abb/attachment.html 

More information about the mythtv-dev mailing list