Hi Jaco,

Thanks for your response. I understand your point exactly since I'm in the same situation more or less. I've read through the pages of documentation on QCodeEdit and to be honest I'm have a few questions still. I hope you don't mind if I ask them to you. Maybe just some background on what I'm doing:
Feel free to ask, that's the purpose of this list ;)
I want to use QCodeEdit as the input to different scripting backends. One would be QtScript and later a Python backend will follow. For the QtScript backend I use a the script editor that comes with GCF (not sure if you are familiar with it: www.vcreatelogic.com/oss/gcf/index.html). In any case, since they don't have plans right now to make the editor more generic I'm looking for something else. The project consists of different GCF components built on top of a scientific framework.
The funny thing is that I have been contacted by the author of GCF monthes ago because he was interested in using QCodeEdit. Apart from that I am not
particularly familiar with GCF.
1) Will it be relatively easy to use QCodeEdit in a console type of mode? Like the Python console for example.
QCodeEdit is not designed to work in a console-fashion but it should be relatively easy to tweak it to achieve that.
Here is a path I can see to achieve that :
* subclass QEditor
* lock all the lines for writing except the last one(s), supposedly the "command line(s)" (easy but requires some new features (so more work from me but it is not a problem)
* reimplement a bit of key event handling so that pressing enter send the commands typed thus far (easy as well), lock previous lines and add a new "command line"

Now I may even consider doing most of that work to have a QConsoleEditor class or something akin part of QCodeEdit as it may be useful to others.
(not part of the plans atm, just mentioning the possibilities)

2) Do you have a roadmap for QCodeEdit?
Yes but I have not published anything.

A quick overview of things to come :
* general performance improvements (loading of big files)
* general memory usage improvements (again, most noticeable for big files)
* builtin sessions support (list of files, cursor positions, edit history, ...)
* snippets ala TextMate (WIP as can be seen in the demo app already)
* improved and simplified input bindings mechanism
* PyQt support
* and some more in somewhat distant future

There is however no strict schedule as I will be extremely busy in the monthes to come (until july at least).

3) Does buying a LGPL license or whatever include support from your side.
Support and updates come with the license if you want it (if you don't want it the price is a bit cheaper though)

4) Can you give me an idea of a price for QCodeEdit.
Classic license schemes range from 200 to above 1000 depending on the options (the more expensive being
BSD license with possibility to freely redistribute the source in BSD form, updates and support unlimited in time).

This "classic" schemes is more suited for companies than individuals though so it can be adjusted in cases like
yours, especially since you plan to use a dual-licensing scheme. In this particular case by the way a pricing
scheme would probably fit better : you don't pay me anything at first and when you get customers we share the
benefit of your sales (you would get a greater percentage of course) or you use the money of your first sales
to pay for a classic license or you don't pay anything yourself but your customers would have to buy a QCE
license on their own (probably not very attractive...).

best regards

luc