OSNews: Interview with Mandrake's & KDE's David Faure

OSNews is featuring an interesting interview with David Faure, the French KDE developer who works for Mandrake, and whose code and contributions can be found in many core elements of KDE. In this article, David talks about KDE 3's enhancements and speed improvements, the future of KWord, Konqueror, the debugging tools under Linux, and even brushes on topics such as GNOME 2, .NET, MacOSX and Mozilla. "I do think that Linux will make it on the desktop. I think it has already made it to some desktops, and will continue to improve...

My own family is obviously the testing bed for this, I have my own usability labs in the persons of my wife, her sister and my parents.

I think that what is currently missing for non-technical users is better error reporting (e.g. sending errors to log files is not enough - any CUPS developer listening? ;), and more focus on stability everywhere - users should never ever have to face a crash."

Dot Categories: 

Comments

David, you rock!

Ou dit autrement:
T'es une bête!

by Andy "Storm" Go... (not verified)

"David, you rock!

Ou dit autrement:
T'es une bête!"

Whoow, déjà-vu :-)
(If you don't know what I'm talking about, check the comments at the interview page)

Good job, David. It's a very nice interview! Now, more people know what's happening at KDE development level and it may bring more users/developers to KDE.

Keep up the good work!

Let's hope nobody translates that French sentence into English word for word;)
(No, it doesn't mean that in French ;)

by Thorsten Schnebeck (not verified)

Hey David,

what happend to "poor Jeremy" (see comments)? Or did you forward his mail to a ranting Waldo ;-)
Nice interview! Keep up your great work!

Bye

Thorsten

by Andy "Storm" Go... (not verified)

Must have been his evil twin brother :-)

Honestly I have no idea who that person is and what interaction we had.
I blame my legendary bad memory for not remembering every mail I wrote
in the last 3 years ;)
Probably a misunderstanding, or an irritated reaction at a 100th duplicate bug report
or a "it doesn't work" bug report with no details.

by Andy "Storm" Go... (not verified)

I'm part of the lucky ones that understand it. It's quite funny...

Who wants to know what it means? :-)

Oh, and I know where you can find a recent picture of him that confirms this French text... :-)

Well, at first I thought it was the French equivalent of what people say in Ireland, i.e. that he's a right bull of a man. Except it's saying he's a girly beast. Now that's a photo I want to see ;-)

David Faure Ro>
Et en plus il est français alors il roxor encore plus.
Si il était breton, il roxerait 1000x plus !!! ;)

David Faure (for) president !

Ca y est, les moules envahissent The DOT ! Il était temps !

A quand une tribune sur dot.kde.org ?

-----------------------------------------

What do you think about the inclusion of a "Tribune libre" (Free Board ?) in the dot.kde.org site as in the most famous Linux French site http://linuxfr.org ?
Here is the "Tribune Libre" : http://linuxfr.org/board/

You can go there and post "plop !" or "kikoooo !" the French linux users will be happy to see new persons on the board ;)

[ileave]

/!\ Danger, this post contains lots of "moule" private jokes !!!

I vote for (Faure ?) that idea !

I just hope my keyboard won't blo

by Navindra Umanee (not verified)

Mais vraiment, vous les francais, vous etes trop bizarre!

\\\(@v@)/// ,( e-boo !!)

Yes, we are crazy but we love that ;)

by jasper (not verified)

wouldn't it be ironic if microsoft's dotnet did the imposible, making gnome and kde applications compatible.

but wouldn't that allow proprietary dotnet applications built for windows to be used on Kde without the need for a professional qt license? after all the windows developer doesn't have to know that the application will be used with qt.

by Andy "Storm" Go... (not verified)

No professional qt license would be required.
The running .net application will interact with a 'layer' that translates the commands to KDE/Qt calls.

by Rumcajs (not verified)

And only developer of .Net layer would have to pay for a proffesional licence, I doubt that you force Microsoft to pay for a Qt licence because their .Net application could be run on Qt 'layer'.
There is still something which I dont understand. If I sell Python wrapper I have to buy a special licence for each copy sold, but when I have only a simple Python scripting possibility in my word processor I needn't to buy a developer licence for each copy, I hope. So when need I and when needn't I a developer licence.

by buster (not verified)

Yes, you don't understand. No, you do not need to buy a special license for each copy sold. What does that even mean?

by Carbon (not verified)

Python is open source. You don't need to pay money to do anything with it, since you can download the main Python distribution right off their site for free, not to mention that it comes with most distros anyways. Welcome to the wonderful world of free software :-)

by jasper (not verified)

the simulairity to pyqt is what were I was thinking about.
they weren't allowed to redistribute the windows binary version of pyqt because it allowed delevopers to sell pyqt application without a qt license.

but that wonn't work in the case of mono for kde.
since they can legally redistribute the layer under a mit license based on the qpl version of qt for x11.
but the most important differnce is that the developer doesn't have to write it with qt in mind. only an eula will stop users from using it with the qt-layer.
and a eula is incompatible with the gpl.

by Adam Treat (not verified)

Well, the Qt bindings for Mono are coming along nicely.
(See http://lists.ximian.com/archives/public/mono-list/2002-February/002808.html)
I think I'll have a working DLL before kde3 is released. Maybe the c# bindings will make it in time for kde3.1!

Cheers,

Adam

by Navindra Umanee (not verified)

Good job! I'll make a mention in the next quickies.

by Alain (not verified)

>rumours have it that the gcc/ld developers are working on prelinking

Rumours !!? I thought that open source teams worked in good cooperation each one helping the other in transparent communication...

> most people don't seem to realize how few developers are behind KOffice :).

Yes, it is a big problem, new improvements are now coming too slowly... It is very well initiated, developpers have to realize that working on KOffice is a good way to enter in the KDE team and add improvements for many users...

Thank you David for this clear speach. Here it is a good communication !...

by Carbon (not verified)

Well, there are a _lot_ of Open Source developers, and they can't all be in telepathic (aka IRC :-D ) contact simeltanously, plus the Gcc/Ld guys may still be considering whether or not to implement prelinking.

by Alain (not verified)

No need to have telepathic powers for understanding that there are problems in C++ prelinking (or around) and that we are very numerous to wait improvements.
But perhaps it is not easy to improve, I prefer such an explanation...

by Carbon (not verified)

Well, improvements are being worked on :-)

Like Faure says in the interview, from what I understand, true prelinking is still in the process of being designed/written in GCC. Thats all there is to it, it will be ready when it's done :-)

by Matt (not verified)

(This message is posted so late, no one will probably see it. :))

Anyway, would it be possible to take out the KDE 3 javascript code and put it in an KDE 2 environment? I have some systems that aren't ready for a big(ish) upgrade and the only thing I'd like is better javascript support in Konq. So, would it be possible to compile/distribute it separately? My thought is: why wouldn't it?

by David Faure (not verified)

It _is_ possible, everything is ;)
You'd need to port the KDE3 khtml and kjs back to KDE2/Qt2, in particular all the
QPtrList->QList QMemArray->QArray etc. Plus any changes in the rest of kdelibs that
affect khtml. But it's only about porting, nothing difficult.

You'd get the current bad handling of events (and navigation in forms) problems though...