Project directory structure

[Tomaz Canabrava]

'I'm too old' => My current job spend three months stopped because the two
admins couldn't agree on the code-style, one came from Python, other came
from C, for a c++ project.

on the UI part, there should be only the Qt-globals, like 'qApp' - a global
QApplication that can be called anywhere. but I doub't we will need to call
it in the core, so we are safel. :)

A good thing actually, from the ui code we can recognize something that's
from the core easily by seeing that's not_camel_case.

Tomaz.


2013/4/4 Dirk Hohndel <dirk at hohndel.org>

> Tomaz Canabrava <tcanabrava at kde.org> writes:
>
> > one could argue that the STL usses_underscore_names, and that's the 'c++
> > default',
> > I read in a KDAB blog ( one of Qt's maintainer ) about the use of
> Container
> > classes of Qt vs STL and the bottom line was 'use stl', I guess Thiago
> > could state a point here. I'm more used to Qt containers ( and we will
> > surely use those for the Model classes of the lists / table views. ) that
> > are CamelCase too.
> >
> > for myself... I'm too old for arguing about naming_differences about
> > beingAbleOrNot to use one or another. I'd stick wich the project says to
> do
> > so.
>
> I'm amused when others play the "I'm too old" card...
>
> I can live with either, I just
> a) prefer underscore (just a matter of habit - most of the projects I'm
>    involved in in the last decade used underscore)
> b) prefer consistency within a project
>
> I guess we can use camelCase in the UI code and underscore_variables in
> the core logic. That is reasonably consistent and will only cause
> confusion if and where we need global variables and call one from the
> other...
>
> /D
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hohndel.org/pipermail/subsurface/attachments/20130404/6264a016/attachment.html>