Better integration in modern workflow

[DrBarbare]

Hi all,

I like this project, and would like to help getting it more visibility. I think the steps towards that would be:

1. Integrate with package manager to get dependencies (I toyed with conan, and it works pretty well)
2. Add CI via Travis and Appveyor
3. Package SFGUI to be used in the ecosystem used in (1.)
4. Document all that

Does that seem to fit the goals of this project?

[eXpl0it3r]

I'd say, go ahead! 🙂

Some points to consider:

• Travis now supports Windows workers, as such Appveyor may not be needed necessarily
• Not sure what Conan package you're using for SFML, but if you didn't know, here's one which still needs work to be fully accepted into the official repo, but Conan maintainers are aware of it.
• Documentation is always nice w.r.t. the usage, if possible, I'd make sure the packaging is scripted/automated.
• If you need help with anything, I'd suggest to either write it here or join the SFML Discord/IRC server

[DrBarbare]

Thanks! I didn't know about Travis support for Windows, that's great! I did use the bincrafters repo. I'll see to join SFML discord.. I tried the IRC in the readme yesterday, but didn't see any SFGUI channel... I'm not a IRC person though ;)

[DrBarbare]

🎺

After a few long nights (and 36 runs on Travis), I got all build passing!
https://travis-ci.org/DrBarbare/SFGUI

I started to work on Travis to ease the insertion of Conan, and it worked like a charm! I was thinking about getting things a bit cleaner before opening a pull request for my code (you can browse it on my fork).

Meanwhile, does @TankOs have a Travis account for this repository?

[DrBarbare]

I also updated the README, however, I would hate to penalize this project with my poor grammar/vocabulary coupled with my ranting about CMake's etiquette (I removed the section about making your own FindSFGUI.cmake, I don't see the reason to do that for this project...)

Updated README

Also, I think I can edit the Wiki, but it lacks a proper review system...