Re: What does Guido want in a GUI toolkit for Python?
On Mon, 29 Jun 2009 16:47:58 -0400, Terry Reedy tjre...@udel.edu wrote: The replacement would need to work with Py 3. TK does. I have not noticed that anything else does, though that should change eventually. (And I am sure someone will point of something I have not noticed.) PyQt does. Phil -- http://mail.python.org/mailman/listinfo/python-list
Re: What does Guido want in a GUI toolkit for Python?
Martin v. Löwis wrote: I sorta' wish he'd just come out and say, This is what I think would be suitable for a GUI toolkit for Python: He is not in the business of designing GUI toolkits, but in the business of designing programming languages. So he abstains from specifying (or even recommending) a GUI library. What he makes clear is the point that Terry cites: no matter what the GUI toolkit is or what features it has - it should be simple to create GUIs, as simple as creating HTML. Tim Berners-Lee would laugh to hear html described as simple. He was very frustrated with how long it took anyone to create a graphical toolkit to create webpages. So, what *does* Guido want in a GUI toolkit for Python? His concern really isn't what is in the toolkit, but what isn't. It must not require lots of lines of code to produce a simple GUI, it must not require specification of absolute coordinates, ... - you should be able to continue the list yourself. Regards, Martin -- http://mail.python.org/mailman/listinfo/python-list
Re: What does Guido want in a GUI toolkit for Python?
On Jun 27, 12:54 pm, laplacia...@gmail.com laplacia...@gmail.com wrote: I just read a blog post of Guido'shttp://neopythonic.blogspot.com/2009/06/ironpython-in-action-and-decl... and notice that he doesn't comment on what he wants in a GUI toolkit for Python. I sorta' wish he'd just come out and say, This is what I think would be suitable for a GUI toolkit for Python: That way, someone could then just come along and implement it. (Or maybe he's said this and I missed it?) So, what *does* Guido want in a GUI toolkit for Python? FWIW, I created a simple GUI builder module I call pygoo that lets you create Tkinter GUIs from a simple text specification. http://www.pygoo.com/ http://code.google.com/p/pygoo/ Warm regards, ~Simon -- http://mail.python.org/mailman/listinfo/python-list
Re: What does Guido want in a GUI toolkit for Python?
On Sat, 27 Jun 2009 17:17:22 -0700, Dennis Lee Bieber wrote: His concern really isn't what is in the toolkit, but what isn't. It must not require lots of lines of code to produce a simple GUI, it must not require specification of absolute coordinates, ... - you should be able to continue the list yourself. Sounds a bit like a return of DECWindows on Xt... Which had a textual design language to define the widgets in use, names for callbacks, etc. and only required the application to load the file and map the callbacks to actual code... You could change the layout without touching the application code (as long as you weren't adding new widgets) Xt itself provides some of that, the rest can be had through UIL (which is part of Motif). GTK+ can do much of this using Glade. The concept of separating code from data is sensible enough, and mirrors the concept of stylesheets in HTML. It shouldn't be necessary to specify size, position, labels, colours and the like via code. Code only needs to be able to get a handle on a specific widget so that it can read and write its state, dynamically register callbacks, etc. -- http://mail.python.org/mailman/listinfo/python-list
Re: What does Guido want in a GUI toolkit for Python?
Martin v. Löwis wrote: I sorta' wish he'd just come out and say, This is what I think would be suitable for a GUI toolkit for Python: He is not in the business of designing GUI toolkits, but in the business of designing programming languages. So he abstains from specifying (or even recommending) a GUI library. What he makes clear is the point that Terry cites: no matter what the GUI toolkit is or what features it has - it should be simple to create GUIs, as simple as creating HTML. So, what *does* Guido want in a GUI toolkit for Python? His concern really isn't what is in the toolkit, but what isn't. It must not require lots of lines of code to produce a simple GUI, it must not require specification of absolute coordinates, ... - you should be able to continue the list yourself. Gui_support obey the above 2 rules, so I guess, 'm on the right way with GUI_support http://mientki.ruhosting.nl/data_www/pylab_works/pw_gui_support.html What are the other rules ? cheers, Stef Regards, Martin -- http://mail.python.org/mailman/listinfo/python-list
Re: What does Guido want in a GUI toolkit for Python?
Casey Hawthorne wrote: So, what *does* Guido want in a GUI toolkit for Python? I saw a talk by a school teacher on pyFLTK: GUI programming made easy. On another note: I#: Groovy makes it easy to tie into the Java Swing GUI, so if Python could do that, with the added complication being the user would need a JVM. -- Regards, Casey Dabo makes it transparent when it come to tying the data to the widget. Based on the wxPython. So it meets Guido's requirements. -- http://mail.python.org/mailman/listinfo/python-list
Re: What does Guido want in a GUI toolkit for Python?
So, what *does* Guido want in a GUI toolkit for Python? I saw a talk by a school teacher on pyFLTK: GUI programming made easy. On another note: I#: Groovy makes it easy to tie into the Java Swing GUI, so if Python could do that, with the added complication being the user would need a JVM. -- Regards, Casey -- http://mail.python.org/mailman/listinfo/python-list
Re: What does Guido want in a GUI toolkit for Python?
laplacia...@gmail.com wrote: I just read a blog post of Guido's http://neopythonic.blogspot.com/2009/06/ironpython-in-action-and-decline-of.html and notice that he doesn't comment on what he wants in a GUI toolkit for Python. I sorta' wish he'd just come out and say, This is what I think would be suitable for a GUI toolkit for Python: That way, someone could then just come along and implement it. (Or maybe he's said this and I missed it?) So, what *does* Guido want in a GUI toolkit for Python? What he did say is But it hasn't really gotten any less complex to create the simplest of simple UIs. And that's a shame. When is Microsoft going to learn the real lesson about simplicity of HTML? -- http://mail.python.org/mailman/listinfo/python-list
Re: What does Guido want in a GUI toolkit for Python?
I sorta' wish he'd just come out and say, This is what I think would be suitable for a GUI toolkit for Python: He is not in the business of designing GUI toolkits, but in the business of designing programming languages. So he abstains from specifying (or even recommending) a GUI library. What he makes clear is the point that Terry cites: no matter what the GUI toolkit is or what features it has - it should be simple to create GUIs, as simple as creating HTML. So, what *does* Guido want in a GUI toolkit for Python? His concern really isn't what is in the toolkit, but what isn't. It must not require lots of lines of code to produce a simple GUI, it must not require specification of absolute coordinates, ... - you should be able to continue the list yourself. Regards, Martin -- http://mail.python.org/mailman/listinfo/python-list
Re: What does Guido want in a GUI toolkit for Python?
On 27 Jun., 23:06, Martin v. Löwis mar...@v.loewis.de wrote: I sorta' wish he'd just come out and say, This is what I think would be suitable for a GUI toolkit for Python: He is not in the business of designing GUI toolkits, but in the business of designing programming languages. So he abstains from specifying (or even recommending) a GUI library. ... which isn't all that different today. One might just take a look at JavaFX and how gracefully it handles declarative data flow a.k.a. data binding. The evolution of programming languages goes on, with or rather without Python. -- http://mail.python.org/mailman/listinfo/python-list
