Comments on: MythStatusScreenlet

By: MythStatusScreenlet 0.1.1 released (theme support) « Net Wolf’s Blog

MythStatusScreenlet 0.1.1 released (theme support) « Net Wolf’s Blog — Thu, 15 Jan 2009 10:29:20 +0000

[...] MythStatusScreenlet [...]

By: netwolfuk

netwolfuk — Wed, 23 Jul 2008 14:12:43 +0000

Hi Matt, I just downloaded it from Gnome Look, and it is 0.0.3, and there is a VERSION-0.0.3 file inside the tgz.
However, I did notice that in the actual code is still says 0.0.2, so will fix that when I get my dev machine back up and running (although it shouldn’t really matter).
I’ll find somewhere else to host it if you find that you’re getting an old version from Gnome Look.

By: Matt

Matt — Wed, 23 Jul 2008 11:39:51 +0000

It appears 0.0.2 is still only available from gnome-look.org website.

Have you got another URL to grab this from?

I’m running Hardy and 0.0.2 is pretty useless.

By: MythStatusScreenlet 0.0.3 released (Hardy support) « Net Wolf’s Blog

MythStatusScreenlet 0.0.3 released (Hardy support) « Net Wolf’s Blog — Sun, 11 May 2008 16:09:50 +0000

[...] MythStatusScreenlet [...]

By: netwolfuk

netwolfuk — Sun, 11 May 2008 16:02:22 +0000

I pretty much gave up on xpath/ElementTree, and have written the XML parsing using simple regular expressions. I’ve done a little bit of testing, and it seems to work in a Hardy virtual machine.

By: netwolfuk

netwolfuk — Mon, 28 Apr 2008 23:06:23 +0000

@Justin, thanks for your interest. It would appear the other implementations of xpath are much more complicated than the simple one that worked in Gutsy. I was looking at ElementTree, but had come up against a wall. Any suggestions welcomed.

@Sune, thanks for your suggestion. I made your changes, but XPath from Ft behaves quite differently from xml.xpath. Try running screenlets-manager from an xterm to see all that’s going on. I do think it’s a python/xml problem, rather than a mythtv XML format change (I’m still running 0.20 on my backend).

Again, any more suggestions very much welcomed.

By: Sune Mølgaard

Sune Mølgaard — Mon, 28 Apr 2008 21:51:56 +0000

Replace

from xml import xpath
with
from Ft.Xml import XPath

Replace all other appearances of
xpath
with
XPath

I think that’s all I did, but will check back if it doesn’t work. However, I now get a completely blank mythstatus screenlet except for the first short while. Might be some further updates in mythtv at work in that respect…

Best regards and all

By: Justin

Justin — Mon, 28 Apr 2008 14:35:20 +0000

Any progress on xpath so far?

By: netwolfuk

netwolfuk — Thu, 10 Apr 2008 10:22:33 +0000

Hi Mr Plow, I’ve now have a Hardy VMware image installed (I am running Gutsy), so will try and look at it this weekend.

From the limited time I spent on it last night, I see that the python-xml in Hardy installs into some “old” dir. I had a quick play around with PYTHONPATH, but had no luck. I suspect I might have to change to one of the newer xpath implementations.

By: mrplow

mrplow — Sat, 05 Apr 2008 01:21:23 +0000

doh, guess Ubuntu Hardy is messing this up
mrplow@mrplow-desktop:~$ sudo apt-get install python-xml Reading package lists... Done Building dependency tree Reading state information... Done python-xml is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 30 not upgraded. mrplow@mrplow-desktop:~$ python Python 2.5.2 (r252:60911, Mar 12 2008, 13:36:25) [GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu4)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from xml import xpath Traceback (most recent call last): File "", line 1, in ImportError: cannot import name xpath >>>