> Am Sonntag 28 Juni 2009 08:21:05 schrieb Karai Csaba:
>> Hi,
>> Krusader 2.x was branched from 1.80, not from 1.90, that's why 1.90
>> contains many more user actions, than 2.x.
>> Do you think, it would be important to overwrite
>> useraction_examples.xml
>> from the 1.90 version?
> Hi Csaba,
> basically yes, but we should test if they still work with 2.0.0 and
> fix or
> remove those that don't.
Basically every user action should still work, as long as it does not
use the %_Script(..)% placeholder. Extensions written in JavaScript
will not work in Krusader 2.0. My long term plan is to make Krusader
extensible using Kross, which is now, with KDE 4, part of kdelibs
(Krusader-1.x used KJSEmbed from the kdebindings module).
Am Sonntag 28 Juni 2009 14:46:15 schrieb Jonas Bähr:
> Basically every user action should still work, as long as it does not > use the %_Script(..)% placeholder. Extensions written in JavaScript > will not work in Krusader 2.0. My long term plan is to make Krusader > extensible using Kross, which is now, with KDE 4, part of kdelibs > (Krusader-1.x used KJSEmbed from the kdebindings module).
Not related to the user action system itself, but some commandline options are different (or broken?) in KDE4. "Enqueue in Amarok" for instance doesn't work anymore for me. "amarok -a some.mp3" just prints "Amarok is already running!" at the commandline and doesn't append the file to the playlist. And when using it with the KDE3 version it opens another instance of Amarok.
Looking forward to Kross integration. Can't wait to script in Python. ;)
> Am Sonntag 28 Juni 2009 14:46:15 schrieb Jonas Bähr:
>> Basically every user action should still work, as long as it does not
>> use the %_Script(..)% placeholder. Extensions written in JavaScript
>> will not work in Krusader 2.0. My long term plan is to make Krusader
>> extensible using Kross, which is now, with KDE 4, part of kdelibs
>> (Krusader-1.x used KJSEmbed from the kdebindings module).
> Not related to the user action system itself, but some commandline
> options are
> different (or broken?) in KDE4. "Enqueue in Amarok" for instance
> doesn't work
> anymore for me. "amarok -a some.mp3" just prints "Amarok is already
> running!"
> at the commandline and doesn't append the file to the playlist. And
> when using
> it with the KDE3 version it opens another instance of Amarok.
I see... But that's not related to Krusader but the 3rd party tools
changing their interface. So, the existing "Enqueue in Amarok" should
be renamed to "Enqueue in Amarok 1.x" while an user action doing the
same for Amarok 2.x would need to use dbus.
That brings me to an other item on the user action todo list: adding a
%_DBus(..)% placeholder which uses Krusader's DBus connection instead
of calling an external cli tool.
Adding a powerful DBus interface to Krusader itself is an other
important todo...
> Looking forward to Kross integration. Can't wait to script in
> Python. ;)
Same for Ruby here ;-) However, don't expect *me* doing it promptly :-/
|
