Which gui for slow (133 Mhz) pc
Author |
Message |
Francesco #1 / 11
|
Which gui for slow (133 Mhz) pc
Hello, What gui can you recommend for my slow pc (win95). I was impressed by the Wxpython demo. But for developing, the startup speed for a simple hello world app with about 10 sec is not acceptable for me. I think, the wxmsw232h.dll with about 4 Mb is the slowing factor. Is there any chance to load this dll already when win95 is started or is it a reasonable idea to load this dll in a ramdrive? Or is it better to try Tkinter or gtk? (I searched with google, but i didn't find a satisfied answer) Many thanks in advance, -- Francesco
|
Thu, 06 Jan 2005 19:46:21 GMT |
|
|
Jeremy Bower #2 / 11
|
Which gui for slow (133 Mhz) pc
Quote:
> Hello, > What gui can you recommend for my slow pc (win95).
I've tried python + (wxWindows, Tk, PyGTK) and a couple of others, too, and they're all about the same in speed. Either learn to live with it (as I have), or move to a non-interpreted environment, which has its own problems. Alternatively, you may be able to largely develop your app outside of the GUI and just put a GUI together last...
|
Sat, 08 Jan 2005 06:48:37 GMT |
|
|
Dave Brue #3 / 11
|
Which gui for slow (133 Mhz) pc
Quote:
> Hello, > What gui can you recommend for my slow pc (win95). > I was impressed by the Wxpython demo. > But for developing, the startup speed for a simple hello world app > with about 10 sec is not acceptable for me.
Another option is to just do "normal" Win32 GUI programming using the win32 (Mark Hammond's) Python extensions. Actually, you have 2 options: you can write Python code that looks nearly equivalent to MFC GUI code, or you can write Python code that looks nearly equivalent to C Win32 GUI code. Either way you'll have very fast load times and your program itself will be quite small (no huge libraries to ship with it). The downside of course is that you have to do more of the work yourself, but I've used this approach in a few programs and it worked well for me. The extensions come with a few examples to get you started, and if you have experience writing the equivalent C/C++ code then development actually goes quite fast. Anyway, it's something to consider.. -Dave
|
Sat, 08 Jan 2005 09:35:20 GMT |
|
|
Francesco #4 / 11
|
Which gui for slow (133 Mhz) pc
Quote:
>> Hello, >> What gui can you recommend for my slow pc (win95). >I've tried Python + (wxWindows, Tk, PyGTK) and a couple of others, too, >and they're all about the same in speed. Either learn to live with it (as >I have), or move to a non-interpreted environment, which has its own >problems.
No, I don't like to turn back to compiled language :) (I can save the compiler waiting times and I like the concept of python) I just want to learn and write a few simple programs. Maybe I have to buy a new computer, this will be the best solution. Quote: >Alternatively, you may be able to largely develop your app outside of the >GUI and just put a GUI together last...
That is a good idea! Thanks and regards, -- Francesco
|
Mon, 10 Jan 2005 02:23:09 GMT |
|
|
Francesco #5 / 11
|
Which gui for slow (133 Mhz) pc
Quote:
>> Hello, >> What gui can you recommend for my slow pc (win95). >> I was impressed by the Wxpython demo. >> But for developing, the startup speed for a simple hello world app >> with about 10 sec is not acceptable for me.
Hello Dave, thanks for your reply. Quote: >Another option is to just do "normal" Win32 GUI programming using the >win32 (Mark Hammond's) Python extensions. Actually, you have 2 >options: you can write Python code that looks nearly equivalent to MFC >GUI code, or you can write Python code that looks nearly equivalent to >C Win32 GUI code. Either way you'll have very fast load times and your >program itself will be quite small (no huge libraries to ship with >it).
That's an alternative. Do I have to compile anything? (I know, stupid question, but I'm an absolute beginner in python, beside, I have a little experience in C/C++ and windows. Quote: >The downside of course is that you have to do more of the work >yourself, but I've used this approach in a few programs and it worked >well for me. The extensions come with a few examples to get you >started, and if you have experience writing the equivalent C/C++ code >then development actually goes quite fast. >Anyway, it's something to consider.. >-Dave
Following another thread, Qt seems to be also a very interesting alternative, I don't know now, if I should spend some time to examine the pyqt libraries, but this is another story, I think ... best regards, -- Francesco
|
Mon, 10 Jan 2005 02:38:38 GMT |
|
|
Chris Liecht #6 / 11
|
Which gui for slow (133 Mhz) pc
Quote: >>Another option is to just do "normal" Win32 GUI programming using the >>win32 (Mark Hammond's) Python extensions. Actually, you have 2 >>options: you can write Python code that looks nearly equivalent to MFC >>GUI code, or you can write Python code that looks nearly equivalent to >>C Win32 GUI code. Either way you'll have very fast load times and your >>program itself will be quite small (no huge libraries to ship with >>it). > That's an alternative. > Do I have to compile anything? (I know, stupid question, but I'm an > absolute beginner in python, beside, I have a little experience in > C/C++ and windows.
no just download win32all: http://starship.python.net/crew/mhammond/ there are some examples that get installed. chris --
|
Mon, 10 Jan 2005 02:48:45 GMT |
|
|
Michael Gilfi #7 / 11
|
Which gui for slow (133 Mhz) pc
Quote:
> Following another thread, Qt seems to be also a very interesting > alternative, I don't know now, if I should spend some time to examine > the pyqt libraries, but this is another story, I think ...
GUI stuff always comes down to your needs really. But pretty much all the toolkits out there can accomplish the same thing, and at roughly the same speed (which is pretty decent to being with) for most applications. What you might want to ask yourself is: how portable does my application need to be (do I want *nix and windows support, for example) and do I need threading? That's when it can get a little iffier and in that case, I've found wxPython to be best. -- Mike -- Michael Gilfix
For my gpg public key: http://www.eecs.tufts.edu/~mgilfix/contact.html
|
Mon, 10 Jan 2005 05:41:40 GMT |
|
|
Alex Martell #8 / 11
|
Which gui for slow (133 Mhz) pc
... Quote: >>> What gui can you recommend for my slow pc (win95). ... > Maybe I have to buy a new computer, this will be the best solution.
Yes. Not sure about Austria, but around here in Italy you can get used PC's that run rings around yours for 250-300 euros. Meanwhile a Pentium-133 with halfway decent RAM is (a bit of overkill, but OK) fine for such tasks as a dedicated router, firewall and proxy/masquerader for a LAN. My home workplace has grown to 5 desktop PC's, plus three laptops occasionally on, with 10/100 Ethernet w. switches among them and ADSL to the world (with ISDN on autodial as a backup should the ADSL ever go down). At the center sits a Pentium-90 running OpenBSD 3 with only one optional piece of software... Python, of course. It handles all of the networking, proxying, firewalling, etc, and talks to the ADSN router on a physically separate Ethernet. The trick is that the old, VERY old Pentium-90 PC has no graphics installed AT ALL. Not even a monitor (nor kbd, nor mouse) -- I just ssh in for occasional maintenance, but there's not much need of that... for this kind of load, OpenBSD 3 can be installed to do everything on its own, with a little tiny help from a few strategic Python scripts. Of course, my "home central server" PC is not powerful enough to run Win-95, by any means. It IS by far enough to do just about anything else I need from it, though. I've even toyed with running Squid there for a while, for example, though my family's usage patterns are such that it was no benefit, so I took it down again. Alex
|
Mon, 10 Jan 2005 16:29:22 GMT |
|
|
Francesco #9 / 11
|
Which gui for slow (133 Mhz) pc
On Wed, 24 Jul 2002 17:41:40 -0400, Michael Gilfix Quote:
>> Following another thread, Qt seems to be also a very interesting >> alternative, I don't know now, if I should spend some time to examine >> the pyqt libraries, but this is another story, I think ...
Hello Michael, Quote: > GUI stuff always comes down to your needs really. But pretty much >all the toolkits out there can accomplish the same thing, and at >roughly the same speed (which is pretty decent to being with) for most >applications.
I don't want to write "applications" now, at first I want to learn and maybe write some tiny utilities for myself and play around. Quote: >Wat you might want to ask yourself is: how portable >does my application need to be (do I want *nix and windows support, >for example) and do I need threading? That's when it can get a little >iffier and in that case, I've found wxPython to be best. > -- Mike
Hm, again, the three alternatives: Porbable is not the question now. Please correct me, if I'm wrong. 1) Tkinter: It is in startup time pretty good, and well documented , stable and straightforward. 2) wxPython is fast (after starting) and has many sophisticated widgets. 3) PyQt: It is "professional" and powerful and is praised from the most people here in this newsgroup. -- Francesco
|
Tue, 11 Jan 2005 04:54:43 GMT |
|
|
Michael Gilfi #10 / 11
|
Which gui for slow (133 Mhz) pc
Heh. NM. Then realistically, you're choices are PyQT (the KDE look) and wxPython. One nice thing about wxPython though is that it looks like a native windows app since it basically wraps the native GUI libraries. Anyway, good luck :) I'm sure you can't really go wrong either way. -- Mike Quote:
> Am Fre, 2002-07-26 um 16.53 schrieb Michael Gilfix: > > Agreed. PyQt is the base GUI toolkit that's used in KDE. If you've > > had some experience with different window managers, I suggest just > > deciding whether you like the look of KDE or GNOME better. If you > > like KDE, use PyQT, otherwise use GTK which is also a well > > developed toolkit. > Well, if you'd read the orginal email, you might discover that this is > about Windows developement ;)
-- Michael Gilfix
For my gpg public key: http://www.eecs.tufts.edu/~mgilfix/contact.html
|
Thu, 13 Jan 2005 23:24:50 GMT |
|
|
Andreas Kostyrk #11 / 11
|
Which gui for slow (133 Mhz) pc
Am Fre, 2002-07-26 um 16.53 schrieb Michael Gilfix: Quote: > Agreed. PyQt is the base GUI toolkit that's used in KDE. If you've > had some experience with different window managers, I suggest just > deciding whether you like the look of KDE or GNOME better. If you > like KDE, use PyQT, otherwise use GTK which is also a well > developed toolkit.
Well, if you'd read the orginal email, you might discover that this is about Windows developement ;) Andreas
|
Thu, 13 Jan 2005 22:44:58 GMT |
|
|
|