> iPeng does offer generic plugin support, yet mobile Safari (the Browser > on th iPhone) has some limitations and specialties compared to a PC > browser. So most plugins work somehow but look pretty bad with iPeng.
I have roughly followed your exchange with Erland. But I'm still not sure every plugin author will need to write a special skin to be used with iPeng. Let's take eg. my Biography/Review plugins (yes, I'm lazy): they display a simple page, with a picture and some text. Is this really any different on iPeng (I'm sorry, I neither have an iPod nor iPhone)? From the five main limitations you mention, the Handheld skin meets at least four the same way, and I do not know about the fifth, as I'm not sure it's ever used at all. In fact Handheld does work with all default templates I know, though it's probably even much more limited than Safari: - mouseovers/d'n'd: set "useAJAX=0" in cmdwrapper_iPeng, and even Favorites & co. won't use d'n'd - space: Handheld is designed to work at 240x320 - this should imho be no issue as long as the plugin uses standard templates - exact positioning: that is a real pain indeed. But again: as long as the plugin is using standard building blocks and wrappers and you provide them, there should be no need writing a skin specific page - onscroll - which plugin's using this? I'm not sure the approach of disabling all plugins because some don't behave is the right way to go. I've always be hesitant adding additional code to my plugins to allow other plugins to interact with mine. Instead we've tried to come up with generic solutions which should be available to other plugins, too. As of today I would have to add code for three other plugins/skins and maintain it. This is a dead end route to go. And why fill yet another datastructure in SC when you can add skins to plugins? Wouldn't it be enough for any plugin author wanting the ultimate functionality out of iPeng to add an iPeng folder with the templates in there? No need for additionalLinks.*iPeng. We should rather look at how we could fix these issues in the generic templates. Instead of asking _all_ plugin authors to change their plugin, we could discuss the real issues with their authors and find a solution which does work for most with the the least effort. If you don't you risk to be without plugin support really soon. Other than Erland's plugins I'm not sure there are many out there which would need a special skin at all. You should probably give some more examples of what's breaking your skin. BTW: is iPeng supposed to be working on a standard Safari? Michael _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
