Not quite yet but it's quietly spreading : several open source projects have switched to using QCodeEdit lately, which is quite encouraging and will ensure a better QA as it will imply more tests and various configurations and more feedback. Here is a list of those I have heard of thus far :
I'll try to add screenshot of these to the gallery which already holds a couple of screenshots from the example. |
|||
After about three weeks of somewhat irregular work I hereby announce the availability of QCodeEdit 2.2.2 Nothing really fancy in this release which mostly focused on bugfixing and polishing but still a couple of new features that may make QCodeEdit more appealing/easier to use : UI to configure formatting (those familiar with KWrite/Kate will recognize the design) and a designer plugin. There is a lot work in progress but no schedule yet for the first 2.3 release. Stay tuned though, I might blog about some of the upcoming improvements sometimes. |
|||
During QCodeEdit 2.2 packaging process, some late fixing was done and a couple of platform-specific regressions were introduced. Hopefully, thanks to testers, and particularly to Benito van der Zander, developer of TexMakerX, they have been spotted and fixed less than 24 hours after the release. As a result, new packages are now availables. Enjoy and stay tuned, for more is coming. |
|||
A lot of time has passed since last release. And a lot of things happened in QCodeEdit. Despite all the improvements previously mentioned, it still wasn't enough... So, several years after it was first requested, a new feature finally made it into QCodeEdit : code snippets. Strictly speaking they are not yet part of the library but the infrastructure is ready and a simple yet convincing implementation is provided in the example/demo program which can easily be reused in other programs. QCodeEdit is now being used by several open source projects, which helped a lot making the API more mature and spotting bugs. As a result QCodeEdit 2.2 is way better than the previous releases, both in terms of performance, features and QA. What's more? Docs are coming to life. Lots of effort has been put in doxygen comments and writing some tutorials. The documentation can still be improved (and will be) but it is a |
|||
