pylibui

pylibui copied to clipboard

• I think README.md can be rewritten, especially the Contributing section, maybe adding a CONTRIBUTING.md will be better.
• We can make some improvements in bindings.py so generating binding templates will be easier. see #14
• More issues and more labels. We can open issues for unimplemented or semi-implemented components and add some labels to new issues, so new contributors can easily find them.

Any ideas?

I would leave the contribution text on the readme for now. When the project reaches stability, we can move it to a less relevant section, such as contributing.md.

I run all my python code in PyCharm, so it is perfectly natural for me to change a file and run it, like to generate the bindings. But I guess we can be flexible and allow for more use cases, like running in a CLI.

I agree with opening issues. Can you do it? I'll give you commit rights on this project, so that you can do it.

We can also enable CI to check each PR and else stability. I have enable CI on my fork https://travis-ci.org/waghanza/pylibui I'll be glad to open a PR to enable CI

Hi @waghanza, CI is something that we have in our plans, so yes, we welcome any PR regarding that matter! 👍

@joaoventura done with PR #54

I plan to enable also windows, but only osx / linux on both py27 and py35 are tested

Merged #54 👍

awesome, we can also add a status badge on README

@waghanza, I was just writing that, can you build a PR with a status badge on the README?

@joaoventura #55

@joaoventura can you relaunch travis build ? due to our parallel work I think travis build the project before #54 was merge

I'm searching how to do it, but cannot seem to find the relevant information..

Done!

I also added documentation with PR #56, however I consider using this repository as a reference for documentation hosting

Hi all,

I'm not sure enabling OS X tesing was a good idea.

For me, multi-platform tests should rely on libui

A big issue in regards to libui is lack of documentation. I don't think this can be fixed anymore; andlabs doesn't invest that much time into libui, which is understandable.

Hopefully some hero can take the good parts and good idea of libui and create a new project that tackles the existing issues AND the documentation. Because the idea behind libui is great and it works on windows just fine. In fact: because it works on windows I use it more so than I use, say, fxruby+fox on windows, simply because using it for a quick GUI is soooooooo super convenient.

(Just to clarify in regards to my nick: I use python as well. Ruby and Python are very much in the same "boat". The use cases and niches are so similar that, despite the differences syntax-wise and philosophy-wise, I feel that the "scripting" families ultimately fight a battle together rather than against one another, even if evidently every language tries to garner more users than other languages naturally.)