I wrote a complete menu (including scrolling chapter menu with rotating images) in pure markup. The XMU file has in total about 1500 lines. Unfortunately I notice that it runs quite slow on HDiSim and in Players.
Are 1500 lines too much for xmu
Markup Performance
Hot Topic
- Saving stream settings
- Problem with 'content ID' while creating directory in 'persistent storage'.
- Problems with XBOX 360 HD DVD Player
- Additional requirements for a WMP plugin on Vista 64?
- Force user to the Settings UI window
- An interesting survey: HD-DVD vs. Blu-Ray
- MFT help
- How to jump to a new title and a specific chapter in that title?
- About MFT_MESSAGE_SET_D3D_MANAGER.
- OT: Suggestions about gallery.live.com
Audio and Video
- New to Scenarist HD Advanced Authoring...
- How can I hide picture in DIV?
- More complex samples from Microsoft, any ETA?
- z-index with <object> and <g:background>
- Custom Effects with Movie Maker 2
- Gadget behavior on spaces vs live.com?
- still DXVA questions
- Flash movies
- Extending Classes in HDi - not working in Emulator
- Function to edit html code of a webpage
Markup Performance
Musafir
Fyrus
1500 lines should be OK, some released titles have more than twice.
Although, performance may vary depending on content.
Reese Bird
Vijay Guru Prasadh
It will depend on how complex your XPath queries are, how complicated the layout is, etc.
"Number-of-lines" is never a good metric for gauging the complexity of something... especially since you could put it all 1500 lines on a single line :-)
If you have real perf concerns, you can send me the page (and any other assets it needs to run) and I can take a look... no promises of amazing perf savings though; some things are just better done by script (or by breaking your content out into multiple pages).
Scott Boyd
Can you please elaborate why the above improves performance.
In my understanding , both options as presented should have same performance.
thanks
AlfonsAberg
Also, the load time increases exponentially with the addition of divs at the top level of your body and cues in your timing blocks.
ie,
<par>
<cue/>
<cue/>
<cue/>
</par>
<par>
<cue/>
<cue/>
<cue/>
</par>
<par>
<cue/>
<cue/>
<cue/>
</par>
<par>
<cue/>
<cue/>
<cue/>
</par>
is better than...
<par>
<cue/>
<cue/>
<cue/>
<cue/>
<cue/>
<cue/>
<cue/>
<cue/>
<cue/>
<cue/>
<cue/>
<cue/>
</par>
and
<body>
<div style:position="absolute" style:x="0px" style:y="0px" style:height="1080px" style:width="1920px">
<div/>
<div/>
<div/>
<div/>
</div>
<div style:position="absolute" style:x="0px" style:y="0px" style:height="1080px" style:width="1920px">
<div/>
<div/>
<div/>
<div/>
</div>
<div style:position="absolute" style:x="0px" style:y="0px" style:height="1080px" style:width="1920px">
<div/>
<div/>
<div/>
<div/>
</div>
</body>
is better than
<body>
<div/>
<div/>
<div/>
<div/>
<div/>
<div/>
<div/>
<div/>
<div/>
<div/>
<div/>
<div/>
<div/>
<div/>
<div/>
</body>
Michael J Brown
Meanwhile I found the reason for my markup being so slow.
Wasn't the 1500 lines. It were just two little <style select="//button" ...> statements ;-)
I fixed it and now it looks very fluent and nice.