Squeak-dev

squeak-dev@lists.squeakfoundation.org

15 participants
79897 discussions

Re: simplicity
by n.moray＠surrey.ac.uk 05 Jan '98

05 Jan '98

> > As Einstein once said: Simplify things as much as possible, but not too >> much. > > Urf. I believe that was "Make things as simple as possible, but no >simpler." Half the fun of quotes is the delivery. :) > > As Graham Chapman once said, whilst impersonating Oscar Wilde (or >was it George Bernard Shaw? :), "I wish I had said that." > > >-C > > > >-- >Craig Latta >composer and computer scientist >craig.latta(a)netjam.org >www.netjam.org >latta(a)interval.com >Smalltalkers do: [:it | All with: Class, (And love: it)] The correct story about Wilde was that he heard someone else make a witty comment, and remarked "I wish I had said that", whereupon his companion replied, "You will, Oscar, you will!" - so perhaps it IS still applicable :-) N. Work email: N.Moray(a)surrey.ac.uk Home email: nmoray(a)globalnet.co.uk send messages to both if Urgent Work address: DERA Professor of Applied Cognitive Psychology, Department of Psychology, University of Surrey, Guildford, Surrey GU2 5XH United Kingdom. Phone number: +44-(0)1483-300-800 and ask for extension 2865 Fax: +44-(0)1483-32813 Home address: 10a Hampstead Hill Gardens, London NW3 2PL. Phone: +44-(0)171-431-4813 "Be well, do good work, and keep in touch" (Garrison Keiler)

1 0

Squeak *.sit bytestream question...
by Serg Koren 02 Jan '98

02 Jan '98

Hi, I'm finishing up an upgrade to the Mac version of Squeak's VM application and am trying to figure out how the bytestream for the included *.sit file was created. I've cleaned up the code and made it compatible with CodeWarrior Pro 2 version and have figured out how to get my code to generate cleanly (and recompile cleanly), but need to incorporate the Stuffit project file. To do this I need to convert the Stuffit file into a bytestream that Squeak can use. Anyone know how this was done? Once I can do this, I'll post the update on my web site. FYI the changes include: - Clean compile and build under CW Pro2 - Real resource file in the VM...it now has a real Squeak icon, etc. - Real About box. - A couple of Smalltalk examples (mostly from "A Taste of Smalltalk") Thanks, S ------------------------------------------------- VisualNewt Software: http://www.VisualNewt.com/ Maker of Newt'sPaper(tm) the Premier Newton(R) MessagePad(tm) News Reader. -----------Sent by BeOS--------------------------

1 0

BeSqueak & Mac Squeak 1.24SK web sites set up.
by Serg Koren 02 Jan '98

02 Jan '98

Hi, This is to let everyone know I've set up a couple of web pages related to two Squeak projects I've undertaken. The first is to upgrade the Macintosh Squeak VM application to be more Mac like and to get it to compile cleanly under the latest version of CodeWarrior; I've actually done this already. In addition, I've started porting Squeak to BeOS (http://www.be.com/). I'm currently in the process of porting the platform specific portions of the code. For more info, feel free to check out the following URLs: Mac Squeak 1.24SK - http://www.VisualNewt.com/Mac/Squeak124.html BeSqueak - http://www.VisualNewt.com/BeOS/Squeak.html Also, if anyone wants to contribute good Smalltalk examples (with significant comments) for inclusion, feel free to submit them to me for inclusion. I'll make sure you get credit in the code and readme files. For more info you can email me at Serg(a)VisualNewt.com Thanks, Serg Koren VisualNewt Software ------------------------------------------------- VisualNewt Software: http://www.VisualNewt.com/ Maker of Newt'sPaper(tm) the Premier Newton(R) MessagePad(tm) News Reader. -----------Sent by BeOS--------------------------

1 0

Re: VM crash
by Tim Rowledge 02 Jan '98

02 Jan '98

On Sun 28 Dec, William O. Dargel wrote: > Leandro Caniglia wrote: > > > Could someone try to reproduce the VM crash I'm experiencing by > > repeating the steps bellow? Thank you. > > > > 1. Open a workspace and evaluate: " self halt error: 'An error > > message...' " > > 2. When the 'Halt encountered' window pops up, select debug. > > 3. From the debbuger menu, select 'step' (stepping the #halt) > > 4. Then select 'step' one more time (trying to step the #error:). > > 5. Wait to see if the VM crashes... > > > > I'm using Squeak 1.23 on NT 4.0 > Happens on my Acorn as well. Some more details:- if you proceed at 2. , all is well. if you debug at 2. and then step over the halt but proceed from there, all is well if you you debug, step, then send the error: and proceed from the first message there in, all is well. if you go the same route but keep stepping, the system dies when stepping over the DebuggerView>openContext:label:contents: message. if you send this message instead of stepping over it, you can eventually get all the way down to ControlManager>scheduleActiveNoTerminate: and thence to scheduled:from: where stepping over 'self activeController: aController' crashes you .. This tallies reasonably well with observed behaviour when trying some of the earlier routes, since the debugger deEmphasises just before the crash. Since William sees an apparent failure on prim 88 (suspend) and I get to where a resume is sent, I have some suspicions about some sort of clash between suspend and resume when the process involved has been molested by the debugger. That's all I have time to spend digging for now, but hopefully it might help someone. tim -- Fractured Idiom:- RIGOR MORRIS - The cat is dead Tim Rowledge: rowledge(a)interval.com (w) +1 (650) 856-7230 (w) tim(a)sumeru.stanford.edu (h) <http://sumeru.stanford.edu/tim>

2 1

Re: VM crash
by W. Kreutzer 02 Jan '98

02 Jan '98

1 0

Re: v1.23 corrupting images
by Leslie Tyrrell 31 Dec '97

31 Dec '97

Ian Piumarta wrote: > Another clue: while debugging I also noticed a ludicrous value in the > stackp slot of the same context. Maybe this is a slighty more useful > nugget of information? > > Ian > When did "ludicrous" get introduced? It doesn't seem to be defined in my image... What are the semantics of this value? How did you determine that it was ludicrous? ( someCondition ) ifLudicrous: [ .... ] or [ someCondition ] whileLudicrous: [ ... ] or perhaps something like- anObject isLudicrous les ( sorry... it's the fatigue talking, I swear! ;^)

2 1

Text color emphasis
by Ernest Micklei 30 Dec '97

30 Dec '97

Hi, In addition to bold emphasis for the selector in the source code of a method, I prefer to have the comment portions show up in blue. A simple scan for comment delimiters in the source and adding the appropriate attribute to the Text object, is all what it takes to achieve this effect in Squeak. However, I noticed that whenever a code window gets focus again (after selecting outside the code window), the color emphasis are ignored when refreshing the contents of the window. Could someone point me to the object with this responsibility ?. Thanks, Ernest PS: I am using Squeak 1.23 on Win95 [[ BLUECO~1.CS : 3631 in WINMAIL.DAT ]]

2 1

Re: Text color emphasis
by Tim Olson 30 Dec '97

30 Dec '97

Ernest Micklei wrote: >In addition to bold emphasis for the selector in >the source code of a method, I prefer to have >the comment portions show up in blue. >A simple scan for comment delimiters in the source >and adding the appropriate attribute to the Text >object, is all what it takes to achieve this effect in Squeak. Well, almost. The "simple scan" code works well in most cases, but it blows up badly when double-quote characters appear inside of a string, as is the case in a few of the methods in the image (try to view ParagraphEditor>>explain when this feature is turned on) ***. >However, I noticed that whenever a code window >gets focus again (after selecting outside the code window), >the color emphasis are ignored when refreshing the contents of the window. >Could someone point me to the object with this responsibility ?. This is due to 2 things: - cacheing window bits for faster update - StandardSystemView caches window bits as two-tone instead of color You can turn off cacheing by selecting the Window... menu and choosing "don't save bits (compact)". This will slow down display when windows are updated, though. You can also tell the StandardSystemView to cache color info by changing StandardSystemView>>cacheBitsAsTwoTone to return false instead of true. However, this will greatly increase the size of the cached window bitmaps. *** To correctly display the comments, you need to parse the method text just as the compiler would. In fact, the Compiler contains a method to do just that: Compiler>>format:in:notifying: will "pretty-print" a method, and decorate it (comments in green, etc.) when the shift key is held down (You can try it out by selecting "format" from the shifted Yellow-button menu of a CodeView). I have experimented with making this the default way of displaying text in a CodeView (selector bold, comments italics are my preferences), with good results. -- tim

1 0

Re: v1.23 corrupting images
by Maloney 29 Dec '97

29 Dec '97

Re: >Recently I moved my main development stream from 1.18 >to 1.23 and found that every 20 to 40 min I end up >with image 24 bytes length after an image save. 1.18 >was pretty stable... Anyone on Unix noticed similar >behavior? > >boris I haven't seen this problem. How often do you save the image? How full is your disk? Are you doing anything that might be opening files and forgetting to close them? -- John

1 0

XML [Re: New comment delimiter?]
by Dwight Hughes 29 Dec '97

29 Dec '97

Patrick Logan mentioned using XML for a file-out format for more elaborate code and documentation systems in an earlier message, and it might serve well as a basis for such semantic structuring/tagging also. The draft of the XML standard is at: http://www.w3.org/TR/PR-xml.html -- Dwight -----Original Message----- From: Mike Klein <mike(a)twinsun.com> To: squeak(a)cs.uiuc.edu <squeak(a)cs.uiuc.edu> Date: Monday, December 29, 1997 1:07 PM Subject: Re: New comment delimiter? | |> From gr(a)fuzzy.uba.ar Thu Dec 25 01:24:16 1997 | |> Just an idea: |> What if we use the color and/or size of the text to show if it's a |> comment for programers, a comment for users, just a comment, or anything |> else? |> It has some problemas like storing all that information as text (HTML may |> help?), and it also makes you learn some color codes to understand what's |> written (size can help for this problem), but it has |> a very nice pro: You can write a book in this way, with titles, |> subtitles, superscripts (?), etc. and of course embedded examples! |> |> What do you think? | |So what you really seem to want is some informational tag on the comments, |so you can tell, for example, the intended audience. (I certainly wouldn't |mind setting the color of the copyright notice comments to transparent :-). |This is, loosely speaking, a meta-comment... a comment about the comment. |Of course in a reflective system, one can add a semantic component even to |comments. Sounds like a good idea. Important to to have some kind of |"standard" so we can all at least have some inkling of what these |meta-comments mean. Also, divorce the idea of physical markup from the |semantic tagging. In outher words, the author of a comment may tag it as |being for lawyers only. It should be the viewer's responsibilty to map |these tags to actual emphases, be they colors for the non-color-blind, |font-sizes for the color-blind, voice-intonation for the totally blind, |or even elided for the legallly-apathetic. There could also be standard |mappings, aka style-sheets. | |Of course it would be nice if we could tag all components to the source, |not just the comment. I think it would be way cool if Squeak's methods |and classes were tagged with a "difficulty level". Beginers' browsers |would show things like #do: before #inject:into: and OrderedCollection |before Metaclass. | | Ramblings after the holidays... | | -- Mike Klein |

1 0

Jump to page: