At this 0069, I've added Opera support script. pbtweet reached to original web browser which found userscript system on web world. This pbtweet for Opera's 99% codes are similar with script for WebKit just the reverse of GreaseMonkey script. I'll try to merge userscripts for WebKit and Opera but can't merge GreaseMonkey script. Difference is from scope of object from userscript.
Codes of userscript should be capsuled into anonymous function basically. But out of this anonymous function or scope is different from environment of userscript platform.
- Safari + GreaseKit
No limitation. userscript code even works out of anonymous function. I worry this unsafe implementation. - Chrome/Chromium and Opera userscript
It's necessary to add script onto document with importing or adding script elements. pbtweet load global scripts if user-agent is Chrome/Chromium. - Firefox + GreaseMonkey
Developer can add unsafeWindow feature of GreaseMonkey. unsafeWindow is able to be handled as document global variable or function from userscript.
Chrome's userscript was same policy with Safari + GreaseKit in early version but changed into same policy with Opera at Chrome 2.0.x wise-fullly.
Opera is not so bad environment for pbtweet except CSS supporting. pbtweet interface depends on CSS transformation. User setting panel, URL expander and picture thumbnail layout is using with using CSS3 transformation. I should make a some style setting codes for Opera in these days.
However CSS3 transformation seems to be described as eye candy effects, I beleve power-fully transformation of CSS3 should be mentioned as necessary function for interactive user-interface like as you see on pbtweet on WebKit.
No comments:
Post a Comment