more_examples_branch: kdebindings/korundum/rubylib/examples

Richard Dale Richard_Dale at
Mon Jan 19 12:02:31 GMT 2004

I don't know what to say here - I think Alex is actually doing some great 
stuff with korundum. On the other hand, if David Faure has an opinion on some 
kde issue that differs from my own, it makes sense to pay attention to what 
he says.

I would much rather have a calmer Alex making commits to kdebindings, rather 
than keeping somewhere 'secret' where only he can play. I think working on a 
language binding is very different to working on a normal kde app. The root 
cause of the problem here is that I think that kdebindings authors would 
rather be able to target the kde 0.1 release after the main one - ie kde 
3.2.1. To us (kdebindings authors), that is a short term target and we would 
want to put as much effort as possible to completing asap. 

I personally can manage to get one binding up to date for the main release, 
and I concentrated on java this time. I had no time for ruby or C for 
instance, but could get something useful done for the 0.1 release.

I think the difference of opinion arises because David is thinking of korundum 
for 3.3, but Alex and myself are concerned with getting it off the ground for 
kde 3.2.1.

-- Richard

On Monday 19 January 2004 11:34, Alexander Kellett wrote:
> On Mon, Jan 19, 2004 at 11:57:39AM +0100, David Faure wrote:
> > What's so hard to understand about "fixing bugs for 3.2 has more priority
> > than working on post-3.2 stuff"? Of course for new stuff the only way is
> > another branch, but the question was whether the new stuff can't wait a
> > little bit, while bugfixing things for 3.2.
> sorry. *showstoppers*. not bugfixes.
> it seems you didn't notice but if you read over
> the commits logs from me over the past week i
> *have* been fixing bugs. and the reason for this
> is the development work i'm doing.
> (yeah i know, not bookmarks bugs, but
>  korundum is more important now imo)
> > > i'm gonna start doing all development out of tree
> > > from now on. i'm sure you'll all love my once monthly commits
> > > from this point on.
> >
> > Nice mentality. "Boohooooo. I'll sulk and play on my own".
> well, my main reason was actually the downtime.
> which not many people are really all that woohoo about.
> anyway, i just want to code. i'm ****ing sick of the
> politics involved with kde these days.
> also, i've been moaned at for the incrementality of
> my commits too many times now. i'm not going to change
> my style of programming, so, i'll just sync up kde
> cvs everyonce in a while instead.
> > I sure wish you would see things a little more from users' point of view
> > than from your own. From a user point of view, is it better if
> > incremental search is built into khtml or done as a separate ruby script?
> > How many people don't even have a ruby interpreter at hand? Which
> > solution is more integrated and thus easier to use? But sure, you're a
> > free man, you can code things in ruby and in a separate repository even,
> > but then this has little to do with KDE anymore.
> this is a kdebindings korundum sample. a simple proof of the fact
> that it (korundum) can be used for real world prototyping/application
> work. the proof of concept incremental search impl was needed in any
> case and i thought you might it interested therefore. in any case, it
> can't possible be used in this form for konqueror as it is very much
> centered around modifying the dom tree.
> i just don't enjoy c++ programming anymore. and nor do i enjoy
> bookmarks / keditbookmarks programming as c++/qt is its base
> language. too much grunt work. therefore. yes maybe you're right,
> what *does* my work have to with you peoples "KDE" anymore?
> i'm not sure. in any case. on richards request i've merged the
> examples into head and will keep it up to date whenever i can
> be bothered.
> i can see many many flaws in this non distributed source
> system we use now. quality control seems to involve reverting
> changes when ones applications break. pretty pathetic.
> mvg,
> Alex

More information about the kde-core-devel mailing list