Dev path for Gideon

[Kuba Ober]

> > I am curious to find out if the current text editor implementation will
> > stay or if it is being completely replaced by KVim and/or KATE.
>
> You can use every editor for Gideon that implements the KTextEditor
> Interface (from kdelibs). For non-Qt/-KDE editors it's a little bit tricky
> but possible. For example is QEditor (editor of the QtDesigner) available
> for Gideon.
> So there will be no replacement.

You meant the current old-kwrite-based editor *will* be replaced by the 
KTextEditor interface. That means that the current editor code goes mostly to 
the trash can. I'm working on indentation in kate right now, but that's still 
some way before it's finished (I'm thinking of making it a little more 
powerful than in emacs ;-).

> > As for
> > project management, is this still reliant on makefiles or is it being
> > changed to operate more like CodeWarrior and MSVC with an option to
> > export makefiles?
>
> No it is not reliant on Makefiles but on Makefile.ams (for Automake
> projects).
>
> Gideon is also "independent" from the build tool you use. Of cource this
> stuff has to be implemented. In parts/*project you can find them. The
> autoproject part (to handle Makefile.ams) is in place, the trollprojectpart
> (for .pro files) is extended in the moment by Jakob.

> An export is not planned

Because the build tool system usually makes the Makefiles from something else 
(Makefile.am files in case of auto* system, .pro files in case of qmake) , so 
yes, you *do* have barebone makefiles since it's usually make that is used 
for building (so invoking building in gideon invokes make, rather than some 
internal make-tool like in MSVC).

Cheers Kuba Ober