Re: [Anjuta-list] QT libs

["Luke A. Guest" <laguest abyss2 demon co uk>]

On Thu, 2003-03-20 at 02:20, Daniel Kastenholz wrote:
> Hi there.
> 
> I've been programming for about 10 years now and have recently changed
> to Linux. Now, I have to write a QT application for my studies, and I've
> been trying for hours to get the simple tutorial from the Trolltech
> website running. It does compile, but the linker complains about missing
> libraries. I'm really nerved and don't know how to add them correctly.
> (Yes, QT _is_ installed. Path: /usr/qt/3/...) Could anyone kindly help
> me with this issue? 
> 
> Thanks.
> 
> Daniel
> 
> 
> PS: I found some websites about an incomplete project wizard for QT apps
> in anjuta. Even if it was incomplete: Did you really have to remove it?
> It could have helped me solving this problem...

Right, the best way to start with QT/KDE is to NOT use an IDE. If you
do, you'll find it difficult to learn how to piece an app together by
yourself. 

Firstly, make your own makefiles and then follow the simple QT
tutorials. By using automake/conf you're adding unnecessary complexity
to your project that will make understanding how the apps fit together
much more difficult.

Only when you understand this should you really start using an IDE,
you'll understand the code better.

BTW, KDevelop (v2) pretty much sucks right now. Gideon (v3) will be
quite good when it's a) finished & b) not as buggy. But because of the
way that the people behind KDE think, it'll never be comfortable to use
as an editor - the main keys that are used by programmers (i.e. me ;-))
are the cursor keys; if the cursor cannot move around the code in the
way the programmer wants/expects then it'll never be comfortable.

I have just moved back to Gnome (I didn't like the previous versions and
I've had enough of KDE & v2.2.x is much better) and I think that the
Scintilla editor is the best I've used, it's just a shame that Anjuta
has quite a few problems with it (I used Anjuta 1.0.1.at work for the
first time today):

<requests>
Configurable shortcuts - can you tell me how to turn this back on?

Context sensitive shortcuts - A lot of people will want to have the same
shortcuts as MSVC and I have to admit in a lot cases, it's much more
comfortable. I want to be able to execute and continue/run in debug with
the same key, for example. Actually, having shortcut modes, a la
SlickEdit would be nice.

Add breakpoints before debugging commences.

Having the shortcuts saved so that they don't get reset when you restart
your session!!!!

Better CVS integration - Anjuta will not be used in a professional
environment (i.e. by people who cannot handle a command line interface -
that's not me BTW ;-)). So instead of dumping stuff to a text file, it
needs some serious UI work.

The searching is awful.

There's a bug when you try to stop a build (It hangs) - I've reported
that one.

I don't like the reordering of the tabs in the Gnome-2 version (it
should be an option).

Swapping of header/source files should be on the menu or is should be at
least be possible to bind it to a key.

There's probably more, but I can't think of them right now ;-P
</requests>

Thanks,
Luke.