Squeak-dev January 1999

squeak-dev@lists.squeakfoundation.org

143 participants
293 discussions

ThingLab fix
by Bruce Cohen 28 Jan '99

28 Jan '99

The delete fix mentioned in my last message: I found a couple of problems when attempting to delete a botch in building the Quad example, and hacked DisplayRegionHack a little to fix them; code is below. ----------------------------------------------------------------------------- Engineering is never having to say you're finished. ----------------------------------------------------------------------------- Bruce Cohen, | email: cohenb(a)gemstone.com GemStone Systems, Inc. | phone: (503)533-3602 20575 NW Von Neumann Drive | fax: (503)629-8556 Beaverton, OR USA 97006 | web: http://www.gemstone.com ----------------------------------------------------------------------------- 'From Squeak 2.3 of January 14, 1999 on 26 January 1999 at 2:17:12 pm'! Form subclass: #DisplayRegionHack instanceVariableNames: 'clippingRectangle translation bitBlt ' classVariableNames: '' poolDictionaries: '' category: 'ThingLab-Windows'! !DisplayRegionHack commentStamp: '<historical>' prior: 0! I am similar to the RegionMedium class in the Xerox research image; I just have the minimum functionality needed to do the job.! !DisplayRegionHack methodsFor: 'initialization'! clippingRectangle: c translation: t clippingRectangle _ c. translation _ t. bitBlt _ BitBlt destForm: Display sourceForm: nil halftoneForm: nil combinationRule: nil destOrigin: t sourceOrigin: 0@0 extent: 0@0 clipRect: c! ! !DisplayRegionHack methodsFor: 'initialization' stamp: 'di 1/21/1999 20:10'! depth ^ bitBlt destForm depth! ! !DisplayRegionHack methodsFor: 'display medium protocol' stamp: 'bc 1/26/1999 14:06'! boundingBox ^ clippingRectangle! ! !DisplayRegionHack methodsFor: 'display medium protocol'! computeBoundingBox ^clippingRectangle! ! !DisplayRegionHack methodsFor: 'display medium protocol' stamp: 'di 1/21/1999 20:15'! copyBits: sourceRect from: sourceForm at: destOrigin clippingBox: ignore rule: rule fillColor: aForm map: colorMapOrNil bitBlt sourceForm: sourceForm; sourceRect: sourceRect; destOrigin: destOrigin+translation; combinationRule: rule; fillColor: aForm; colorMap: colorMapOrNil. bitBlt copyBits! ! !DisplayRegionHack methodsFor: 'display medium protocol'! copyBits: sourceRect from: sourceForm at: destOrigin clippingBox: ignore rule: rule mask: mask bitBlt sourceForm: sourceForm; sourceRect: sourceRect; destOrigin: destOrigin+translation; combinationRule: rule; mask: mask. bitBlt copyBits! ! !DisplayRegionHack methodsFor: 'display medium protocol' stamp: 'di 1/21/1999 20:34'! drawLine: sourceForm from: beginPoint to: endPoint rule: rule fillColor: aColor bitBlt sourceForm: sourceForm; sourceRect: sourceForm computeBoundingBox; combinationRule: rule; fillColor: aColor. bitBlt drawFrom: beginPoint+translation to: endPoint+translation! ! !DisplayRegionHack methodsFor: 'display medium protocol' stamp: 'di 1/21/1999 20:16'! fill: rect rule: rule fillColor: aColor bitBlt sourceForm: nil; sourceOrigin: 0@0; destRect: (rect translateBy: translation); combinationRule: rule; fillColor: aColor. bitBlt copyBits! ! !DisplayRegionHack methodsFor: 'display medium protocol'! fill: rect rule: rule mask: mask bitBlt sourceForm: nil; sourceOrigin: 0@0; destRect: (rect translateBy: translation); combinationRule: rule; mask: mask. bitBlt copyBits! ! !DisplayRegionHack methodsFor: 'display medium protocol' stamp: 'bc 1/26/1999 14:08'! highLight "Color fromUser" "A default color that will at least reverse most bits" ^ Color quickHighLight: self depth! ! !DisplayRegionHack methodsFor: 'paragraph hack'! displayParagraph: para at: pt para displayOn: Display at: pt+translation clippingBox: clippingRectangle! !

1 0

Remote desktops under Squeak?
by Kevin Fisher 28 Jan '99

28 Jan '99

Hi all: I have a question...what is the purpose of the 'remote' connections under Squeak (in morphic projects)? The most I can get it to do is to share pointers between two machines running squeak, but the desktop is not shared (like Self). Another thing I noticed: I could only 'share' between a Windows Squeak and a Unix squeak...Unix to Unix did not work (produced a debug window).

1 0

FW: Reification of object references
by Stephen Pair 28 Jan '99

28 Jan '99

For those that don't have HTML capable mail readers...sorry for any inconvenience. - Stephen -----Original Message----- From: Stephen Pair [mailto:spair@advantive.com] Sent: Wednesday, January 27, 1999 9:19 PM To: Squeak Subject: Reification of object references A number of messages circulated a while back concerning the reification of object references and messages. As time passes, I become more and more enthused about the possibilities. It seems to me that aspect oriented programming would be made trivial with these tools at our disposal. Has anyone researched how one might go about reifying object references or messages? I've thought a little about how one might reify object references, but I'd like to hear some other viewpoints on the topic. The first thing that occurred to me was that there was a great risk of severely impacting performance (time and space). To avoid the problem, it should be implemented in a way that generic references remain direct or "immediate" references. Thus, we would need some way of determining whether a reference was immediate (an implicit instance of the generic object reference) or indirect through an instance of an ObjectReference. I believe that all object references are 32bit aligned, is this true? If so, then all object references should be evenly divisible by 4 and the lower 2 bits should be available for use (correct?). Since SmallIntegers are denoted by the least significant bit being set, this leaves the bit in the 2's position available. Using a mask of 16r02, the VM would determine whether or not a reference was immediate or indirect. In the indirect case, the VM would send a Smalltalk message to the reference to either get or set the reference. Methods could be provided in Object to get and set object references (#referenceAt:, #referenceAt:put:), which would handle the bit manipulation. In addition, methods to reify and un-reify (is there an antonym?) references could be provided in Object. A useful hierarchy of object references could then be implemented such as: ObjectReference WeakReference TransactionalReference etc... In thinking about this problem, it originally occurred to me that <- ( or :=) could be treated as though it were a binary message, and in the case of a reified object reference, would actually be sent to an instance of object reference...however, it further occurred to me that there is in fact an inconsistency in the language with regard to <- when viewed as a binary message. For example, consider: instVar <- 'some string'. instVar asUppercase. ....in the first statement, '<-' would be a message sent to the object reference (when viewing it as a binary selector), however, the second statement is understood to mean send 'asUppercase' to the target of the reference...thus, the inconsistency. Perhaps we should be writing code like: " *instVar asUppercase " or " &instVar <- 'some string' " ( just kidding :), but the similarity is worth noting ). It also occurred to me that it might be useful for the ObjectReference to know what variable in what object is being set (so <- is insufficient for a setter message). One other interesting prospect is that reifying object references may be useful in eliminating many of the common uses for #become:. For example, in the case of proxy objects, if an object were able to require an specific object reference to be used when referring to it, then proxy objects could have a single associated reference object that all referring objects would share. Then, it would be a simple matter of setting this single reference rather than doing a #become: when the proxy is realized. This would also imply that chaining object references be supported. I have not put any thought into the implications this might have on collections? Perhaps someone else has some ideas here? Regards, Stephen Content-Type: application/octet-stream; name="Stephen Pair.vcf" Content-Disposition: attachment; filename="Stephen Pair.vcf" Attachment converted: Anon:Stephen Pair.vcf 2 (????/----) (000065B8)

1 0

Re: 2.3 for Unix
by Kevin Fisher 28 Jan '99

28 Jan '99

I just wanted to pass on to everyone that the latest Linux version works great! I just compiled it (complete with the sound patches courtesy of Lex Spoon) and it works great! Demo number 3 works fine (but slowly), and the Flash player works great! Thanks a lot, guys!!! On Thu, 28 Jan 1999, Ian Piumarta wrote: >ftp://alix.inria.fr/pub/squeak/unix/2.3 contains the usual stuff for: > > alpha-osf1-v4.0 > i386-linux-2.0.36 (linked against glibc-2.0.7) > i386-linux-2.1.24 (linked against libc-5.4.38) > sparc-solaris-2.5.1 > sparc-sunos-4.1.4 > >with the regular four-file snack-packs in the "distributions" directory. > >Major noteworthies: > > * graphics-related bug fixed (can anyone spot what it is? this bug > has been there since 1.13 and nobody noticed!) > > * user-defined primitives are gone (definitively! -- use named > primitives instead) > > * there's an optional low-res 1/50 second clock using ITIMER_REAL and > SIGALRM, avoiding lots of relatively expensive calls to >gettimeofday() > > NOTE: this means that sleep() won't work; if you really > absolutely cannot avoid calling sleep() from custom-made > code then change > #define USE_ITIMER > to > #undef USE_ITIMER > at sqXWindow.c:93 and recompile the VM > > * the ".image" extension on the image name is added implicitly (you > have the option of omitting it on the command line) > > * a couple of Makefile pimples squeezed, more or less as suggested by > Bert Freudenberg and Lex Spoon > >Let me know of any problems ASAP. Enjoy! > >Ian

1 0

Usability of Squeak on PDA's
by Pennell's 28 Jan '99

28 Jan '99

Can users/porters of Squeak on PDA's comment on the usability and performance? My PalmPilot recently died and I'm shopping for something about the same size with a backlit screen and the ability to record a couple of minutes of verbal notes. Squeak support would be a bonus. -david

4 3

Re: 2.3, Unix, and Squeak central
by Bruce O'Neel 28 Jan '99

28 Jan '99

Hi, Ian has already responded, but, I think I got a working 2.3 on Solaris by generating interp.c from a 2.3beta vm and the 2.3 image, changing all ^M to ^J via xemacs, and then copying that to gnu-interp.c and running make. It does properly execute (FlashMorphReader on: (HTTPSocket httpGet: 'http://www.audi.co.uk/flash/intro1.swf' accept:'application/x-shockwave-flash') processFile. from the readme. In this case "properly executing" is defined as playing an advert for Audi :-) cheers bruce Lex Spoon <lex(a)cc.gatech.edu> wrote: > > Bill Cattey <wdc(a)MIT.EDU> wrote: > > I've got the 2.3 image and changes file, and I'm running them on my > > Solaris and Linux systems in the 2.3beta image I got from inria. I've > > noticed that sometimes morphic projects get VERRRRRY slow, and the > Play > > With Me 3 (16 bits) demo project, when entered hangs the VM and ALT<.> > > can't interrupt. > > > > I figure these may be due to little improvements in 2.3VM that aren't > in > > the Beta VM. Alas, the 2.3VM has not yet been made available for the > > Unix platforms. Is this expected to happen soon, or should I attempt > to > > reproduce the work of Carl Gruden? > > > > I haven't gotten Play With Me 3 to work, either. However, I haven't > seen the slowdowns you mention. > > One person posted they got a 2.3 VM compiled by: > > a) generating interp.c from Squeak as normal (comment in > CCodeGenerator) > b) skipping the translation for GCC that the Unix Makefile normally > does. For instance, change "../util/translator" to "/bin/cat" in the > makefile. > > > I tried this, and it worked fine.... The only problem is that the VM > doesn't contain the truetype code anywhere. Is this in the image > somewhere that it can be filed out, or is it platform-specific code that > someone the likes of Ian Piumatra will have to write? > > > Lex > > == Bruce O'Neel - beoneel(a)acm.org http://homepage.iprolink.ch/~bioneel The corporate culture is concerned less with Occam's razor than his aftershave lotion. -- R. L. Peskin <peskin(a)caip.rutgers.edu> _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com

1 0

PWS, (s)Wiki & Proxies
by Vandendriessche, Frederik 28 Jan '99

28 Jan '99

Question: How does one operate behind a proxy that requires you to login before connecting to the internet ? (Using a proxy that does not require a loginID/password is no problem) I recently found some german (sorry lost the name of the author) code that gets the name of documents that are pointed to by hyperlinks in the edit box on a swikipage. This code launches some request to the internet, via my proxy. CodeFragment: titleForUrl: link | doc content start end | doc := HTTPSocket httpGetDocument: link accept: nil. "accept text/html only" (doc isKindOf: String) ifTrue: [^nil]. "error" doc contentType asLowercase = 'text/html' ifFalse: [^nil]. content := doc content. start := content findString: '<title>' startingAt: 1 caseSensitive: false. start = 0 ifTrue: [^nil]. end := content findString: '</title>' startingAt: start + 7 caseSensitive: false. end = 0 ifTrue: [^nil]. ^content copyFrom: start + 7 to: end - 1. The first line of code causes my proxy to return a '407 Proxy-Authentication needed' message. How to solve ? ** Maybe we (and not some socket) need to create an instance of PWS (thus a request) instead of sending messages to the HTTPSocket. ** When this request works fine (code 200), we could do the same as in the code above. ** When there is some error (code 407), we should return this to the user, let him/her enter his/her credentials, and retry. ** (But is all this possible?) Anyone with other/better ideas/solutions ? Greetings. Frederik Vandendriessche System Engineer, > eElectronic Business Services, * frederik.vandendriessche(a)eds.com * ..32/0 2 711 37 83 L ..32/0 2 711 39 47

1 0

Re: Morphic, dataflow and encapsulation
by Frank Speckmann 28 Jan '99

28 Jan '99

hi! i recently stumbled over something that might be of interest in this context, though it is not directly adressing smalltalk or even squeak (yet). here it is: http://www.vtt.fi/tte/papers/j-uml/ it is about a sort of middle tier between uml and java. sounds like a nice idea... cheerio! Frank Speckmann f.speckmann(a)teamworks.de >No kidding! > >To look at graphical application development in a slightly different >context, I long ago worked with the Helix database program for Mac. It was >really easy to hook together a few tiles in the flowline-ish graphical >working environment to do something really simple. The demos were great for >that! The moment you needed a database of any complexity, however, you >might as well forget about even a useful overall view. All you had was >continuous screens packed with tiles that could tell you nothing about >themselves unless you opened up their little windows. > >In Authorware, as well, the graphical flowline metaphor becomes a royal >pain in the icon for the same reason. When all the details of your >graphical objects can never be viewed, dumped, exported or previewed in any >convenient way, the apparent convenience of the graphics can quickly become >a millstone around your neck. There's nothing worse than having a >substantial portion of the functioning of an application be buried in a >million dialog box options instead of simultaneously accessible as readable >text. > >I have somewhat less trouble with xcard systems simply because there is >more tendency for them to be able to provide script lists conveniently when >needed, especially if the bulk of the functioning of an application is in >the scripts, not dialog box options. > >The most desirable system for really sophisticated program tasks *might* >include a graphical optional view pictorially analogous to an outline mode >or collapsible tree structure. But it seems to me it's always going to >become essential at some point to print out the entire code, post it on a >big wall, and be able to see everything from the topmost to bottommost >aspect at the same time. > >David > >>My problem with graphical programming systems (and here I'm thinking about >>a few >>very different entities: Prograph is the extreme case, HyperCard and Interface >>Builder for Apple's Yellow Box are more typical ones) is their failure to >>produce documentation for what's there or they hide what's going on by >>requiring >>many different windows to be open. >> >>There's no documentation feature which allows someone to tell the >>application or >>its UI (whatever you're working on) to document itself -- so you end up >>hopping >>>from place to place, reference to reference, striving to maintain context. I >>HATE this. With a passion. Even Smalltalk can be a pain with three or four >>browsers open at a time while I try to figure out just WHAT object is going to >>respond to a message that has been sent. I must be too old or something. >> >>One of the things that I liked best about the GUI Builder in >>SmalltalkAgents was >>that when it built a window it wrote the code for that window which I >>could then >>see and, if needed, edit. >> >>In InterfaceBuilder (in Apple's Yellow Box) you build an interface and hook up >>the feature -- but then result is all concealed in a NIB file which is a black >>box -- there's no way to tell IB to write out in human-readable form what the >>contents of that NIB file are. >> >>This inability to concisely document is, to me, the greatest weakness of >>graphical tools. >> >>Thanks for listening -- pant pant pant.... >> >> >>Adam Bridge > > >David Cramer, Process Innovation Evangelist 87-1313 Border Street >PBSC Computer Training Centres Winnipeg MB R3H 0X4 >Corporate Office Research & Development Canada > >

1 0

Reification of object references
by Stephen Pair 28 Jan '99

28 Jan '99

1 0

Re: ThingLab
by Reinier van Loon 28 Jan '99

28 Jan '99

Dan Ingalls wrote: > What doesn't work > Battery won't fileIn right, so the electrical examples don't work. It's probably easy to fix. There is a second browser called the Object Definer that Alan says never worked (it was a > project to define constraints graphically using thinglab itself). Also, as I said, it should all be moved to Morphic where the objects can be put in parts bins and intermingled with the > rest of Morphic. For those interested in getting Battery to file in right: 1) edit ThingLab.cs and change 'nil subclass: #SetConstraint' into 'Constraint subclass: #SetConstraint' 2) repeat this for SetMembershipConstraint 3) copy the class definition of SetConstraint and rename #SetConstraint to ConditionalConstraint 4) change the string 'mask: nil' in all thing files which have 'showPicture:' and 'mask: nil' in it to 'fillColor: nil' 5) file ThingLab.cs in 6) file Battery.st in 7) open a ThingLab browser and enjoy Currently I'm busy getting all 'things' in a 'file in-able and view-able' state. Anyone out there doing the same? To Dan: The following classes and methods are missing: ConditionConstraint, ExprEquality, transpose, methodsNotUniqueState Any chance you've got them? Regards, Reinier.

3 2

← Newer
1
2
3
4
5
6
7
8
...
30
Older →

Jump to page: