QCodeEdit

[Usability]

Just checked : it works perfectly for me try updating your working copy and/or rebuilding your app... If it still doesn't work please send me some more details and I'll investigate this.

It turns out I broke the folding in the fixes I made to get it to compile on MSVC6, which does not allow void functions to return data. I will have to look at this more carefully, perhaps the correct change would have been to change the declaration of the function.

Anyway, false alarm. There is no problem with the folding, sorry to waste your time on that.

[fullmetalcoder]

Despite the long silence QCodeEdit development has not halted. Actually those of you who tried Edyuk latest releases have seen it at work and probably spotted some of the most noticeable improvements.

Anyway I got two things to announce right now :

• QCodeEdit now has a website up and running
• QCodeEdit 2.1 is available for download

Hoping you'll like both.

[fullmetalcoder]

I'm still working on QCodeEdit and a new version will be available shortly but I'd like some more testing of the latest feature I've added as it was particularly hard to get it working fine and fast without breaking anything :

QCodeEdit now has dynamic line wrapping (it does not honor word boundaries but it works)

Lots of fixes and improvements have been made since last version so you are encouraged to try out the latest SVN version. If no bugs are found a new package will be released soon.

regards

[lorebett]

Hi

just for information.

I came across this post while trying to solve a problem with QSyntaxHighlight which does not seem to provide access to the current QTextBlock; at the moment, I'm trying to implement source-highlighting in Qt4 (and also Qt3) text editor by relying on GNU Source-highlight (http://www.gnu.org/software/src-highlite/), since I'm turning it also into a library; GNU Source-highlight uses its own syntax for language definition files (I don't like XML), which is powerful enough to deal with possible nested states.

I'll take a look at QCodeEdit since it looks like it provides a better QSyntaxHighlighter.

Do you think using GNU Source-highlight might help your editor too?

[fullmetalcoder]

Thanks for the information. I gave a look to GNU source highlight. While I agree that XML may not be the most appropriate language for syntax files I don't like the format used by GNU source highlight (both a matter of taste and implementation related considerations).

Theoretically it would be possible to either integrate GNU source highlight into QCE or provide support for these syntax definitions using the existing internals I am not willing to do it myself (though I would welcome any such contribution).

Now some updates about QCodeEdit :

• dynamic line wrapping works fine now (apart from bugfixes it means that it DOES break at word boundaries whenever possible and that cursor movement became more intuitive within wrapped blocks of text)
• Lots of API has been added after user requests (there five projects that I know of currently using QCodeEdit )
• formatting has been improved
• there have been some significant speed improvements in drawing

Future plans include:

• encodings support (WIP)
• session management API
• more configuration options (especially GUI for changing formatting)
• and a couple more exciting things (but in a slightly more distant future )

[lorebett]

Thanks for the information. I gave a look to GNU source highlight. While I agree that XML may not be the most appropriate language for syntax files I don't like the format used by GNU source highlight (both a matter of taste and implementation related considerations).

could you expand on this?
any feedback is more than welcome

[fullmetalcoder]

Well, it is not very syntactically consistent (at least it does not look so). Also the syntax looks more script-ish than just descriptive (that is just a matter of taste I suppose). That's about all I can say after quickly reading the C syntax file, hope it helps.

[Usability]

I just pulled the latest revision of this editor and notice that it now detects external changes to the file, which is great.

Unfortunately its indicating a conflict event even if the file is not changed in qcodeedit2, so there is no conflicting changes.

In my opinion it should silently reload in this scenario, and save the nice conflict resolution queries it does for the occasions where there are unsaved edits.

[fullmetalcoder]

your remark make a lot of sense. I'll make the needed changes ASAP.

[Usability]

Another thing I noticed is some odd interaction between the horizontal scroll bars and the status line. If an editor window is opened on a wide file so that the horizontal scroll bar is needed from the moment the window is created, then the status bar is garbled. See the attached image.

If the window is then resized a modest amount the problem remains. If its resized to the point where the scroll bar is no longer needed, the status bar is drawn correctly. If the window is then shrunk again so the scroll bar reappears, this time its inserted correctly. So the problem is only there if the scroll bar is needed as the editor is opened.

The screen shot came from the example editor app invoked like this.

example/example example/window.cpp

If you need further help reproducing this let me know. I am using bulid 770 from
svn checkout http://edyuk.svn.sourceforge.net/svn...rty/qcodeedit2

[fullmetalcoder]

This is a problem I've been struggling with for quite some time. It appears that some versions off Qt need the position of the widgets placed inside viewport margins to be offsetted when scrollbars are visible and some don't. The issue being that I have not yet managed to determine how each version (and platform?) behave so as to use some macro tricks to get rid of that annoyance.

[Usability]

More seriously, when I move the horizontal scroll bar with the latest version of qcodeedit2, the application freezes. Have you seen anything like this before?

It doesn't seem to affect the example editor, just my app. However when I switch back to the last bulid of qcodeedit2 I was using the problem goes away.