Header files (Re: A little review of kdecore & kdeui)

[David Faure]

On Friday 07 April 2006 23:00, R.F. Pels wrote:
> On Friday 7 April 2006 22.47, David Faure wrote:
> 
> > > I think that makes it harder to remember.
> >
> > If you can remember to type "new QLineEdit", how can you not remember to
> > type "<QLineEdit>" after the include? It's exactly the same word... I know
> > that it changes our habits (which isn't mandatory), but really, for many
> > people (I should know, I'm doing one week-long Qt4 training per month those
> > days), it's really much much simpler than "ok, for QVBoxLayout I need to
> > include qlayout.h" < now THAT is harder to remember.
> 
> True. Still. I think it's harder. And I remembered why there was a reason to 
> keep the names lowercase. Not all filesystems are case-sensitive and  
> non-camelcapped names are easier to type. I know it might seem like a nit, 
> but I think it would be unwise to go against what numerous people and 
> software packages have established as a standard.

Nobody is talking about "going against", since this is always about "offering both".

And don't forget that KDE developers are Qt developers, so why should KDE go
against (and here I do mean "go against") established Qt practices, where developers
can use #include <QLineEdit>? How many times do you think we'll see the request
"why can't I #include <KLineEdit>" on kde-devel at kde.org once people start developing
with Qt4/KDE4, if we don't provide such includes? I'm 100% sure of it: we'll see that
request over and over - and over and over - again. So let's do it, and let's do it right.

But I don't konw whether right means "during install" (and no camelcase inside kdelibs code)
or "like qt, with forwarders to srcdir in kdelibs and different ones after install" (and
apparently much trouble for kdebindings people, although now that they can handle Qt,
kde should rather be similar, no?:)... )

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).