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 .
Most of the graphics code is indeed based on AGG, but a thin layer still exists both in the native Win32 DLL (which implements the AGG functionality I use) and in the managed DLLs which sit on top of it. What would require most work is probably the event handler which is currently based on Win32 event messages, available through WndProc. I doubt that mono emulates WndProc well enough for the GUI layer to work.
i would like to make a gui like qt/embed using anti-grain geometry and the linux framebuffer.
This is something the wxWidget wxUniversal WxEmbed community would really appreciate because qt is not free.
The same for the mono community because they currently draw the system.windows.form using cairo wich is only a frontend for gdi+ and x11.
we can make cairo use Anti-grain geometry as backend but it would be too much work for noting.
i found http://www.opac.ch/opac/oldies/ but not exactly what i was looking for.
i seen the gui you use at http://www.creativedocs.net/devs/gui and it is exactly what i wish.
i know your gui code isn't documented and that you wish to be free to change anything
and dont wan to help with other people project using it.
i am happy with that cause i will make my own fork.
And i will support myself using only what you wish give.
if only you wish to realease the code on any license you wan.
you said ...
>> I doubt that mono emulates WndProc well enough for the GUI layer to work.
they already have a working system.windows.form based on cairo i dont know how they manage WndProc but it work.
What i wish is only to replace the current system.drawing implementation made using cairo by one using AGG.
i dont need all of your widget toolkit.
only your .net warper for agg that you use to draw the widget.