A few clarifications: 1. thanks for the perl explanation, I'll add that. 2. textlink. The problem is, this is an INVISIBLE control, that is, the control is the full content field and you can just provide a link. What do you need the other content for? You can have more than one JS command. 3. useAjax=0. Can you explain me, what the result of this will be? Rationale: I don't want to disable AJAX, in fact I use the AJAX controls whereever I can, the problem is, that lots of plugins make assumptions about the screen layout and UI when using AJAX. 4. 'controls': That's a bug, didn't remove it from a left side condition when moving 'controls' to the right. I will change that. As a fix you can change line 189 in cmdwrappers to <td class = "listRow" style = "padding-left: 6px" [% IF !leftcontrols %]colspan = 2[% END %]>
The main point is a more general one, that you, Michael, probably don't know because you - having no iPhone - haven't read my UI philosophy article on penguinlovesmusic. So in brief: I want this not just to be a skin that displays everything that can be shown in SC, but i prefer it to be usable, which is not the case if I just scale stuff. I tried the handheld skin, it's not usable on iPhone IMHO. I also made the conscious decision to use the iPhone UI philosophy instead of the SC one wherever possible, yet that brings some changes. I don't want to see lots of stuff that doesn't work. It's annoying for the user. If a plugin developer writes me an e-mail stating "my plugin does this just fine, I've tested it and I don't wanna change it' I can easily hardcode this by adding it to my hash of default plugins. My experience so far has been, that most plugins display badly since most define their own containers or make assumptions about the underlying code. Favorites, for example, generates a list around the content where I use a table, thus favorites completely screws up the layout. This is not my fault, the plugin just doesn't comply to the cmdwrappers code structure, which is no wonder since it's not really documented. My experience is, that this is true for almost every plugin I stumble upon. Some of the changes in UI philosophy I made: I usually don't want to see a "play this" button on the screen. It just takes up space and annoys users used to iPhone because they are used to click on the item text. Thus textlink. I could just hardcode the playcmd into the text and remove the icon when I decide this is a playable item but I wanted the plugin developer to be able to decide. I can't just throw in a lot of controls somewhere on the side because if you crowd them, you will always click on the wrong one. I repeatedly hit the wrong one even with a mouse on the default skin this simply doesn't work with the iPhone. They have to be manually positioned or this at least has to be tested. The sense of positioning some of the controls to the left and some to the right is not to accidentally click the wrong one. The maximum number of controls acceptable on the right side, in my view, is two, even that is a stretch! Good discussion, anyway! -- 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=41697 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
