GiuseppeC: my question is - whatever you try to develop - why would you choose R3? Original R3 GUI (Carl's version) is non-finished, hence gone. As for Saphirion, I might be mistaken, but - their tools are still mostly R2 (custom RebGUI based?). I wonder, development wise, when, for the last time, whoever touched R3 GUI at all? I don't want to provide wrong assumption here, it is just how I understand the situation, of course lacking any internal information. Henrik e.g. found GUI quite complicated and wanted to start new GUI effort. Does Cyphre work on R3-GUI? Not sure, but I doubt it.
Asfor other R3 efforts - Atronix guys have their own View version, it seems to be OpenGL accelerated. Not sure R3-GUI is going to work with their View version. HostilFork and his Ren-C - he's not much interested in GUI at all, but he kind of cooperates with Atronix and guys are considering switching to Ren-C R3 variant.
So - for me, GUI wise, I would consider 3 options - R2, Red, Ren-C - whatever guys come-up with ...
Pekr, I am concentrating on R3-GUI Saphirion version as it is an evolution/change from CARL R3-GUI. So we Have R2, RED, R3-GUI Saphirion.
Also I don't know where to find ANY info about atronix accellerated opengl version, or ANY R3-GUI Saphirion chances since 2013-4 as they are no published anywhere.
As for Atronix - their GUI might not be VID anymore. As for their View engine, I think, that in the end, they might release it, dunno though. You would have to ask them ....
I already have this link but I don't know if the GUI system has been advanced internally and not updated on GitHub.
If anyone from Sapphirion is listening they could clear any doubt to the community.
I'm listing... and I will repeat what I have said a couple of times.
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 ?