R3 is not used by us for anything serious at the moment.
R3-GUI was a test and prototype to see how far we can get with Carl's R3 base and some small changes.
The main reason is, as correctly stated, our main product is still R2 based.
So, a technology migration is necessary at some point.
I'm not very confidenet that we will choose R3.
On the other hand, the work we did with R3-GUI is pretty general and the concepts, internals etc. can be used with other technologies like Lua etc. Hence, for us it wasn't a sunk investment.
So, the best you can do with R3-GUI is: Use it and develop it further, read the source and examples.
You have to work your way through it, but there should be enough information available to make it.
It's far from finished and building a good, tested, documented and feature rich GUI framework is something you should expect to take between 6 - 18 months of work. After 6 it's useable (that's what R3-GUI is now), after 12 you can start building apps on it and after 18 around 80% if it will be matured.
Hi Robert, thank you for the answer. I supposed R3-GUI was a complete product. Personally, I'll do what you suggest: I'll use it, read the code an the examples. It seems a good work and I don't see any reason for not adoping it.
Are you and your team available to help me/us navigate throught code/structures not so easy to understand to us ?