HaiQ - IDE for Qt4

[magland]

HaiQ 0.2.0 for Windows released

Handcoder’s IDE for Qt is now known as “HaiQ”, and version 0.2.0 for Windows has been released.

The software has been improved substantially, thanks in large part to feedback received from this forum, as well as the addition of a very talented Stephan Tiltz to the development effort! Please continue to provide us with bug reports, and feature requests.

The Windows version has been fully tested, and ready to use, binary out of the box. Linux version compiles cleanly, but needs some testing (download and compile the win32 source code).

Some key features:

Stability
For all downloads of HiQt and HaiQ, we have received only one report of a crash - it was fixed within a day. Providing a crash free IDE is highest priority.

Project Parsing
HaiQ is fundamentally different from other IDEs for Qt4, including Visual Studio and KDevelop (AFAIK), because it treats the project (.pro) file as source code. Users maintain this file, just as they maintain any other source file. HaiQ detects changes to the project file in real time, updating the file/class browsers and everything. Loading of .pro and .pri files is 100% accurate because it uses a modified “qmake” to do the parsing. HaiQ will never write to your files without an explicit request to do so.

Integrated documentation browser
Press F1 on a Qt keyword in your source file to bring up the corresponding help doc.
Also, generate integrated documentation for your project (uses Doxygen).

Code completion
Nothing too fancy. Reliable, accurate, and fast.
The accuracy of code completion has been improved, and an option has been added to auto-complete upon typing left parenthesis.

Code navigation
Double click a word in your source file to bring up a list of tag locations – places where that class or function was declared, defined, etc. Backward and forward buttons to navigate code.

Preferred file list
Maintain a list of preferred files for your project for convenient access.

Editor
New editor features include optional line numbers, braces/parenthesis highlighting and an assistant-style search panel.

Regarding interface to QScintilla, we decided to hold off on including this with version 0.2.0. The only feature in our QScintilla module that is not presently included in our QTextEdit-based module is code folding. While useful, we did not feel that this was worthy of requiring dependency on the QScintilla library, especially in light of some limitations we found with the QScintilla API. Eventually, QScintilla editor component will be released as an optional plugin.

Customizable new project templates
Start a new project by choosing from a collection of basic new project templates, or easily create your own template.

HaiQ S.T.U.F.F.
The priorities for HaiQ, in approximate order of importance are:
* Stability = no crashes
* Transparency = open your .pro files without fear
* Usability
* Flexibility
* Functionality

Therefore, we consider seriously before adding features. That is, we add functionality when the program is ready, and when it will not take away from the other priorities (stability, transparency, usability, flexibility). For this reason, we removed one component from the program (QObjectBrowser), but expect it to return in a future version when time is right.

I hope you enjoy the program!

[sunil.thaha]

Kudos to the team behind HaiQ. !! Once again great work guys

Now is the time for Bugs
1. Line numbers starts from 0.
2. When there is an error in compilation, going to an error opens the same file in a new tab. After you edit the file, a message box pops up asking you to relaod, the file that was modified. Now the solution would be to see if the file is already opened, if so show that tab.

Feature Request.
1. Reposition the tab. Drag the tab and put it else where
2. Mark a tab as readonly.
3. Split window, where you can split a tab.
4. Shortcuts to move to next/previous tab ( Alt+[Left|Right] arrow )

[magland]

Kudos to the team behind HaiQ. !! Once again great work guys

Now is the time for Bugs
1. Line numbers starts from 0.
2. When there is an error in compilation, going to an error opens the same file in a new tab. After you edit the file, a message box pops up asking you to relaod, the file that was modified. Now the solution would be to see if the file is already opened, if so show that tab.

Feature Request.
1. Reposition the tab. Drag the tab and put it else where
2. Mark a tab as readonly.
3. Split window, where you can split a tab.
4. Shortcuts to move to next/previous tab ( Alt+[Left|Right] arrow )

Thanks for your feedback, sunil.thaha. I assume you are running HaiQ on Linux... (we have not seen these problems on Windows).

We are aware of the offset in line numbering, and will solve that problem. I was not aware of the problem with opening two versions of same file. This must be caused by the file being represented in two different ways, e.g. "/foo/file1.cpp" and "/foo//file1.cpp" or something like that. You can confirm this by clicking on the tabs and looking at the full paths displayed on the main window title bar.

If this is indeed the case, adding the following line of code and recompiling should fix the problem:

In src/HaiQWorkspace.cpp, function: HaiQWorkspace :: open_file, add the following single line at the top:

fname=canonical_path(fname);

fname=canonical_path(fname);

To copy to clipboard, switch view to plain text mode 

Incidentally, it is important not to use "QFileInfo::canonicalPath" here because of multiple thread issues. Let me know if it solves the problem.

Your feature requests have been added to the todo list.

[sunil.thaha]

Thanks for your feedback, sunil.thaha. I assume you are running HaiQ on Linux... (we have not seen these problems on Windows).

Well, I have a bad news . i am indeed using HaiQ on Windows. I have downloaded the windows binary instead of the source code. Nevertheless I expect to see the same even if I have compiled the source code -right?

[magland]

Well, I have a bad news . i am indeed using HaiQ on Windows. I have downloaded the windows binary instead of the source code. Nevertheless I expect to see the same even if I have compiled the source code -right?

Windows, eh? Can you do a favor and reproduce that problem with duplicate editors and look at the main window title bar as I described in previous post? If the path strings are slightly different, then it should be easy to fix. Line numbering will be fixed soon.

[sunil.thaha]

More Bugs:
1. The line marked as a syntax error ( red color) is not cleared even if the error is corrected

More Feature Requests
1. Automatically save files before compilation
2. Facility to open multiple files using the Open file Dialog

[magland]

sunil.thaha:
Pls download the updated version.
The first two issues you brought up should be resoved, i.e. line numbering and opening same file twice.

More Bugs:
1. The line marked as a syntax error ( red color) is not cleared even if the error is corrected

HaiQ should clear all red markers upon compilation - let me know if this is not the case.

More Feature Requests
1. Automatically save files before compilation

HaiQ should already be doing this.

2. Facility to open multiple files using the Open file Dialog

Noted.

[QTmplayer]

Once again: Nice work!

There's only one thing left with the completion on left parenthesis. If this option is activated the parameter info tooltip does not show up. This works well when the option is deactivated.

Regards
QTmplayer

[magland]

Once again: Nice work!

Thank you, QTmplayer, I hope it's useful for you.

There's only one thing left with the completion on left parenthesis. If this option is activated the parameter info tooltip does not show up. This works well when the option is deactivated.

Thanks, I had overlooked that detail... it's a one line fix. You can either wait until the next patch or release, or you can fix it yourself, if you want to compile from source:

Add the line indicated below in src/HaiQWorkspace.cpp

if ((event.key()=='(')&&(complete_code_on_paren)) {
	m_completion_window->process_key(event.key());
	interface->insert_text("(");
	slot_function_hint(); ///add this line /////////////////////////
	return;
}

if ((event.key()=='(')&&(complete_code_on_paren)) {
	m_completion_window->process_key(event.key());
	interface->insert_text("(");
	slot_function_hint(); ///add this line /////////////////////////
	return;
}

To copy to clipboard, switch view to plain text mode 

Easy fix = sign of a well-designed program

[magland]

Next version of HaiQ has an integrated debugger (interface to gdb) and code formatting tool that uses Artistic Style (http://astyle.sourceforge.net).

But it needs testing. Who can try it out? (send email)

[sunil.thaha]

More Bugs.

1. Highlighting ... try
1.a. Highlighting #include <QstTest.h>
1.b. #define TEST() Class* test() { QST_MACRO_GETS_HIGHLIGHTED_WRONGLY(); blah(); }

2. Bug: Clear the syntax error indicator upon compilation, This doesnot happen all the time :-(

Feature request
1. Completion: if there is only one possible word in the completion list, why popup, instead, can't we complete it... Further, you could provide an option like the auto complete on '(' to toggle the feature on or off