moin,
as promised, I'm going to write some lines, about my development-workflow.
Let's start with SCM. I'm using git, because I sometimes don't have a working
connection to the Internet when developing. (Or it's damn slow.. and SVN,
especially on sf.net is a PITA when it's slow ;)) I haven't fou
Moin,
On Tuesday 22 December 2009 02:17:20 P Zoltan wrote:
> - Aproximately what are the dependencies of the qt4 version of ktechlab?
> Do we need a specific (greater than X) version of kdevplatform? I'm asking
> because we should state those in the wiki, in the compiling section, and
> also I hav
On Tuesday 22 December 2009 10:53:51 Matthew Ayres wrote:
> To me, it looks as though STL is the conclusion here.
I'm fine with that. I will change everything in my code accordingly and stick
to STL iterators for the container-classes from now on.
bye
julian
signature.asc
Description: This is a
I agree with Zoltan.
Expanding slightly, I would point out that adding new functionality before
the port is done just adds more work to the porting process.
On Mon, Dec 21, 2009 at 11:57 PM, P Zoltan wrote:
>
> IMHO new modules / functionality should be added after having a working
> qt4 / kde
To me, it looks as though STL is the conclusion here.
On Tue, Dec 22, 2009 at 12:45 AM, P Zoltan wrote:
>
> So... what is the conclusion?
>
> java style: julian, me
> stl style: alan, matthew, lot of old code :D
>
> Helping question: do we want same style in all the codebase, or not? I'd
> s
