Handcoder's IDE for Qt

[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

[elcuco]

I downloaded and compiled 0.1.14, and found some problems.

* I see no icons. Only the close button.
* The doxygen documentation gets borked, since it uses an external css. Which QTextBrowser does not load. There are work arounds, I hope you find them.
* I am not sure why, but the doxygen documentation I see on the Project Reference tab is not the same I get when I run the doxygen command.
* Some sub projects are not loaded.

I used qmdilib for my test, it's available on qt-apps.org.

Looks sweet, great ideas. Implementation is kinda flawky, but this will get fixed in a version or two.

[magland]

I downloaded and compiled 0.1.14, and found some problems.

* I see no icons. Only the close button.

I had this problem also on Linux. To fix this go to src and run rcc on HiQt.qrc to re-generate qrc_HiQt.cpp -- not sure why it's not getting auto-generated during make. I'll look into it.

* The doxygen documentation gets borked, since it uses an external css. Which QTextBrowser does not load. There are work arounds, I hope you find them.

I'll look into it.

* I am not sure why, but the doxygen documentation I see on the Project Reference tab is not the same I get when I run the doxygen command.

I use the Doxyfile in the src/templates/Doxyfile, which you can configure to your needs. I suppose I should give the user the option to select an alternate Doxyfile. Just be aware that HiQt will modify certain key Doxy-parameters, such as INPUT.

* Some sub projects are not loaded.
I used qmdilib for my test, it's available on qt-apps.org.

I'll take a look.

Looks sweet, great ideas. Implementation is kinda flawky, but this will get fixed in a version or two.

Thanks, and hang in there. Your feedback is invaluable

[elcuco]

A few other questiosn/suggestions:
* Another tip for doxygen: If in the root directory of the project, there is a "Doxyfile", use that instead of your template.
* The dependency viewer - make it a dock window. This way I can put it on the GUI and still look at the source. (great idea BTW)
* The help dock is way to wide. It takes up too much space, cannot br shrinked, and it steals space from the code editor.
* The code editor has way to much "bold". Just a rant, feel free to ignore it.
* I don't understand what does the "build with runtime tools" does.
* I would like to have an option to modify the tab width (you set it to 2, and I like it 8 or 4)
* Incremental search is a must. Poping dialogs just distracts me from the text. Move on, it's 2007, not 1997.
* dot was not found on my system by default. Just writing "dot" was enough for me to get it working.
* I would like to have the option to export the dependency graphs as images (to send people email with text like this "look, you project sucks bug time, look at this").

[magland]

Thanks, great suggestions.... Regarding "build with runtime tools", that allows you to see a tree of objects/widgets in your project via QObjectBrowser. I forgot to check for this, but to use it, you must set as your active project a project of type "template=app".

* dot was not found on my system by default. Just writing "dot" was enough for me to get it working.

Do you mean that "dot" WAS found on your system, or not?

A few other questiosn/suggestions:
* Another tip for doxygen: If in the root directory of the project, there is a "Doxyfile", use that instead of your template.
* The dependency viewer - make it a dock window. This way I can put it on the GUI and still look at the source. (great idea BTW)
* The help dock is way to wide. It takes up too much space, cannot br shrinked, and it steals space from the code editor.
* The code editor has way to much "bold". Just a rant, feel free to ignore it.
* I don't understand what does the "build with runtime tools" does.
* I would like to have an option to modify the tab width (you set it to 2, and I like it 8 or 4)
* Incremental search is a must. Poping dialogs just distracts me from the text. Move on, it's 2007, not 1997.
* dot was not found on my system by default. Just writing "dot" was enough for me to get it working.
* I would like to have the option to export the dependency graphs as images (to send people email with text like this "look, you project sucks bug time, look at this").

[magland]

You can track the progress on the suggestions for HiQt here:

http://www.math.upenn.edu/~jfm/todo.html
(temporary site)

Send more feedback/requests, and I'll add to the list.

[magland]

Pleased to announce:
HiQt Version 0.1.15.c

Lots of new features and improvements.
One in particular is improved code navigation... a very useful "back" button, you'll have to see it in action.

[Pepe]

I know that HiQt requires Qt 4.3 to run, but can it be used to develop applications that use a lower version of Qt?

I have installed Qt 4.2.3, but I copied the Qt 4.3 dlls to the HiQt bin directory, so HiQt runs. Now I set the paths to Qt 4.2.3 directories (qmake, designer...) but the class browser doesn't work, even the path to ctags is correct.

I see this warning in console:

Unable to open documentation file: "C:\Qt\4.3.0\doc/html/qt.dcf"
Error reading documentation file: "C:\Qt\4.3.0\doc/html/qt.dcf"
QTextBrowser: Cannot open 'index.html' for reading
QTextBrowser: No document for index.html

I don't see any option to set the documentation path.

[elcuco]

That is because the GUI uses the path of the library to determinate the location of the docs. Funny, I never tought of your problem.

[magland]

I know that HiQt requires Qt 4.3 to run, but can it be used to develop applications that use a lower version of Qt?

I have installed Qt 4.2.3, but I copied the Qt 4.3 dlls to the HiQt bin directory, so HiQt runs. Now I set the paths to Qt 4.2.3 directories (qmake, designer...) but the class browser doesn't work, even the path to ctags is correct.

I see this warning in console:


I don't see any option to set the documentation path.

Thanks Pepe I'll fix that problem.

[elcuco]

Another configuration path, with default to the path of the Qt librarry running...?

[magland]

Edit: see next post*

Pepe, I reproduced your problem on my system, and I will fix it as elcuco suggests. However I am confused when you say "the class browser doesn't work"... it seems to work fine on my system even when using 4.2.1. Could you explain... do the classes just not appear? ... and are you using HiQt 0.1.15.c?

I know that HiQt requires Qt 4.3 to run, but can it be used to develop applications that use a lower version of Qt?

I have installed Qt 4.2.3, but I copied the Qt 4.3 dlls to the HiQt bin directory, so HiQt runs. Now I set the paths to Qt 4.2.3 directories (qmake, designer...) but the class browser doesn't work, even the path to ctags is correct.

I see this warning in console:


I don't see any option to set the documentation path.

[magland]

Pepe, disregard my last reply... I was able to reproduce the problem with Qt 4.2.x... no class/file browser... . This has to do with the "qmake-HiQt" component. The problem is that qmake-HiQt.exe is seeing your 4.3.0 .dlls as well...

I'll have this fixed in the next release (2-3 days).

Thanks for bringing it to my attention!

[magland]

Okay Pepe, here's the workaround for now:

Simply copy your mkspecs and doc directories from c:\Qt\4.2.3 to directories called c:\Qt\4.3.0\mkspecs and c:\Qt\4.3.0\doc. This should do the trick and work perfectly.

Let me know...

I know that HiQt requires Qt 4.3 to run, but can it be used to develop applications that use a lower version of Qt?

I have installed Qt 4.2.3, but I copied the Qt 4.3 dlls to the HiQt bin directory, so HiQt runs. Now I set the paths to Qt 4.2.3 directories (qmake, designer...) but the class browser doesn't work, even the path to ctags is correct.

I see this warning in console:


I don't see any option to set the documentation path.

[Pepe]

Simply copy your mkspecs and doc directories from c:\Qt\4.2.3 to directories called c:\Qt\4.3.0\mkspecs and c:\Qt\4.3.0\doc. This should do the trick and work perfectly.

Yes, that works, thanks.

Anyway I hope you can fix it the right way. Otherwise this problem could arise if you later decide to distribute a stand-alone binary package (with Qt dlls or statically linked).

I have other suggestions, for the settings dialog (Tools->Settings):
- it would be nice if you add some "select..." buttons so the user could choose the paths in a file dialog, instead of having to type the paths.

- as it seems that ctags.exe, doxygen.exe and dot.exe are included in your package, I think the default path for them should be relative instead of absolute. This way the paths will be correct after an update.

I explain: you install HiQt 0.1.14 in c:\HiQt-win-0.1.14 and run it for the first time. HiQt creates default paths for that programs (which are right). But then you upgrade to 0.1.15 installing it in c:\HiQt-win-0.1.15 (and delete the folder with the previous version). Now the paths for ctag.exe and others are wrong. They point to the old folder, so the user has to change them manually.
If the default paths were "..\3rdparty\ctags\ctags.exe" and so on, that wouldn't happen, they will keep working between upgrades.

I have another problem: I can't compile anything. It says that it can't find g++ (it's not in the path)

And one question: where are the files created by doxygen saved?

[magland]

Thanks for the comments and suggestions. I'll make those changes for 0.1.16, couple days. Regarding finding g++, you need to add MinGw\bin to your path... but I think I should make some kind of configuration option for this as well. Overall the configuration dialog will be improved.

Yes, that works, thanks.

Anyway I hope you can fix it the right way. Otherwise this problem could arise if you later decide to distribute a stand-alone binary package (with Qt dlls or statically linked).

I have other suggestions, for the settings dialog (Tools->Settings):
- it would be nice if you add some "select..." buttons so the user could choose the paths in a file dialog, instead of having to type the paths.

- as it seems that ctags.exe, doxygen.exe and dot.exe are included in your package, I think the default path for them should be relative instead of absolute. This way the paths will be correct after an update.

I explain: you install HiQt 0.1.14 in c:\HiQt-win-0.1.14 and run it for the first time. HiQt creates default paths for that programs (which are right). But then you upgrade to 0.1.15 installing it in c:\HiQt-win-0.1.15 (and delete the folder with the previous version). Now the paths for ctag.exe and others are wrong. They point to the old folder, so the user has to change them manually.
If the default paths were "..\3rdparty\ctags\ctags.exe" and so on, that wouldn't happen, they will keep working between upgrades.

I have another problem: I can't compile anything. It says that it can't find g++ (it's not in the path)

And one question: where are the files created by doxygen saved?

[magland]

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

* Support for developing with previous versions of Qt. (Pepe, see readme.html.)
* Improved configuration dialog.
* Save Doxygen-generated documentation to file.
* Significantly reduced compilation time (qmake-HiQt trimmed way down)
* Others...

[magland]

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 :-)

Sorry about that, I didn't mean "keyword" I meant "tagword"... try double clicking on a word that is the name of one of your project's classes or functions... this should bring up the navigation window with a list showing where that tagword was declared and/or defined. The tag words should actually be highlighted bold in your code.

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

Now that you mention it, globals, such as "QMainWindow", should appear always, regardless of #includes, -- can you double check that -- perhaps you just need to wait until tags are done being updated - see status bar. It's the non-globals, e.g. QMainWindow::addToolBar() that depend on the #includes.

I can certainly add an option to complete everything regardless of whether or not it's visible from the current file... that would actually be easier than current functionality. However, I like using it the way it is because it reminds you to add the #includes when the code completion is not working... also it's better in the sense that code-completion will always work the same for the given file, independent of which other files have been opened.

[sunil.thaha]

I can certainly add an option to complete everything regardless of whether or not it's visible from the current file... that would actually be easier than current functionality. However, I like using it the way it is because it reminds you to add the #includes when the code completion is not working... also it's better in the sense that code-completion will always work the same for the given file, independent of which other files have been opened.

Well I use the classes and compile the project, When i get errors I include the headers.
If I use HiQt I will see if the methods get auto-completed if not, I have to include them...
That is fine. I don't know how others use it. :-)


Feature Requests:

1. Code folding and unfolding
2. Line numbers & Goto Line number
3. When the default intend mode is using space; lets say 4 spaces, then when I am at 4th column; pressing backspace needs to delete the 4 spaces and get me back to the first column. this is exactly what Kdevelop does and is quite intuitive

Exactly like what kdevelop does.