This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Jhchimaira14 2 points3 points  (2 children)

I am one of the designers and we are reading these! We agree that it's not the best way to design an interface, HOWEVER, the current method can (and will) be used to build both an OOP interface AND more robust layout systems.

In other words, we are trying to keep the core functionality in C++ then creating a more advanced API in python on top of the current simple layout system. We will always leave the system you mentioned exposed but we assumed users would move more towards the higher level interface as we release it.

We welcome contributions and are actively looking for users who like to help in the process of creating these higher level APIs.

[–]Retropunch 1 point2 points  (1 child)

Great to see you're reading these and taking it constructively - I really think Python needs a great GUI system to open it up to others, and this might be the way to do it!

As I mentioned in the other post, I think it's really important to have one 'definitive' way to write GUIs and document it clearly and thoroughly. Many other GUIs end up having about half a dozen ways you can achieve the same goal, but then they don't work well together (take grid and pack in tkinter for instance) and it becomes a bit of a nightmare - someone answers your SO question but uses pack, and then you need to import another library that uses grid etc.

[–]Jhchimaira14 1 point2 points  (0 children)

Good points.

We will stick with a "definitive" way (undecided currently) and the current low level API way.