Website Update needed to bring Information pieces together

[marianeichholz]

The current documentation is unfortunately a bit fragmented and scattered.

• rugui.org lists version 1.3.2 as "current version". AFAIK is should list 1.6.0 and at least mention 2.0.0.beta2.
• The example applications are mentioned, but with no URL or direction, where and how to get it (I used GitHUB and skimmed the author's repositories, kind of bit safari). And a warning, that these codes would not work in new(er) environments.
• A, well, a little table, which version on RuGUI will work with which Ruby, GTK, Glade and ActiveSupport would do fine, just to protect the daring developer from foreseeable frustration, when the parts won't play together.
• Or/complementing: "Well known issues", I like those...
• The two(?) tutorials can be found in the Blog, but there really should be a Link in the "Getting Started" section, because (at least me) cannot get started without. Really! :-)
• Some links to the RubyGTK/RubyGlade-Tutorials in a "Ressources"-Section would complement that nicely.
• Some bridging hints, where the developer is on his/her own with GTK/Glade, and where he/she should better cling to RuGUIs proprietary mechanisms probably would do, too..

No rocket science, just collecting the well known information at the logical Hub, rugui.org :-)

Thank You in advance - marian

[vicentemundim]

Thanks for summarizing all these issues!

The RuGUI.org site is completely outdated. I think that migrating it to use Github pages and point documentation there would be the first step.

I haven't been giving RuGUI much time as of lately. I'll try to make the examples work with the new version of RuGUI, but I can't promise anything. As for the documentation, feel free to make some pull requests!

[marianeichholz]

If I can help, no worries! Just for Dummies: What is a "pull request" in this context? Just to do the right thing :-) - marian

PS: OK, I should view some areas ob the GitHub documentation. Never mind!

[vicentemundim]

On github you have this workflow where you first fork a repository, then make the changes you want in your fork, push then to github, and finally create a pull request within github interface.

You can read more about it here: https://help.github.com/articles/using-pull-requests