WARNING: longer text ahead @-)
from the perspective of a relatively new user (i.e. my perspective O:-) ) I wanted to share a few thoughts about Gideros and maybe get your opinion and suggestions on them. First, I tried various engines and frameworks before settling with Gideros and I really like what it offers. I think the balance between structure provided by the engine and openness for your own code is really great. The API is relatively small so it is really easy to actually find your way around. However, to be honest, it took me a little while before deciding to actually invest some time into it. The reason is mainly the way Gideros presents itself to the newcomer. Now that I am here, I realize that the community is rather small and this makes me appreciate the amazing work that the maintainers do even more. However, this probably comes at the expense of the presentation, namely the website and documentation. ATM, it is really difficult for a new user to gather information. I stumbled upon sites with documentation of features through links in the forum and I could never find it again because it was not reachable from the website (at least I could not find it...). Many things in the Tools section are outdated, I am not sure about the Developers section, some seem to be spam, some probably dont exist anymore etc... But what I think is more important is the lack of a concise documentation for many things. Looking in the forum for information that is 4+ years old does not give confidence to a new user I think (although of course, most of that information is still accurate which speaks for the robustness of the engine, but still... it is all over the place)
So, you probably discussed that a lot already, but I was thinking about possible future directions. These are only thoughts but I would really like to hear your opinions on the topic.
First, it seems that the way the website is built is a heritage of the commercial past of Gideros. Now that it is open-source for some time now, I wonder if the way the information is organized could reflect that. For example, many engines successfully use Github not only for hosting the software but also for documentation. ATM, the wiki there contains only two empty tables of content. Maybe this could become THE central hub for Gideros information. The main advantage is that it would make contributions a lot easier for everyone. The website could be considerably debloated then and information would be easier to find as well (and if it just collections of links). It would probably be easier to add information as well although I dont know how the website is managed ATM. Also, for someone evaluating Gideros it would show the amount of work that is still going into it. From the website you could get the impression that it is almost dead which might deter potential new users.
The main goal would be to make it easier for new users to find and get into the engine which in turn will most likely increase the amount of donations and contributions so profit for all! $-)
This would probably be a large amount of work but I would certainly offer to help (even if the Github idea is not useful) in documenting and collecting information. I am a useless programmer so this could be way for me (and maybe others) to contribute to the development, which I really would like to.
Alright, this is my 2(00) Cents about these things. I hope I did not come across to bold, given I am rather new to the community but I am really enjoying the engine and always wish it would be more accessible... at least I would have made the decision much earlier!
Maybe there are already other plans or ideas floating around that I missed. If so, apologies for adding noise! I would happily jump aboard there of course.
Thanks for reading and sorry for the wall of text!