Not logged in. · Lost password · Register
Forum: Features request RSS
Xml Would Be Amazing...
Page:  previous  1  2 
genekeenan #16
Member since Mar 2003 · 18 posts
Group memberships: Members
Show profile · Link to this post
yah, your proof works fine.

it will be really great to have this all in xml and it will be nice to be able to control the formatting of the xml. Flash really hates white space tho it won't be such a problem in a closed environment such as a home network.

very exciting

gk
Keefy #17
Member since Mar 2003 · 89 posts
Group memberships: Members
Show profile · Link to this post
OK, it seems I've got pretty much everything working already. Almost too easy, I'm thinking I've missed something.  ;)

The attached zip contains a simulation of the XML interface. Load up "index.html" to get going. This page requests two XML files from BrowseAmp. To simplify things (and because BrowseAmp doesn't process XML in the same way as HTML yet), I've represented the files it would return in the "Simulation" directory. See my post in the Main forum in the beta discussion to see how BrowseAmp can generate these. Normally these values would point to the BrowseAmp server, e.g. "http://myHost/CurrentTrack.xml". Hopefully I'll be able to parameterise the server name and port, maybe storing it in a cookie or something.

Note that the same XSL file is used for both of the transforms. This is not required, you could have multiple files if you wanted. I've chosen to have one for the time being, this should simplify things. The "for-each" elements ensures that only the relevant parts are displayed, e.g. if the input XML doesn't contain a "CurrentTrack" element, then that information is not displayed.

Normally, XML/XSL works the other way around, where you have the same XML file (usually really a database interface) and multiple XSL files to define all the different ways of viewing the data, e.g. "product index", "product detail", that sort of thing. As one of the aims of what I am doing is to reduce cross-host transfers to a minimum, the approach here is different.

The XML format (schema) used in the example is very far from final. I'll probably change the format away from elements:

<item>
    <id>1</id>
    <length>1:01</length>
    <title>First track</title>
</item>

into attributes:

<item id="1" length="1:01" title="First track"/>

as this should bring the byte-count down for the transfers. It makes no difference really, the XSL is only very slightly different for either approach.
The author has attached one file to this post:
BrowseAmp_Client.zip 1.8 kBytes
You have no permission to open this file.
Keefy #18
Member since Mar 2003 · 89 posts
Group memberships: Members
Show profile · Link to this post
First beta of a working skin is available in the Skins forum. Please place any future discussion in that topic.
Close Smaller – Larger + Reply to this post:
Verification code: VeriCode Please enter the word from the image into the text field below. (Type the letters only, lower case is okay.)
Smileys: :-) ;-) :-D :-p :blush: :cool: :rolleyes: :huh: :-/ <_< :-( :'( :#: :scared: 8-( :nuts: :-O
Special characters:
Page:  previous  1  2 
Go to forum
This board is powered by the Unclassified NewsBoard software, 20150713-dev, © 2003-2015 by Yves Goergen
Page created in 170.9 ms (85.8 ms) · 48 database queries in 78.5 ms
Current time: 2018-02-24, 23:36:44 (UTC +00:00)