On Friday 20 February 2009, Richard Dale wrote: > Yes, but how does that differ from just adding > createConfigurationInterface() to the scripting api in addition to > showConfigurationInterace()?
because that would only work nicely for the Python and Ruby script engines. for everything else, there'd be more code still required. saving a couple lines in the Python/Ruby engines by making AppletScriptEngine more specific to their design patterns doesn't really fit with the idea that the engine parent class is trying quite purposefully to not dictate or prescribe API. the Python and Ruby engines take the "we are binding libplasma, KDE and Qt" approach, which is just fine and completely appropriate. that is not, however, the goal of AppletScriptEngine. ergo ... -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
