Malaga Discussions I

[Boudewijn Rempt]

On Monday 29 August 2005 10:12, you wrote:


Well, that would suck if there had been scripts yet -- but the reason there 
aren't any yet is that I've been afraid of just this happening. So, yes, 
d-bus has already had a detrimental effect.

> Your users will have to do some search and replace (I have no idea yet
> about the details, but it should be in the line of 'dcop krita' -> 'dbus
> org.kde.krita') - that's the kind of migration work we expect here from
> our users going from KDE3 to KDE4.

So, how about dcopref and things like that? And I guess I will have to redo 
the interface stubs, right?

To me that means that I should stop working on dcop interfaces for Krita right 
now because the work will be wasted -- and the work I would have to do to 
port Krita to dbus is essentially churn because it will offer neither me, as 
application maintainer, nor the users -- the script writers -- any 
appreciable benefits.

> And the main question is not if we should have scripting or no scripting,

Of course not. Especially since we already have it.

> but if we can put that work on our users/3rd party app developers or if
> we should make sure 'dcop krita' will work in the future.

I'm not knowledgeable like Maksim, so I'm not really entitled to an opinion, 
but if we were to break stuff, it would be good to have something that made 
writing scripts using rpc really easy. Like making the interface of the 
exposed classes completely discoverable in a way that allow authors of rpc 
client language blndings to recreate the original interface essentially on 
the fly. 

It's not that I'm all that happy with dcop -- especially dcop ref as a 
generic, opaque reference stub that doesn't expose the interface of the 
object it refs for is unpleasant. But I don't know whether dbus actually is 
better in that area.

-- 
Boudewijn Rempt 
http://www.valdyas.org/fading/index.cgi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050830/e3ae5efd/attachment.sig>