Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add gui layout algorithm #5

Closed
nzjrs opened this issue Oct 5, 2015 · 4 comments
Closed

add gui layout algorithm #5

nzjrs opened this issue Oct 5, 2015 · 4 comments

Comments

@nzjrs
Copy link
Collaborator

nzjrs commented Oct 5, 2015

Manually specifying widget coordinates is slow, error prone, and different to other gui frameworks.

Perhaps auto computation of widget location and size can be added. There are two pure python gui layout libraries available

http://cassowary.readthedocs.org/en/latest/
https://github.com/pybee/colosseum

@dddomodossola
Copy link
Collaborator

Hi nzjrs, you have not to define the coordinates of a widget. It is only required define the size of a widget in the constructor. however you're right, the auto-sizing could be a useful functionality. I'm trying to avoid external library dependencies, so I plan to do it simply coding it by myself.

@nzjrs
Copy link
Collaborator Author

nzjrs commented Oct 5, 2015

Cool thanks.

I'm trying to avoid external library dependencies, so I plan to do it simply coding it by myself.

I think some pure-python dependencies are fine. Coding it yourself can introduce unnecessary bugs.

@dddomodossola
Copy link
Collaborator

You're right again, but I'm worried about PIP... I heard about a lot of developers that everytime gets problems with pip, furthermore I imagine a world where people download something and this "something" works. :-D
I will evaluate your suggestion.

@nzjrs
Copy link
Collaborator Author

nzjrs commented Oct 5, 2015

You're right again, but I'm worried about PIP... I heard about a lot of developers that everytime gets
problems with pip

pip can have problems when it needs to compile native code. for pure python it is good enough.

if developers have trouble with it that is often the fault of the developers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants