Provide a prelude module

[antoyo]

To import all the gtk::*Ext traits that does not conflicts.

[zzeroo]

I would like to do that. Is that ok?

• create a prelude module
• include gtk::*Ext traits that do not cause a conflict
• update all examples/ documentation and include new prelude module

[antoyo]

Yes, that would be awesome.
You can just use gtk::prelude::* instead of manually finding out which traits have no conflicts.
Thanks a lot for your contributions.

[zzeroo]

Hi @antoyo, I need a decision.

I could just include use gtk::prelude::* everywhere (examples, README, ...) and fix the use statements, like so:

• 2fbe0e5

or, should we have a own prelude module like here:

• 651bd76

I mean the first version is very quick and shows that relm is very tight bound to gtk. The second example is more standard, and extenable. What do you think?

[antoyo]

The idea of using gtk::prelude directly is nice:
we don't need an additional prelude module for relm indeed.
I prefer to update the examples to use gtk::prelude.
Thanks for proposing this idea.

[antoyo]

@zzeroo I specified this issue for the milestone 1.0, so please tell me if you're still working on this issue and would like me to do it?
Thanks.

[zzeroo]

@antoyo I started to work on this issue, but because we restructure many of the examples and the benefit is very low so I think we should close this issue and the PR #78 and focus on more essential parts.

[antoyo]

Ok, since I'll rework all examples, I'll do it at the same time.

[antoyo]

I tried to do use gtk::*; but this was not working in some cases because different traits can have the same methods which causes ambiguity.
So, I'm closing as there's not much we can do, I think.