Michael Herger;253403 Wrote: > > Default is still based on the same wrappers and templates. Only a small > number of them has been customized. But I've added a lot of new (and > partially incompatible) JS, that's true. > > The main issue I remember you had was due to some more "advanced" > layout features like scrolling DIVs.
It was some time ago so I don't remember exactly what problem I had. But I know that my Custom Browse plugin currently has to have some different code for the new Default skin compared with the Classic/FishBone skin. The Nokia770 skin also requires some skin specific code and the third party iPeng skin which us currently under development requires another variant. I also know that Joerg currently doesn't use the contentcontainer/contentitem blocks very much in the iPeng skin. I'm not sure of the exact reason, but I imagine that they doesn't fit the iPeng skin since it looks very different from all the skins bundled with SqueezeCenter. I'm talking about the more advanced features, I'm sure it will work fairly well in the simple case where the plugin has a very simple user interface or the skin looks almost exactly as one of the bundled skins. Michael Herger;253403 Wrote: > > I hope you reported all the issues you encountered... > I'm pretty sure I reported all the issues with the new default skin, but I haven't reported all the cases where I did have to have different code. I guess I could look through my code and compile a list of that if it is of interest ? I guess it isn't urgent for the 7.0 release though ? Michael Herger;253403 Wrote: > > > I also like pippin's idea regarding some sort of style guide. It > would > > be good if the principles regarding the skins bundled in SlimServer > > were documented somewhere. > > http://localhost:9000/html/docs/skins.html > http://wiki.slimdevices.com/index.cgi?SkinDevelopment > > I was thinking about a style guide regarding behaviour, not how to implement a new skin. A concrete example is the things discussed in this thread "Should a text field be visible always or should it be shown when one moves the mouse over it". Another one is "Should a button be shown directly or should it be hidden until the user moves over the item which the button belongs to". The behaviour is probably different between different skins, so I think the important thing is just to have some kind of documentation that describes the thoughts behind the design of the new default skin. However, I'm also aware of the fact that documentation doesn't solve every problem, some people tend to not read it anyway. So I think something simple would be good and then focus on making the code easier to reuse/inherit instead. -- erland Erland Isaksson 'My homepage' (http://erland.homeip.net) 'My download page' (http://erland.homeip.net/download) (Developer of 'TrackStat, SQLPlayList, DynamicPlayList, Custom Browse, Custom Scan, Custom Skip, Multi Library and Database Query plugins' (http://wiki.erland.homeip.net/index.php/Category:SlimServer)) ------------------------------------------------------------------------ erland's Profile: http://forums.slimdevices.com/member.php?userid=3124 View this thread: http://forums.slimdevices.com/showthread.php?t=41417 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
