It's been more than a month since Edyuk 1.0.1 was released. Thanks to the feedback I have been able to polish many of the rough edges left, fix all the bugs that have been reported thus far and to add a couple of new features. Edyuk 1.1.0 is not ready yet but its time is coming soon. Despite my busy schedule I will probably be able to respect a two monthes release cycle once again.

 The very purpose of this release is to reach the state where Edyuk is fully usable on a daily basis by any programmer. This means good usability and enough features but by no means perfect usability and every possible features. There may still be some small issues in it and there will always be room for new features but I'm quite satisfied of what I've done so far. 

 Here is a list of the new features and noticeable improvements in of existing ones :

• it is possible to change the display mode of the "Manager" dock, as requested on Sf.net tracker (three possible choices : tabs, toolbox and combo box)
• added UI form preview from the project manager (independent from Designer integration)
• added a simple way to create subclasses of UI files from the project manager with easy selection of slots to create
• qmake projects are now displayed by default using "flat" variables (no more HEADERS and SOURCES folders cluttering the tree) but you can change that if you prefer the old display mode
• Proper line endings management has been added. Line endings are not preserved by default.
•  Added the "swap header|source" action to the "search" menu to make it visible.
• Much improved class browsing by adding some line endings informations that allow more accurate jump from class tree to source files. uic-generated files are no updated properly even if they have been created after opening the project.
• Reworked the build engine to allow much better build mode and exec target management. Advertised build modes are now ALWAYS valid. Build mode and exec target choices are preserved when switching from a project to another. More sensible choice for default exec targets.
  
• Better coordination between build engine and debugging engine and more feedback to the user in case of troubles to improve the general debugging experience

And of course some bug fixes (not exhaustive) :

• segfaults in GDB plugin when the selected debug target was considered as debuggable by GDB (but in assembly mode, not C++...)
• the class tree was not properly updated when a file was deleted or removed from a project, which could result in segfaults when code completion made use of these symbols
• auto save had some issues and was not very user friendly (can still be improved).
• fileOpen() always returned a null pointer which in turn made it impossible to properly jump to a symbol when the file was not open yet

A couple of things left to do before Edyuk 1.1.0 may be released (all the above are available on SVN) :

• Make it clear which project is active by using a bold (or any other formatting that will clarify things)
• Make it possible to change the actve project using context menu (the combo box really isn't intuitive...)
• Fix the "rebuild all" action for subdirs (more a workaround qmake/make limitations than a real fix but still...)

And of course I'm not anywhere near the end of it. There are loads of things left to do (or rather, things that could be interesting) :

• a proper encodings support
• add methods/members/... directly from the class browser
• export the class tree of a project as UML
• provide diff view when a "conflict" is detected (a file beingedited has changed on disk)
• a better template system which would make use of QWizard to allow more complex things such as class creation
• VCS management
• support for other languages that have Qt bindings and generally speaking a wider set of syntax definition files
• better user docs with tutorial, screenshots, ...
• ...
  

Some things are obviously more likely to get done in a near future than the others, especially considering ly busy schedule, so if any of these is important for you or if you just want to scratch a itch by working on it please feel free to do so and contribute some code. While I won't be able to do much actual coding I can find time to answer any questions you may have about Edyuk architecture, coding standards, etc...