hi, strange, when we started to develop the wx-gui, I just used my old laptop. it was celeron with 600 MHz and I had 192 MB RAM. It was usable
j 2008/6/10 Marco Pasetti <[EMAIL PROTECTED]>: > Hy Glynn, > > did you ever estimated the speed of the Python GUI Vs a generic compiled > GUI? > > On my old Notebook (AMD Athlon64 3000+, 1.25 GB RAM DDR, integrated NVIDIA > GPU with shared 64 MB VRAM) I noticed that, very often, just opening a > module GUI or a dialoge window caused the system to freeze for a while (XP > Pro SP2, 32bit, very well maintained). This said, all the other GUI parts, > such as the GIS Layer Manager and the Map Display, always worked very well, > and never (maybe rarely) freezed. > > Is that because the GUI is interpreted or is it only a Windows problem? > actually, many Windows native application GUIs frequently freeze, even if > they are compiled and not interpreted GUIs... > > Thanks for your precious explanations, as always.. :-) > > Marco > > ----- Original Message ----- From: "Glynn Clements" > <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: "Michael Barton" <[EMAIL PROTECTED]>; <[email protected]> > Sent: Friday, June 06, 2008 6:37 PM > Subject: Re: R: [GRASS-dev] WinGRASS Plans > > >> >> [EMAIL PROTECTED] wrote: >> >>> Since we are talking about, why an interpretated language for the GUI >> >> It makes it easier for the user to customise the code, and to apply >> updates. >> >> -- >> Glynn Clements <[EMAIL PROTECTED]> > > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev > -- Jachym Cepicky e-mail: jachym.cepicky gmail com URL: http://les-ejk.cz GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
