GIR and Object_reform priorities

[EPashkin]

Currently we have too many issues, but mostly its not really necessary for main task (replace current gtk-rs paradigm).
Not better focus to add working example like basic.rs to prove that concept is really works?
For this needed only functions from rt.rs and some basic signals (really needed only connect_delete_event that can be added to already manual window\mod.rs)

[gkoz]

As a reminder to other readers: we started this project in the midst of the object reform, which was being implemented by hand.

I still want to finish the reform ASAP because:

• there's no need to keep a fork,
• not upgrading the master branch is unfair to any contributors who have to learn the obsolete ways of wrapping objects and then do the job of the generator by hand.

Anything beside objects (classes and interfaces) is outside the scope of the reform.

How do we put this back together? After fixing the signal module, the examples should only need some unwraps removal to just work with this branch. Also any changes to signal, rt and record wrappers will need to be merged from master.

Some methods missing from autogenerated modules will need to be added in manual impls for structs and additional extension traits for traits, aiming (within reason) to not lose any APIs available in the master branch.

[EPashkin]

Closing as object_reform merged in gtk-rs.