gHowl comes with an XML parser so you might give that one a try. The workflow would be:
1. Stream your panel contents (out of the Twitter component) to a file location.
2. Supply file path to the gHowl XML parser.
The data should be much more usable after that.
I am working a more elegant way of dealing with web-based XML feeds in the next release. The twitter component is still in its infancy... more proof-of-concept at this point.
There is a new version available which includes a new Twitter component. Outputs provide parsed results in addition to the XML. head over to the wiki to get the latest...
Nathan Miller
The result is in XML.
gHowl comes with an XML parser so you might give that one a try. The workflow would be:
1. Stream your panel contents (out of the Twitter component) to a file location.
2. Supply file path to the gHowl XML parser.
The data should be much more usable after that.
I am working a more elegant way of dealing with web-based XML feeds in the next release. The twitter component is still in its infancy... more proof-of-concept at this point.
-Nathan
Oct 24, 2011
Nathan Miller
Philipp,
There is a new version available which includes a new Twitter component. Outputs provide parsed results in addition to the XML. head over to the wiki to get the latest...
-Nathan
Dec 10, 2011
Ángel Linares
I've been playing a little bit with this component and the spanish premium risk index...15 tweets limit from Twitter Search API sucks...:(
Jun 20, 2012