Robb Shecter wrote:
>
> Hi,
>
> I had this idea, and would like to get comments - if it's cool, or dumb
> - whatever:
>
> I want to have my Java programs better integrated or "aware" of my KDE
> desktop. And vice-versa. I don't need the equivalent of the Python-KDE
> binding: This package does two things: it gives access to desktop-system
> features, as well as graphics widgets.
>
> I just want access to system features. I'm thinking of the services
> that the "KApplication" class gives KDE apps: Notification when the
> system is getting shut down, for instance. Or, the generation of temp
> file names.
>
> I first thought about making a binding like the Python-KDE package but
> then decided against it. I also don't want to access native code from
> Java. Too messy and system dependent. My idea is to use CORBA: Have a
> server that creates KApplication server objects. The Java programs then
> connect to a KApplication server instance and also register themselves
> for callbacks.
>
> There'd probably be a small applet-like framework that Java app writers
> would use that would hook their program into this setup.
>
> The system could also use something like Echnida to launch Java apps
> quickly.
>
> Now, once this basic idea is implemented, the CORBA/IDL solution offers
> extreme flexibility. For example, there's no reason that a GNOME server
> couldn't be written that creates the GNOME equiv of KApplication
> (whatever that may be...). It would serve the same IDL, and all the
> Java apps would work with it too. The same could even be done for MS
> Windows.
>
> AND, this can go the other way: Programming environments like Squeak
> Smalltalk can be adapter to fit into the client-side of the framework.
>
> So, what this system would really become is a "VM-driven language to
> desktop integrator".
>
> Comments?
My understand is that KDE is completely CORBA driven anyway. ( Even
though their object model is called KOM ). CORBA integration should be
fairly straightforward at that point. GNOME uses CORBA as its IPC (
though only C binding at this point ), so CORBA integration should be
easy there too. The trouble is differing IDL defs and system
architectures. The good news is that the high-level GNOME and KDE
people are trying to unify their IDL defs and foster as much
cross-integration as possible. IMO, apps tied to one desktop defeat the
purpose of having the option of multiple window managers. I love the
KDE object model, but their desktop looks like it was built by a bunch
of left-brained scientists who have no lives. Techincally it's a nice
system, but aesthetically leaves me wanting more. But that's another
discussion altogether.
--
Justin Lee | Does is really matter how far you go?
JEDI | Can you get some sleep, now, standing on so many toes?
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
