Displaying other XML elements in Ticker

Asked by Adrian

It would be very nice if Xibo were able to take anything in a Ticker feed that was in [] and try to match that with XML elements, i.e. not Title, Date, Description, but anything that is in [ ], e.g. [Author]. Can this be made into a feature?

I'm digging around trying to find the code that parses the xml of an rss feed, but failing to find that particular source file... :-(

Question information

Language:
English Edit question
Status:
Solved
For:
Xibo Edit question
Assignee:
No assignee Edit question
Solved by:
Adrian
Solved:
Last query:
Last reply:
Revision history for this message
Adrian (taylor-adrian) said :
#1

Guess it's in the client?

Revision history for this message
stef (stephane-quimpere) said :
#2

Since you already have a php server for xibo, you could make a php page that parses it and you can then parse and get what you want.

Google PHP and simplexml, this page : http://www.ibm.com/developerworks/library/x-simplexml.html

and a few other similar pages helped me a lot with that.

Revision history for this message
Alex Harrington (alexharrington) said :
#3

Adrian

Best place to log feature requests is in the Blueprints section. https://blueprints.launchpad.net/xibo

Pop over there, have a look through and see if something similar has been suggested before (and subscribe to it for progress updates if it has), or log a new blueprint with as much information as you can about how you think the feature should work.

We periodically scan through them all when working on the project roadmap and pull in ideas as we go.

If you could mark this question solved, and post a link to the blueprint in here that would be very helpful.

Cheers

Alex

Revision history for this message
Dan Garner (dangarner) said :
#4

Adrian,

If you file a blueprint for it (and link it back here) I will add some details to it showing the relevant parts of the client code. Otherwise Stef's workaround is a good one.

Cheers,
Dan

Revision history for this message
Adrian (taylor-adrian) said :
#5

Thanks for all the responses. I will file a blueprint. In the meantime, I've worked around it with judicious use of sed :-)