erland;253399 Wrote: > When you do this I think it also would be good to consider moving some > stuff into cmdwrappers and the other component template files which are > re-usable. I believe that wouldn't do. I believe we need a JavaScript equivalent to that since I doubt you really want to implement stuff based on the HTML-Links in hreftemplate today. I'm having a hard time implementing iPeng since I have to invent that JS stuff myself. And since I have to get rid of most of the other JS stuff in there since this generally is not device independent and doesn't work on the iPhone (mouseovers, Drag'n'Drop, assumptions about screensize...) I would like Michael's approach to generalize the classes he's using if I didn't know this is gonna get too fat for the iPhone (the new default skin is unsable there not only due to size - mobile Safari is quite good at zooming - but it's simply way too slow and crashes quite often). I BELIEVE we would need a generalized API to provide the functionality that cmdwrappers is delivering now (opening a container, placing an item, selecting stuff) through the JSON/RPC I/F. You can easily send JS code through JSON and I would envision that you have a hook for skin development that let's the skin developer implement generalized classes for "cmdwrappers" commands and then a plugin can just call those and deliver JS code through JSON/RPC to a callback function in the skin itself. That would be flexible AND efficient.
-- pippin ------------------------------------------------------------------------ pippin's Profile: http://forums.slimdevices.com/member.php?userid=13777 View this thread: http://forums.slimdevices.com/showthread.php?t=41417 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
