Handcoder's IDE for Qt

[elcuco]

are you re-painting after 5 seconds, with the functions been bold? that's sweet!

I fail to understand how the help browser works, but it's kinda handy when you zoom it down 2-3 times. I prefear having the text in a small font, and then get more info on the page - so i can have more space for the text editor itself. I would recommend you to work more on the help viewer - it's a killer feature for me.

BTW,
My sub-projetcs demos are not working on this new version as well.

[magland]

are you re-painting after 5 seconds, with the functions been bold? that's sweet!

Yes, it's very useful to quickly see if there was a misspelling or something... or if you forgot a #include, because it only bolds keywords that are visible from the current file.

I fail to understand how the help browser works,

Could you explain... do you mean that it doesn't work properly when you press F1 over a keyword, or do you mean that you don't understand how it's coded...?

but it's kinda handy when you zoom it down 2-3 times. I prefear having the text in a small font, and then get more info on the page - so i can have more space for the text editor itself. I would recommend you to work more on the help viewer - it's a killer feature for me.

Sure, perhaps I'll add a zoom feature (is that built in to QTextBrowser?)

BTW,
My sub-projetcs demos are not working on this new version as well.

Funny... I tried the project attached to QDevelop issue #155 and that seemed to load correctly... could you send me your test project?

BTW I still have not resolved the "code completion losing input focus on Linux issue"... but I'm working on it.

Many thanks,
Jeremy

[elcuco]

I don't care about the code. Only the functionality, I am a user of your application, not a developer.

My text cursor is in a word "QString", when I press F1, the help browser is opened on index.html and not qstring.html.

The zoom is built in, you will find it. My suggestion is: zoom out by 2-3 by default.

Another rant, the buttons on the left are a good idea. However they are not intuetive enough. It's hard for me to understand what each one of them does. Nice idea tough, maybe reducing the count, and adding some text will help.

[magland]

My text cursor is in a word "QString", when I press F1, the help browser is opened on index.html and not qstring.html.

Oh yes... it's a case-sensitivity issue, just change "/html/Qt.dcf" to "/html/qt.dcf" in HiQtDocBrowser.h, and that should do it... or you can just wait for the next version.

Another rant, the buttons on the left are a good idea. However they are not intuetive enough. It's hard for me to understand what each one of them does. Nice idea tough, maybe reducing the count, and adding some text will help.

Yes, I agree, and I'm working on it.

[magland]

Here's a new version
HiQt-0.1.6

Feedback appreciated...

New Features since 0.1.5:

Documentation browser
fixed Linux bug - so docs are now available
keyword searches no longer need to be exact matches
"copy" (Ctrl+C) text now works
Zoom in and zoom out
Name of current doc file is displayed in current doc bar

Main Window
improved tool button layout, menu options, and shortcuts
Templates
Able to create new project and main source file from template - handy for testing quick programs

Editor
Significantly sped up editor using a workaround to a Qt bug in QTextEdit (separate thread)
Better (more continuous) syntax highlighting
Multi-line indentation using [Tab] and un-indentation using [Shift+Tab]
Improved auto-indenting

[magland]

Here's a new tool in HiQt that you don't see in other IDE's...
it's a menu option for generating the file and class dependency
graphs for the currently active project. Within seconds, you
can see the big picture for your project, and double click on
a file node (or a class node) to go straight to the source.
Below are graphs for the elegant qmake.pro.




Graphs are generated using GraphViz --
which I include with the Windows binary distribution.
Usually output of Graphviz is .png or .ps, but in this case
I show the nodes as QGraphicsItem's in a QGraphicsScene
so there are a lot of possibilities...
for now you can just double click the nodes to go the the source.

A note to Linux users... I realize that HiQt
is quite unpleasant on Linux -- i.e. there are several
things that for whatever reason don't port nicely
from Windows. The most severe problem is the
loss of input focus during code completion -- another
thing is the ctags/etags issue. I'll work on these things,
but for now I have very limited access to a Linux box
with 4.3.0 (I need latest version since there are unworkable
bugs in 4.2).

To Windows developers... I believe that the program
is stable, and in my opinion your best bet if you want
to manage your own .pro files. You need Qt 4.3.0 to use it.
Please try it and tell me if it is not getting to be even more
of a useful tool than microsoft studio.

Also, latest version has much faster code completion than a few days ago.

[magland]

I fixed the code completion issue on Linux, so it should be usable on Linux now. As mentioned by fullmetalcoder, you need to make sure you have the latest ctags installed.

http://www.qt-apps.org/content/show....?content=62825

[magland]

Interface to Doxygen

Many programmers have discovered the value of documenting C++ source code using Doxygen-style tags. In fact, I believe that the creator of Doxygen was trying to replicate the Qt documentation system (but somebody can correct me on this). Anyway, I don't use Doxytagging as much as I should for the following reasons 1. I'm lazy 2. It takes some effort to manage the Doxyfile (ensuring that it includes all of my project files, but not any extras) 3. it takes some effort to generate the docs and view them and keep track of them.

To remedy this, I have added an option in HiQt which allows user to
(a) One-click generation of Doxygen documentation on the currently active project
(b) Viewing that documentation within the IDE (like the Qt reference doc browser)
(c) Press F1 on a keyword to go to the Qt docs, Press F2 on a (project) keyword to go to the project docs
(d) Browse the docs, and then navigate back to the corresponding source code

(Remember, Handcoder's IDE never writes anything to your project directory...)

Now I will use Doxygen tags a lot more -- because I can see the benefits instantly... and I hope you will try it too -- (especially if you use windows because it will work out of the box with 4.3.0, Linux should work too I am guessing)

http://www.qt-apps.org/content/show....?content=62825

[magland]

Code completion is now much faster (and better) than QDevelop and (for practical purposes) comparable to Edyuk.

There is also an interface to QObjectBrowser... so you can view a tree of all of your objects/signals/slots/properties during run time! (Use the "build with runtime utilities" command")

Also, as I mentioned earlier, there is built-in Qt docs plus project-specific docs using Doxygen.

Think about it... there must be something good about the IDE I am using if I can add these features so quickly... If you like it, post positive feedback, because that will tell others to try it if on the fence.

Also, if you like the approach, consider joining the dev team. Hoping to generate interest so the project can take on a life apart from me... then we all benefit.

http://www.qt-apps.org/content/show....?content=62825

[sunil.thaha]

First of all,
Kudos to you for the great work.
I was able to install the application flawlessly :-)
Compiling and debugging is great

The explorer, pro file handling is really harmless !!

Bugs:
But the code completion has some bugs.

You type in QLa(Ctrl + Space )
You will not file QLabel ??

or

Type QMou( Ctrl + Space ) you will get the QMouseEvent highlighted.

Delete the "ou" of the QMou and type ai for the QMainWindow
Again ?? you won't find QMainWindow in the completion list

[magland]

First of all,
Kudos to you for the great work.
I was able to install the application flawlessly :-)
Compiling and debugging is great

The explorer, pro file handling is really harmless !!

Thanks for those words... it'll keep getting better. Have you discovered that you can double click on a keyword to get a list of tags for that word... then double click a list item to navigate... I find this very useful, and soon there will be a "back" button.

Bugs:
But the code completion has some bugs.

You type in QLa(Ctrl + Space )
You will not file QLabel ??

or

Type QMou( Ctrl + Space ) you will get the QMouseEvent highlighted.

Delete the "ou" of the QMou and type ai for the QMainWindow
Again ?? you won't find QMainWindow in the completion list

Check to see that you have #include <QLabel> and <QMainWindow> at the top of your file (wait a few seconds until the change is detected). If you already had those things (or if that doesn't fix it), let me know what system you are on and I'll try to reproduce. This completion works fine for me on Windows...

Incidentally, there are other issues with code completion that I am aware of and will be addressing, (such as local variable declarations with comma-separated variables).

Cheers

[sunil.thaha]

Have you discovered that you can double click on a keyword to get a list of tags for that word... then double click a list item to navigate... I find this very useful, and soon there will be a "back" button.

Keyword : You mean if, else, do, while ... ?

Well I tried double clicking on everyword i could find but did not find anything happening . Can you make it clearer :-)

Check to see that you have #include <QLabel> and <QMainWindow> at the top of your file (wait a few seconds until the change is detected). If you already had those things (or if that doesn't fix it), let me know what system you are on and I'll try to reproduce. This completion works fine for me on Windows...

That worked !! Maybe, I hadn't given enough time.
But ... Even without including the header files, wouldn't you like to have the completion working? Anyway a work around for that is to include QtGui and later comment it out