In this section of the documentation, there is reference to a demo project called “Hardware/Automatic Image Resolution”. This project is nowhere to be found. The doc should be updated.
@flashjaysan if you need info about scaling, you will like these videos:
There're lots of stuff that could be documented more precisely. I think we as community are also responsible for it. We can't rely on maintainers to write docs&guides, because they already are busy improving core, and they have full-time jobs and families.
> Newcomers roadmap: from where to start learning Gideros "What one programmer can do in one month, two programmers can do in two months." - Fred Brooks “The more you do coding stuff, the better you get at it.” - Aristotle (322 BC)
Thanks for your links. Yeah! I'm very aware of this! But I'm just starting and it's a bit overwhelming to learn and write documentation at the same time.
It's pretty easy to write/update the documentation - especially if you spot some typo, error something else easy and it's a quick fix. The API documentation is held in xml files here:
Just download them and either send the updated version to one of the maintainers or use github to send in the update - you then get added to the list of contributors (bonus!).
Coder, video game industry veteran (since the '80s, ❤'s assembler), arrested - never convicted hacker (in the '90s), dad of five, he/him (if that even matters!). https://deluxepixel.com
Thanks for your links. Yeah! I'm very aware of this! But I'm just starting and it's a bit overwhelming to learn and write documentation at the same time.
Where is the reference to the missing project? Link?
For people in need of doing it too, here is what I edit : Find the example.xml file in gideros install folder under "Resources/start". Replace the "Hardware" category with this :
@totebo No... Everytime I try github, I don't understand how to submit my forks. It's like I commit to my fork and not the original one. So I gaveup...
Comments
There're lots of stuff that could be documented more precisely.
I think we as community are also responsible for it.
We can't rely on maintainers to write docs&guides, because they already are busy improving core, and they have full-time jobs and families.
Likes: SinisterSoft, oleg, hgy29
"What one programmer can do in one month, two programmers can do in two months." - Fred Brooks
“The more you do coding stuff, the better you get at it.” - Aristotle (322 BC)
Yeah! I'm very aware of this! But I'm just starting and it's a bit overwhelming to learn and write documentation at the same time.
Likes: oleg, antix
https://github.com/gideros/gideros/tree/master/docsrc
Just download them and either send the updated version to one of the maintainers or use github to send in the update - you then get added to the list of contributors (bonus!).
Likes: oleg, Apollo14, totebo
https://deluxepixel.com
Likes: oleg
Third paragraph.
Likes: totebo
https://play.google.com/store/apps/developer?id=razorback456
мій блог по гідерос https://simartinfo.blogspot.com
Слава Україні!
https://gist.github.com/razorback456/5fb29fcb51b7c3fb61c6d69032fdbe2e#file-examples-xml
https://play.google.com/store/apps/developer?id=razorback456
мій блог по гідерос https://simartinfo.blogspot.com
Слава Україні!
Find the example.xml file in gideros install folder under "Resources/start".
Replace the "Hardware" category with this :
Likes: Apollo14
Likes: SinisterSoft