The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Great, just great!
by Iuri Fiedoruk on Monday 21/Jul/2008, @04:35
|
Thanks to all that work on bidings.
Using script languages is, on my opinion, the future of desktop. It brings more flexibility, speed of development and is much easier to modify. For example, I do not see a future of plasmoids beings written in C++ becuase it's hard to create packages for all systems and plataforms, while writing a plasmoid with a script, you just have to install the script interpretator and voilá! :-D
Also, adding Lua is great news, I've worked a bit with it in freecraft/stratagus/stargus and it is a lot of fun and flexibile.
|
[
Reply To This | View ]
|
Re: Great, just great!
by Sebastian Sauer on Monday 21/Jul/2008, @05:36
|
re plasmoids;
* href="http://techbase.kde.org/Development/Tutorials/Plasma/RubyApplet (QtRuby tutorial)
* http://www.kdedevelopers.org/node/3560 (QtRuby and C#)
* http://techbase.kde.org/Development/Tutorials/SuperKaramba#Plasma (you can even use Plasma dataengines)
* http://developer.apple.com/macosx/dashboard.html (they are supported by Plasma too)
* more to come :)
|
[
Reply To This | View ]
|
Re: Great, just great!
by Thomas Moenicke on Monday 21/Jul/2008, @09:21
|
> It brings more flexibility, speed of development and is much easier to modify.
There should be additional code implemented in the language on top of the C++ API, in order to get more out of the language characteristics and simplify the usage. But the developer should still be able to dig deeper if he wants to learn more.
|
[
Reply To This | View ]
|
|
Superkaramba?
by Jim on Monday 21/Jul/2008, @05:12
|
Does all of this mean Superkramba will soon work in KDE 4.0 without complaining about missing Kross support? I have yet to get Superkaramba to work in 4.0
|
[
Reply To This | View ]
|
Re: Superkaramba?
by Sebastian Sauer on Monday 21/Jul/2008, @05:28
|
It works and worked already in 4.0. Depending on the exact error-message, which you don't shared with us, it may the case, that you just need to install kdebindings (or to be more exact either ruby-supported located in kdebindings/ruby/krossruby or python-support located in kdebindings/ruby/krosspython).
|
[
Reply To This | View ]
|
Re: Superkaramba?
by Debian User on Friday 25/Jul/2008, @01:55
|
Hello,
isn't it so that Plasma is supposed to contain the Superkaramba in 4.0?
Yours,
Kay
|
[
Reply To This | View ]
|
|
Regarding Plasma and Python...
by S. on Monday 21/Jul/2008, @09:38
|
Greetings all,
With my apologies if this is an FAQ -- I haven't been able to find an answer to it yet, at any rate -- but do the Plasma bindings for Python work? My understanding is that they didn't as of not very long ago, but that was to be fixed at the meeting.
Related question: has anyone produced working example code for Python Plasma widgets, dataengines and runners, that we could put in the Wiki? (Emphasis on 'working' -- I know there are bits of non-working code in SVN.)
Thanks. :)
|
[
Reply To This | View ]
|
Re: Regarding Plasma and Python...
by Simon Edwards on Monday 21/Jul/2008, @10:12
|
Someone did some initial work on getting Python working with Plasma. But they don't have enough time to continue with it so they've passed it on to me. Python support should be in KDE 4.2, working compilable code should be in SVN much before 4.2 though.
--
Simon
|
[
Reply To This | View ]
|
Re: Regarding Plasma and Python...
by Anon on Monday 21/Jul/2008, @13:14
|
Thanks Simon - appreciate you taking this on.
|
[
Reply To This | View ]
|
Re: Regarding Plasma and Python...
by S. on Tuesday 22/Jul/2008, @01:44
|
Fantastic! Thank you lots, Simon. :) I did look into contributing, although I'm sorry to say I was left confused and generally at a loss on how to proceed by what I found in SVN back then (that was a couple months back). There was stuff that looked like it /should/ have been working, and yet didn't, and I couldn't tell whether it was broken, or I was doin' it wrong.
Anyway -- how may a wee little user like yours truly help with things?
|
[
Reply To This | View ]
|
|
My hobby
by Ian Monroe on Monday 21/Jul/2008, @13:38
|
Writing QtRuby scripts that run using the Kross QtScript extension running in a QtRuby application.
:) :)
|
[
Reply To This | View ]
|
Scripting Documentation
by Kit on Monday 21/Jul/2008, @14:12
|
One thing I'd like to see on Techbase would be to extend the Kross documentation to include more about how you should design your API with various Dos and Don'ts. I'd imagine theres lots of research and papers out there on designing a nice high-level API, even just collecting links to them on a Techbase page would probably be quite useful.
On a slightly side note, does the Smoke-to-Kross bridge restrict sharing objects to situations where both are in the same language? (i.e. could you use QtRuby bindings with the Kross-Python backend and any other combination?) Also, in the future would you (theoretically) also be able to mix-and-match C#, PHP, and Lua as well?
|
[
Reply To This | View ]
|
Re: Scripting Documentation
by Sebastian Sauer on Tuesday 22/Jul/2008, @04:27
|
> One thing I'd like to see on Techbase would be to extend the Kross
> documentation to include more about how you should design your API
> with various Dos and Don'ts.
yes, we - scripting in general - need there really more documentation. That doesn't mean to only write new tutorials but to also connect already existing information together and to provide specialized code-snippets, best-practice samples, links to already existing solutions that does solve a specific problem already, modules that can be used, etc.
> does the Smoke-to-Kross bridge restrict sharing objects to
> situations where both are in the same language?
smoke is language-independent and so is Kross. So, it's not restricted to a specific language though there may tweaks needed for each language.
> i.e. could you use QtRuby bindings with the Kross-Python backend
Should be np as soon as kdelibs/kross/core/* is accessible in QtRuby, someone could use it to exec e.g. Python-code from within Ruby. Same with all other backends.
|
[
Reply To This | View ]
|
|
ObjC Bindings?
by Marc Driftmeyer on Monday 21/Jul/2008, @14:14
|
Are you looking into this option once Qt has ObjC support and Cocoa?
|
[
Reply To This | View ]
|
Re: ObjC Bindings?
by Richard Dale on Tuesday 22/Jul/2008, @03:08
|
The very first language binding I did was an Objective-C Qt one in 2000. But there was virtually no interest in it, as everyone who likes Objective-C was more interested in GNUStep than Qt or KDE.
Although Qt will be based on Cocoa, I don't think it will have any sort of public Objective-C api, and I would be surprised if anyone at Trolltech was to produce a language binding for Objective-C
The old Qt Objective-C binding was implemented by using a C binding to the Qt api and calling the C functions from Objective-C. Objc++ wasn't available for Gnu Objective-C on Linux then, and so you couldn't easily mix C++ and Objective-C.
Today I wouldn't implement a binding like that at all. For Ruby, PHP and C# we use an auto-generated dynamic runtime library called 'Smoke', which allows you to look up methods according to their type signatures. In Ruby there is a method called 'method_missing' which corresponds to [NSObject :forwardInvocation], and the Ruby bindings use that method to trap method calls and forward them to the C++ methods in the Smoke library. So it should be possible to do that in Objective-C. But as well as the types of the method arguments we would need to add their names to the Smoke tables, to allow lookups by name as the Objective-C method signatures would be derived from the arg names.
|
[
Reply To This | View ]
|
Re: ObjC Bindings?
by Marc Driftmeyer on Tuesday 22/Jul/2008, @17:38
|
Thank you for the very professional and thorough background on the matter. Having Debian and OS X with Qt on both platforms [made the jump to KDE4.1RC1 after I thought they were mature enough to say adios to 3.5.9 (I was vocal in the past but enjoy the start of what I'm seeing--the Widgets customization or drag n' drop positioning for the Panel Widget would be an improvement; ordering of how widgets currently have to go onto the panel stack I take is something that will later be relocatable to suit the user's needs--but glad it's almost there)] I also include GNUStep and the Etoile-Project to see how they are maturing. I've noticed a lot of Smalltalk additions to the Etoile-Project hooking in with ObjC so I hope once the Etoile-Project is capable of more that there would be a way to have more cross-pollination between KDE, GNUstep, Qt and OS X.
I realize it's a large effort, but I think it will be much easier if GNUstep does indeed get their port of WebKit onto GNUstep.
I'm glad to see all the other additions like Ruby and Lua. I've personally zero interest in C# but then I can't stomach Microsoft [it's that ex-NeXT employee/ex-Apple employee in me].
- Marc
|
[
Reply To This | View ]
|
|
What about Java-KDE binding?
by Noa on Wednesday 23/Jul/2008, @13:37
|
OpenJDK is near to be finished and included in all Linux flavours.
Why not a Java-KDE binding?
There is QtJambi (Qt-Java binding) supported by Trolltech :
http://trolltech.com/products/qt/features/language-support/java
|
[
Reply To This | View ]
|
Re: What about Java-KDE binding?
by Simon Edwards on Saturday 26/Jul/2008, @01:42
|
It's not a question of why it is a question of who. Most of the hard work is already done. It is now a matter of someone stepping up to do (and maintain!) a KdeJambi or whatever you want to call it.
--
Simon
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|