(a Movie-Player for PalmOS)
You`ll here find a Skin for the MMPlayer.
Download the PDB-File (236 KB). This is what you need.
Download the XML-File (241 KB). If you`re curious.
The Skin supports screens with 320x320 and 320x480 pixel resolution, landscape and portrait-mode. Take a look at the screenshots below, they were taken on a T5 with 320x480 pixel resolution in landscape-mode. My main aim was to keep it as original as possible.
Some hints:
- to get to the Prefs, tap on the small fake-equalizer on the right of the Timeline, same to leave the prefs
- to switch the Equalizer ON/OFF, tap the Rebel-Alliance-Symbol in the lower left edge
- to get to the Playlist, tap the playlist-Button =)
- to close the Playlist, tap the red aquabutton in the top left corner (Mac OS X style to "close" a window)
Because of some limitations in the MMPlayer-skinsupport, I had to fake the time-display. It will stay at 00:00, it`s only there to give the skin an authentic look.
If you find bugs or have any comments, post them in the MMPlayer Skins-Forum.
Other Infos:
All Graphics were remade (no screenshots) using The GIMP. The Waveform, Playlist and the Prefs are not available in the original QuickTime-Player, it resembles what I personally think it might look like.
MMPlayer has some Limitations when making a Skin which are not mentioned in the "SDK", I'll add some important here:
MMPlayer has some Limitations when making a Skin which are not mentioned in the "SDK", I'll add some important here:
- You can only use EVEN numbers for positioning Pictures (a limitation of Palm OS 5). If you use uneven pixelcounts, it will simple decrease them to the lower even position. Nothing goes wrong if your Pictures do have an uneven Dimension.
- Use a Background-Image for the textfields like the time, author, title etc., if you do not, there will be overlay-effects
- Transparency in GIFs is not supported (it really IS a pity)
- Using JPEG-Images for Buttons kept crashing my Palm
- Links to other forms must not point to the high- or wide-version, but simply to the standard-form (i.e., don't do a '<formlink ... form="prefs_wide" />', simply do '<formlink ... form="prefs" />'). I got Crashes and strange behaviour doing otherwise
- there are quite a lot of undocumented features, for example you can use 'freq="120"' instead of the 'channel'-tag for an eqslider, or you can use 'Margin="1,2,3,4"' for many elements (1 = left, continue clockwise)
Main View
Prefs View
Playlist View
