@ chunk1982...If you want to learn more there are some things you could do to understand the structure of xbmc xml code. A couple of things that are hard to grasp at first are:
- includes
- animations
- conditional visibility
- default.xml (if you have a <control> and it's going to be the same over and over again, whatever you leave out will be taken from this file)
I would first start by taking MyVideo.xml (from confluence lite since you're already somewhat acclimated), and replace all of the includes in that file. Take your time and make sure that you are accurate as to not ruin the file, and use some sort of comment structure that YOU can understand. For instance...
<include>BehindDialogFadeOut</include>
becomes much easier to understand as:
Code: Select all
<!--"BehindDialogFadeOut"-->
<control type="image">
<posx>0</posx>
<posy>0</posy>
<width>1280</width>
<height>720</height>
<texture>black-back.png</texture>
<animation effect="fade" time="400">Visible</animation>
<animation effect="fade" time="200">Hidden</animation>
<visible>Window.IsActive(MovieInformation) | Window.IsActive(MusicInformation) | Window.IsActive(SongInformation) | Window.IsActive(FileBrowser) | Window.IsActive(TextViewer) | Window.IsActive(ContentSettings) | Window.IsActive(SelectDialog) | Window.IsActive(FileStackingDialog) | Window.IsActive(MediaSource) | Window.IsActive(PictureInfo) | Window.IsActive(PlayerControls) | Window.IsActive(VirtualKeyboard) | Window.IsActive(NumericInput) | Window.IsActive(ProfileSettings) | Window.IsActive(LockSettings) | Window.IsActive(SmartPlaylistEditor) | Window.IsActive(SmartPlaylistRule) | Window.IsActive(script-RSS_Editor-rssEditor.xml) | Window.IsActive(script-RSS_Editor-setEditor.xml) | Window.IsActive(script-Apple_Movie_Trailers-settings.xml) | Window.IsActive(script-Apple_Movie_Trailers-chooser.xml) | Window.IsActive(script-Apple_Movie_Trailers-search.xml) | Window.IsActive(script-Apple_Movie_Trailers-showtimes.xml) | Window.IsActive(script-XBMC_Lyrics-main.xml) | Window.IsActive(script-XBMC_Lyrics-settings.xml)</visible>
</control>
<!--"BehindDialogFadeOut"-->
Once the page is laid out in code instead of includes you can see it for what it is instead of flipping back and forth between MyVideo.xml and includes.xml.
If you take the time to do an exercise like this (making sure that all of your tags are closed and that your columns are in order), you will begin to understand the way the controls are laid out, the way that the page is set up when you see it on the screen, and how everything works together. It's not exactly thrilling, but it will help you to understand the manner in which xbmc utilizes .xml and give you some insight at the same time.