One typical question I am asked regularly about Creative Docs .NET is:
"when do you intend to release the GUI code?"
Every time, I am sad to have to reply "not yet". There are several reasons I see for not yet releasing our code:
I don't think the GUI features are stable enough; releasing the code means I'll have to commit to some backward compatibility. For now, I prefer to remain free to change anything without breaking code which does not belong to me.
There is no documentation whatsoever.
I don't know where to find the time to answer the questions which are bound to pour in as soon as other people start using the GUI code. And I can't simply reply RTFM...
The GUI code is very tightly bound to the rest of our framework. Releasing the GUI code would also require me to release almost every piece of code on which Creative Docs .NET is built.
...ah well, and there is also the fact that I have to get our management's approval first .
This blog has been quite quiet for since May. It is not because we consider Creative Docs .NET to be perfect now; oh no, surely not. No, we are simply very busy with some parallel developments which require all our attention. I'll blog about them as soon as we have something to show, I promise.
Internally, we have a new version of Creative Docs .NET which uses an upgraded GUI framework and is now based on .NET 2.0, making extensive use of the new generic collection classes and other interesting features. Externally, however, nothing significant has changed for the user; under the cover, thousands of lines of code were refactored in order to make the user interface serializable and editable with an interactive designer, allow data binding, etc.