mherger;292438 Wrote: > > Some details about SqueezeJS: It's all grouped around the > SqueezeJS.Controller class, which handles all communication with the > server, signaling events like playerselected, playlistchange etc. > > The second main class is SqueezeJS.UI which offers a few UI components > like buttons (play/pause, fwd, power etc.) and labels (playtime, track > information etc.). All buttons available in the player control panel > are implemented in SqueezeJS.UI, thus can be added to any page with > only a few lines of code. >
Nice concept to vamp up the old skin architecture. Good work. A pity that Ext2 is such a resource hog so it's not an option for iPeng... One question: Is there an abstraction in the SqueezeJS.UI between the element control and the visualization? Or can that even be done completely in CSS? What I want to get at is: My understanding is, that using SqueezeJS it's easy to use the default UI components in other applications, what about the other way around, changing UI components for the existing skin? -- pippin --- see iPeng at penguinlovesmusic.com ------------------------------------------------------------------------ pippin's Profile: http://forums.slimdevices.com/member.php?userid=13777 View this thread: http://forums.slimdevices.com/showthread.php?t=46423 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
