So I hope this humble message might inspire some folks to have a serious
look at pyfltk. For many situations, PyFLTK can take you to break-even
point quickly, and deliver net savings in time and effort after that.
Animated by your posting I have downloaded:
fltk-1.1.6-source.zip (3.073.432
Claudio Grondi wrote:
Running some of the test examples
(e.g. C:\Python24\pyfltk\test\doublebuffer.py)
I am getting an error I have never seen before:
==
TitleOfMessageBox:
Microsoft Visual C++ Runtime Library
TheMessage:
On Mon, 6 Nov 2005, it was written:
aum [EMAIL PROTECTED] writes:
To me, wxPython is like a 12-cylinder Hummer, ... Whereas PyFLTK feels
more like an average suburban 4-door sedan
Interesting. What would Tkinter be at that car dealership?
A '70s VW Beetle - it's been going for ever, but
aum wrote:
But for smaller gui programs not needing the power of wx, I find I get
the job done much more quickly and effortlessly with PyFLTK.
Interesting. I've found PyQt very easy to use too. I wonder how they compare
(providing you can GPL your app, of course).
--
Jeremy Sanders
PyFLTK is not a debian package - yet.
Is nobody interested, or is there a more specific reason ?
--
Egbert Bouwman - Keizersgracht 197 II - 1016 DS Amsterdam - 020 6257991
--
On Mon, 07 Nov 2005 12:25:49 +0100, egbert wrote:
PyFLTK is not a debian package - yet.
Is nobody interested, or is there a more specific reason ?
AFAIK, the maintainer feels it's still at release-candidate stage.
When he's happy with it, I'm sure he could be persuaded to make
arrangements to
aum [EMAIL PROTECTED] writes:
What I'm saying is that there are many basic projects being written for
these toolkits, whose functionality could be completely supported by
PyFLTK. When only a smaller set of widgets is needed, there's a stronger
case for using lighter widget libraries -
Roger Binns wrote:
It is possible to make the wxPython smaller by having more DLLs each with
fewer widgets in it. That way you will only suck in the ones you use.
I find this VERY interesting Roger, I've been contemplating making such
a request to the maintainer of wxPython (when he gets
On Mon, 07 Nov 2005 09:10:32 -0200, Jorge Godoy wrote:
Installing things mean, usually:
8
Distilling what you've said, it would appear the essence of your argument
is PyFLTK is less desirable because it's not popular, an argument
which, despite a level of pragmatic truth, does contain more than
Hi all,
I've been doing a fair bit of python gui programming on and off, jumping
between different widget sets along the way, from anygui, to pythoncard,
to tkinter/PMW, then to wxPython/wxGlade, and have now settled on a python
gui API that seems to get barely a mention - PyFLTK.
PyFLTK
aum [EMAIL PROTECTED] writes:
To me, wxPython is like a 12-cylinder Hummer, ...
Whereas PyFLTK feels more like an average suburban 4-door sedan
Interesting. What would Tkinter be at that car dealership? What
about PyGTK?
--
http://mail.python.org/mailman/listinfo/python-list
On Sun, 06 Nov 2005 16:31:54 -0800, Paul Rubin wrote:
aum [EMAIL PROTECTED] writes:
To me, wxPython is like a 12-cylinder Hummer, ...
Whereas PyFLTK feels more like an average suburban 4-door sedan
Interesting. What would Tkinter be at that car dealership? What
about PyGTK?
Tkinter -
aum wrote:
To me, wxPython is like a 12-cylinder Hummer, with fuzzy dice hanging
from the mirror, fridge and microwave in the back, and DVD consoles on
every seat, towing a campervan - absolute power and luxury, giving 8mpg
if you're lucky.
wxPython has the cost of a massive disk and memory
Peter Hansen wrote:
The wxPython program below, py2exe'd on my machine (1.6GHz Pentium M),
comes to only 12MB (2-3MB of which is Python itself), and takes 1-2
seconds to load (actually less than one second after the first
invocation following a fresh reboot).
And even 12MB seems heavy,
aum wrote:
On Sun, 06 Nov 2005 16:31:54 -0800, Paul Rubin wrote:
aum [EMAIL PROTECTED] writes:
To me, wxPython is like a 12-cylinder Hummer, ...
Whereas PyFLTK feels more like an average suburban 4-door sedan
Interesting. What would Tkinter be at that car dealership? What
about PyGTK?
Bugs wrote:
Peter Hansen wrote:
The wxPython program below, py2exe'd on my machine (1.6GHz Pentium M),
comes to only 12MB (2-3MB of which is Python itself), and takes 1-2
seconds to load (actually less than one second after the first
invocation following a fresh reboot).
And even 12MB
Hi Peter,
I just used the setup.py that comes in the singlefile/gui sample.
However, py2exe does still also require the msvcr71.dll runtime as well,
which is 340kb. Here it is, it's a bit lengthy:
# If run without args, build executables, in quiet mode.
if len(sys.argv) == 1:
aum [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]
To me, wxPython is like a 12-cylinder Hummer, with fuzzy dice hanging
from the mirror, fridge and microwave in the back, and DVD consoles on
every seat, towing a campervan - absolute power and luxury, giving 8mpg
if you're lucky.
On Sun, 06 Nov 2005 21:23:03 -0800, Roger Binns wrote:
To me, wxPython is like a 12-cylinder Hummer, with fuzzy dice hanging
from the mirror, fridge and microwave in the back, and DVD consoles on
every seat, towing a campervan - absolute power and luxury, giving 8mpg
if you're lucky.
A
19 matches
Mail list logo
