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

List:       kde-multimedia
Subject:    Easy C++ syntax. Plan. Questions.
From:       Nicolas Brodu <nicolas.brodu () free ! fr>
Date:       2000-03-16 22:43:35
[Download RAW message or body]

It's there, in the KDE CVS.

Look at the examples hellomain, flow and x11comtest to have an idea of what it
looks like. Older examples are still there, to show the necessary _base addition
when using this kind of code.

I'd now like to add a command-line option to mcopidl to generate automatically
some empty implementation files. The development process for a new object would
look like:
- write foo interface in foo.idl
- mcopidl -a_new_option foo.idl  // to generate foo_impl.h/cc.empty for ex
- fill the gaps and compile
- now can use the foo object directly (with the new C++ syntax) anywhere.

I also plan to describe this in a documentation file when it's done.

Now, a question. There is talk on kde-core-devel for freezing kdelibs. I
personally think that freezing arts is a bad idea. Freezing all the other libs
is a good thing, because it will allow people to start writing binary compatible
apps using those libs. But aRts/MCOP is still moving, and IMHO it's not ready
yet for people to start coding apps on top of it with a binary compatible
restriction on us. There are such things or extensions like video which will
surely require a binary incompatibility somewhere/'somewhen'.
Should we talk about it (and to the release coordinators) on kde-core-devel?

Cheers,
Nicolas
-- 
A shortcut is the longest distance between two points. (unknown author)

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