[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: About 2.0
From:       Thomas Zander <zander () kde ! org>
Date:       2006-03-26 0:20:36
Message-ID: 200603261220.37020.zander () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Friday 24 March 2006 23:35, Boudewijn Rempt wrote:
> > but Java's RMI isn't usable in script shell, right ?
>
> Depends on the scripting language. It's not usable in bash, at the
> moment, but it's quite usable from python. It's not an insurmountable
> problem: scripting languages with bindings should be able to generate
> proxy objects. And then everything goes swimmingly. It's not a hard
> problem. (It should already be possible in dcop, but I never managed to
> figure it out.)

Technically speaking; everything can be scripted via the shell. You only 
need a front-end app that translates between the internals and the 
command line.
I wrote quite a few in my time for the different network-transparant 
engines I wrote along with them ;)

To answer the question Cyrille started with;
as Boudewijn stated you have to wrap objects with 'native' objects for the 
current scripting language you are using in such a way that the API is 
the same but the internal code will just call the remote object.
In other words; exactly like Java RMI.

At this point I have to mention that Java RMI sucks from a couple of 
viewpoints; so don't go copying that design just yet.
The sane design structures stand; make an OO API based very loosely on the 
internals only which wrap the application internals and expose a minimum 
of the application internals (i.e less objects and more methods per 
object, for example).

This approach tends to be a life saver if you actually start to refactor 
your application but want to keep the API the same.

ps. I created a framework for a scripting interface based on an xml file 
that used java's introspection rules to create the API that could be 
updated really easy without any binairy compatibility issues.

-- 
Thomas Zander

[Attachment #5 (application/pgp-signature)]

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


[prev in list] [next in list] [prev in thread] [next in thread]