Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!rpi!batcomputer!munnari.oz.au!metro!extro!objtch From: objtch@extro.ucc.su.oz.au (Peter Goodall) Newsgroups: comp.windows.ms Subject: Re: Smalltalk V /Windows (oink, oink) Message-ID: Date: 7 Mar 91 21:35:12 GMT References: <10960018@otter.hpl.hp.com> <27207@netcom.COM> Sender: news@metro.ucc.su.OZ.AU Organization: Sydney University Computing Service, Sydney, NSW, Australia Lines: 85 Nntp-Posting-Host: extro.ucc.su.oz.au ergo@netcom.COM (Isaac Rabinovitch) writes: >In <10960018@otter.hpl.hp.com> pwt@otter.hpl.hp.com (Peter Toft) writes: >>I've also just received ST/V for Windows. Though I've not yet done any >>development using it, running the demos hasn't indicated much of a performance >>problem when compared to my other Windows Apps. >>Admittedly, I'm using a 486 with 10Mb of memory. But it's the relative >>performance that counts. >I released the "turbo" button on my machine (bringing it down to >10Mhz, which is slower than a lot of 286's these days), and it was >still quite responsive. Have heard that it degrades over time, >though. If true, compressing the image should fix it, and it wouldn't >affect distributed versions of your programs. >I think of a lot of Smalltalk's reputation for slugishness, especially >on PCs, comes from the problems of adapting it to run on top of >simple-minded operating systems. Digitalk didn't help when they >neglect to implement any decent scrolling or searching mechanism. >This time, they've simply used standard Windows facilities, and it >makes a difference. (This sort of standardized support for >applications makes me think of Windows 3.0 as the first "real" >operating system for PCs!) >I *do* get in trouble if I start and stop ST several times though. >Keep running out of memory, as if it were not releasing all its >memory on exit. Typical kind of first-release problem -- I hope. I believe it is a problem with the memory manager in Win3 - We do have several complex systems from different sources at work together here. >One thing that *really* bothers me is that any program you create with >ST/Windows starts up with a window advertising that the program was >written with Smalltalk V -- and every window label gets "Smalltalk/V" >prepended to it. The first is slightly obnoxious, the second is just >plain stupid. >-- This is the label: method on class Application window As you will see the prefix to the label is in a global variable called WindowLabelPrefix - very easy to fix! ST>label: aString ST> "Set the window label of the receiver to aString." ST> label := aString isEmpty ST> ifTrue: [aString] ST> ifFalse: [WindowLabelPrefix, ' ', aString]. ^^^^^^^^^^^^^^^^^^ ST> handle isNil ifTrue: [^self]. ST> handle = NullHandle ifFalse: [self setWindowText: label]. Here is what that global contains: 'Smalltalk/V' Don't ever think anything is hard-wired into a Smalltalk system until you have looked. Conditional branches for example are not part of the language. They are written in Smalltalk. Look at the classes True and False! I'm not sure about th opening credits yet, I've been too busy to look. > ergo@netcom.com Isaac Rabinovitch > netcom!ergo@apple.com Silicon Valley, CA > {apple,amdahl,claris}!netcom!ergo > (specific statement withheld at this time for operational reasons) ---------------------------- Peter Goodall Smalltalk Systems Consultant ObjecTech P/L 162 Burns Bay Rd, LANE COVE , NSW, AUSTRALIA objtch@extro.ucc.su.oz.au