Stef, In terms of response times, even with a lot of things turned off, I was still surprised at how long it takes to change from even one method to another. Anything past 0.2 sec (or whatever that threshold is) starts to add up; Pharo sometimes takes up to a second, which is _really_ shows up.
Saving an image is not necessarily quick either, I _think_ particuarly on Linux?? Also, I get the sense the wait cursors are displayed, on Linux, for a smaller fraction of the down time than on Windows. Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stéphane Ducasse Sent: Wednesday, July 15, 2009 12:58 PM To: [email protected] Subject: Re: [Pharo-project] Making some progress, and a few observations On Jul 15, 2009, at 6:04 PM, Schwab,Wilhelm K wrote: > Hello all, > > I managed to create an install script; as I suspected would be case, > it was very anticlimactic. I tried creating a password-protected > directory under my personal web site, but that did not go well. The > authentication is weird, so it was probably asking a lot. A directory > repository worked. Good to know > Does Monticello/PackageInfo see a change in method category (aka > package) as a change to the package? normally it should. > It appears not, and it worries me a little in that it seems to make it > easy to lose work by forgetting to save it. Do any of you script > saving your packages? you can check in ScriptLoader to see how we compute the packages that changed (not only dirty but also new packages) > The results are untested at present, but I used SIF to transfer a fair > amount of code into Pharo. To cope with the naming of the ODBC > classes, I ended up doing things like Smalltalk at:#DBConnection > put:ODBCConnection, and that worked out nicely, at least AFAICT at > this stage. SIF finally ended up complaining about running out of > items when processing the last file. I reserve the right to later > report that it was a miserable failure, but it looks like I most of > the code imported. > > Using the standard tools, the w2k theme, disabling faded backgrounds > and enabling fast drag, performance on an older Linux system is ok > (more or less). There are still things that take too long, like what? > and Pharo's responses are no better (sometimes worse) than even > software running over a remote desktop connection. We need a speed > boost, but judicious settings help a little. > > Is there a way to disable the anti-aliased fonts? In fairness, I > should try turning that off to see if any speed boost is worth the > price. > > Bill > > > > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
