Squeak-dev December 2002

squeak-dev@lists.squeakfoundation.org

173 participants
456 discussions

sqUnixDirectFB
by Frits Swinkels 22 Dec '02

22 Dec '02

No, aio.h and sqaio.h are not the same: the latter contains a call aioInitialize() which is not in the original. I assume that the author did not rename the file for fun. Frits Swinkels #306 2920 Cook Street Victoria, B.C., V8T 3S7 phone and fax 250 389 0155 frits.swinkels(a)shaw.ca

2 1

WriteStream nextPutAll:
by bitwFrog 22 Dec '02

22 Dec '02

Markus, Worked a treat, Thank you very much ! Regards, Paul Lakin -- bitwFrog

1 0

sqUnixDirectFB
by Frits Swinkels 22 Dec '02

22 Dec '02

Two questions re sqUnixDirectFB.c. 1. It would be good to know from which precise sqXWindow.c it was derived. 2. sqUnixDirectFB.c refers to sqaio.h (and a corresponding sqaio.c). Anybody has copies? I am having one more go at putting a shrunk Squeak on memory-challenged (i.e. 16Mb) x86 machines without X11. Frits Swinkels #306 2920 Cook Street Victoria, B.C., V8T 3S7 phone and fax 250 389 0155 frits.swinkels(a)shaw.ca

2 1

WriteStream nextPutAll: vs Stream nextPutAll:
by bitwAttb 22 Dec '02

22 Dec '02

Hello, I encountered this when I tried to fileIn the MusicTools class from Mark Guzdial's Live Essay. I believe it's related to a similar problem that John Voiklis reported in msg00314 when someone found SwkiNavigator.st failed when trying to fileIn the icon images. Here's what I did: 1) In Mark's Live Essay Image, filed out SqueakMusicTools.cs 2) The changeset files in OK to Mark's image 3) Tried to fileIn on 3.4B image, got: "MessageNotUnderStood: reset" walkback. 4) Dunno how to cut & paste the gory details but, the fileIn process fails at the end when the GIF files for the icons are supposed to be read in by the ImageReadWriter. ImageReadWriter, when performing formFromStream, passes a nextPutAll: to WriteStream class. WriteStream class nextPutAll method seems to have been changed in Aug 2001 to, in turn, call super nextputAll, so the method call gets handled by Stream class. Stream class nextPutAll: returns not a Stream but an instance of the argument collection, in this case a String. So Stream nextPutAll: returns String class to be reset when ImageReadWriter is expecting to have created an i nstance of RWBinaryOrText class. Hope it makes sense .. TIA for suggestions, Paul Lakin -- bitwAttb

2 1

[GOODIE] ConflictChecker added to SqueakMap
by Doug Way 22 Dec '02

22 Dec '02

I just updated my ConflictChecker utility for 3.4, and added it to SqueakMap. From the preamble... ----------------------------- Given a changeset filename, you can use this goodie to check an older .cs/.st file for conflicts with methods from more recent update-changesets in your image. Its output is displayed in a Transcript window. Example usage: 'FilePackage conflictsWithUpdatedMethods: 'MyChangeSet.cs'.' Or, use the 'conflicts with updated methods' menu item or 'conflicts' button in the FileList window. The ConflictChecker doesn't just check to see which methods in a changeset would overwrite methods in the image... it actually checks to see if there have been more recent updates to the image since the changeset was created*, in which case the more recent methods would be overwritten by older methods from your changeset if you filed it in, which would likely break things. It's basically a 3-way conflict check. *It uses the latest update # from the .cs/.st file header as a basis for comparison. Generally, you should use a reasonably fresh image to do this, and the image should have update-changesets going as far back as possible (at least as far back as the changeset you want to test). - Doug Way

1 0

Re: Subjective Squeak
by Daniel Vainsencher 21 Dec '02

21 Dec '02

Two things - Model vs Mechanism You say memory foot print I say who cares. 256MB is quite achievable for a PDAs nowadays, so I'm not sure it's a big benefit. OTOH, that's just Mechanism. You mention switchable environments - now that's a Model issue. One PIE paper shows a good role for layers as a model of programming (layers as a programmers product - a unit of code modifications). Then it mixes it up with all the decisions they make due to machine limitations - needing to switch between states rather than forking a process, implementing the aspects as a low level mechanism (affecting object storage). Who cares? after all these years, I don't care a bit for all their mechanism, but I am very sorry we still don't have a model as developed as they did for programming. For the same reason, if you tell me you want to make images able to share read only pages of memory in which class objects live, sort of Smalltalk DLLs, similar in some ways to SmallScript, I'd think it's also technically an interesting idea, but I'd still ask what's the model. Saving memory is not the issue here. What our models are is the big question, and how do we start modifying the way we work, to realize them as quickly as possible. Mechanism vs Mechanism The more you talk about switchable layers, the more, I think why not get the same capabilities from richly communicating separate images, reusing the OS/separate VM's protection? About projects - the problem with projects precisely exemplifies the issues at stake. First, you need to have projects be dependent on a specific configuration, and be able to download that automatically (using SM). We're mostly agreed there. Second, you need to be able to activate it, while isolating it properly from your current image. So yes, right now, I know I'd load more projects if they were simply run in a separate, new process. In fact, when I start to think about it, a complete alternate Squeak universe unfolds. Imagine a GUI image, that has all the GUI tools you want, but doesn't generally run the models. The models run on one or more headless images. I have a mail image, and I have a completely separate development image, but their GUIs run on the same image. Most of the browsers and workspaces simply happen to be connected to the development machine. Communications between the image are kept mostly asynchronous, and on simple, standard protocols, and completely for free, you get a Squeak that runs very well on SMP machines. Or distributed across a network. And yet at any time, you can connect a browser and an object explorer to a specific image, and KNOW, that in front of you within this address space, is something as simple as a completely self consistent Smalltalk, separate from the rest of the world, except for the above communications. Daniel Anthony Hannan <ajh18(a)cornell.edu> wrote: > Hi Daniel, > > If you look at environments/layers as configurations and classes as > the loadable units, then a configuration specifies which versions of > which classes to load. It may do this by including (inheriting) other > configurations then adding/overriding classes itself. If the user > switches configurations it is very reasonable to expect things like the > world menu to change. However, if he stays in his own personal > configuration and just changes which other configurations it inherits, > then if he inherits two configurations that have two different versions > of the world menu then an exception will be raised because it is > ambiguous. So conflicts will be raised and must be resolved. > > Ideally there would only be one version of each class, and configurations > would just specify which ones to load. But allowing different versions is > needed, because full collaboration is impossible. New class versions can > be submitted as replacements for originals, and the best way to do that is > to put the new version in its own configuration so others can inherit > from it and test it. Then when it is tested and accepted it can be > promoted to the original configuration. > > Remember, I am still a proponent of class extensions that are actually > separate behaviors/classes in a multiple inheritance hierarchy. This > way new versions of classes are just changes and not additions of new > behavior. With class extensions as separate classes, we only need > configurations and classes, eliminating the need for a third intermediary > concept (packages). > > As for multiple images, even if memory is cheap we don't want to waste > it, so PDA users can load and run as many applications simultaneously > as possible. So I really think we should strive for one "operating > system" image. And as for a safer non-crashing image I think layers/environments/configurations would actually help this. When a > critical error happens, the user can be moved to a safe configuration > automatically. He would still be able to inspect the damaged > configuration because its still in the image, its just no longer running. > See > http://web.media.mit.edu/~lieber/Lieberary/Softviz/CACM-Debugging/Kansas/Ka… > for an example of this done in Self. > > Finally, without different configurations allowed in the same image how > do you expect to handle Squeak Projects, and switching between them > easily? The current mechanism is very fragile and needs to be fixed. > Today, projects can only be loaded in images that are sufficiently > similar to the image it was created in. If certain functionality is > missing or changed the project will break. It has no way of determining > or loading the base image it depends on. It only know local changes it > made inside its project. > > Cheers, > Anthony > > > Daniel Vainsencher <danielv(a)netvision.net.il> wrote: > > Ah here I definitely disagree - I think this is a huge landmine. > > > > Whether people come to use a layered system for it's real benefits or > > not, I think it would be a disaster if people use it to ignore trivial > > incompatibilities between packages. > > > > Remember that one of the great benefits of free software development is > > the testing. It's a critical part of the magic. For a modular > > environment, as Squeak is already headed to be since the day SqueakMap > > is online, integration testing is a large part of the issue. > > > > Where two packages need significantly different functions, they should > > be using two separate, mutually neutral actual mechanisms. Where two > > packages need slightly different versions of the same thing, this needs > > to be visible, slightly painful for all involved, until it is resolved. > > > > I'll give you a concrete example - if each package, as part of it's > > layer, should bring in it's own version of the TWM>>openMenu, everything > > would "work", and the user might go mad before understanding why it > > keeps changing on him. The solution is to find these areas of conflict, > > however small, and redesign them for cooperation. Not to apply a > > one-size-fits-all plaster that allows all packages to ignore one > > another. > > > > The real solution is for package maintainers to avoid patching other > > packages, in your package, instead submitting patches to the upstream > > packages maintainer. And concurrently, to give the user tools to notice > > and control when this is happening. > > > > Memory is cheap, and cheaper every day. > > > > For an OS, it gets unfixably stuck too often. We have issues to solve here > > much before we need layers.

1 0

Re: Subjective Squeak
by Anthony Hannan 21 Dec '02

21 Dec '02

Anthony Hannan <ajh18(a)cornell.edu> wrote: > Remember, I am still a proponent of class extensions that are actually > separate behaviors/classes in a multiple inheritance hierarchy. This > way new versions of classes are just changes and not additions of new > behavior. With class extensions as separate classes, we only need > configurations and classes, eliminating the need for a third intermediary > concept (packages). Actually, separate class extensions is not required for eliminating the third concept. Class extensions can be represented as new versions of classes (additions). However, if two or more configurations specify two new versions of the same class (for two new class extensions), then there would be a conflict. To fix this, we could allow two versions of the same class to automatically merge if none of its methods conflict. So all that is needed are classes and environments. You can call the environments "configurations" (as I have in this and my last email) or "packages" (as I have in previous emails). Cheers, Anthony

1 0

Re: Subjective Squeak
by Anthony Hannan 21 Dec '02

21 Dec '02

Hi Daniel, If you look at environments/layers as configurations and classes as the loadable units, then a configuration specifies which versions of which classes to load. It may do this by including (inheriting) other configurations then adding/overriding classes itself. If the user switches configurations it is very reasonable to expect things like the world menu to change. However, if he stays in his own personal configuration and just changes which other configurations it inherits, then if he inherits two configurations that have two different versions of the world menu then an exception will be raised because it is ambiguous. So conflicts will be raised and must be resolved. Ideally there would only be one version of each class, and configurations would just specify which ones to load. But allowing different versions is needed, because full collaboration is impossible. New class versions can be submitted as replacements for originals, and the best way to do that is to put the new version in its own configuration so others can inherit from it and test it. Then when it is tested and accepted it can be promoted to the original configuration. Remember, I am still a proponent of class extensions that are actually separate behaviors/classes in a multiple inheritance hierarchy. This way new versions of classes are just changes and not additions of new behavior. With class extensions as separate classes, we only need configurations and classes, eliminating the need for a third intermediary concept (packages). As for multiple images, even if memory is cheap we don't want to waste it, so PDA users can load and run as many applications simultaneously as possible. So I really think we should strive for one "operating system" image. And as for a safer non-crashing image I think layers/environments/configurations would actually help this. When a critical error happens, the user can be moved to a safe configuration automatically. He would still be able to inspect the damaged configuration because its still in the image, its just no longer running. See http://web.media.mit.edu/~lieber/Lieberary/Softviz/CACM-Debugging/Kansas/Ka… for an example of this done in Self. Finally, without different configurations allowed in the same image how do you expect to handle Squeak Projects, and switching between them easily? The current mechanism is very fragile and needs to be fixed. Today, projects can only be loaded in images that are sufficiently similar to the image it was created in. If certain functionality is missing or changed the project will break. It has no way of determining or loading the base image it depends on. It only know local changes it made inside its project. Cheers, Anthony Daniel Vainsencher <danielv(a)netvision.net.il> wrote: > Ah here I definitely disagree - I think this is a huge landmine. > > Whether people come to use a layered system for it's real benefits or > not, I think it would be a disaster if people use it to ignore trivial > incompatibilities between packages. > > Remember that one of the great benefits of free software development is > the testing. It's a critical part of the magic. For a modular > environment, as Squeak is already headed to be since the day SqueakMap > is online, integration testing is a large part of the issue. > > Where two packages need significantly different functions, they should > be using two separate, mutually neutral actual mechanisms. Where two > packages need slightly different versions of the same thing, this needs > to be visible, slightly painful for all involved, until it is resolved. > > I'll give you a concrete example - if each package, as part of it's > layer, should bring in it's own version of the TWM>>openMenu, everything > would "work", and the user might go mad before understanding why it > keeps changing on him. The solution is to find these areas of conflict, > however small, and redesign them for cooperation. Not to apply a > one-size-fits-all plaster that allows all packages to ignore one > another. > > The real solution is for package maintainers to avoid patching other > packages, in your package, instead submitting patches to the upstream > packages maintainer. And concurrently, to give the user tools to notice > and control when this is happening. > > Memory is cheap, and cheaper every day. > > For an OS, it gets unfixably stuck too often. We have issues to solve here > much before we need layers.

1 0

Re: [ANN] [UPDATES] 18 updates for 3.4beta
by Bruce ONeel 21 Dec '02

21 Dec '02

Hi, ftp://st.cs.uiuc.edu//Smalltalk/Squeak/3.4beta/Squeak3.4b-5156.zip is now in place. Thanks! cheers bruce Scott Wallace <scott.wallace(a)squeakland.org> wrote: > Here are the preambles for eighteen updates that have just been > forwarded to the external 3.4beta update servers. > > 5139moreFileFixes-nk -- Ned Konz -- 30 November 2002 > This is a further attempt to get FileDirectory>>exists to work right > across platforms. > Unfortunately, this doesn't pass the FileDirectoryTests on the 3.2-6 > Unix VM or the 3.4.0Beta Mac VM. It does on the Windows VM, and I've > also posted changes to the Unix VM to make it work there. > However, this code should be the correct solution to the problem. > > 5140NoMacDoubleColon-nk -- Ned Konz -- 4 December 2002 > The change set 5131macRelativeFNFix-nk introduced an incorrect result > for the isAbsolute test on Mac filenames starting with a double > colon. This change set removes the double colon logic from the > isAbsolute test. > So with this CS the isAbsolute logic is: > * fileName starts with : -> relative > * fileName starts with the name of a folder under the root -> absolute > * otherwise -> relative > > 5141acornDirFixes-tpr -- tim(a)sumeru.stanford.edu -- 3 December 2002 > Catch a root directory being used as a path name in directoryExists: > to prevent recursion. Only affects Acorn machines > > 5142changeListHelp-sw -- Scott Wallace -- 3 December 2002 > Supplies balloon-help for all the items in the change-list menu. > Adds 'select new methods' to the change-list menu, whose choosing > will result in the selection of only those methods in the file that > do not currently have in-image counterparts. > > 5143AVCFix-nk -- Ned Konz -- 19 August 2002 > Some change sets that include definitions > of additionsToViewerCategories would not load correctly. > The problem is that a spurious method > UndefinedObject>>additionsToViewerCategories gets compiled sometimes, > and then breaks later code. > This CS is a quick patch for this problem. > > 5144findMethFix-je -- Joern Eyrich -- 4 December 2002 > avoid walkback when invoking 'find method...' on a class that has none" > > 5145prefsHeight-nk -- Ned Konz -- 3 December 2002 > Makes sure that all the buttons on the front pane of the Preferences > panel are visible. > Also adds a little space between a button group. > > 5146oneBitMVC-BEO -- Bruce ONeel -- 4 December 2002 > MVC was broken in one bit mode. > > 5147macColonAgain-nk -- Ned Konz -- 5 December 2002 > The change set 5131macRelativeFNFix-nk introduced an incorrect result > for the isAbsolute test on Mac filenames starting with a double > colon. This change set removes the double colon logic from the > isAbsolute test. > And my prior version (update 5140) was still wrong, as it consulted > the file system. > With this CS the Mac isAbsolute logic is: > If a path begins with a colon, it is relative. > Otherwise, > If it contains a colon anywhere, it is absolute and the first component > is the volume name. > Otherwise, > It is relative. > > 5148WeakKeyAssn-raok -- Dr Richard A. O'Keefe -- 29 November 2002 > Since at least Squeak 3.0, WeakKeyAssociation>>key:value: > has ignored its first argument and put the wrong object > in its key WeakArray. This mistake is still present in > Squeak 3.4. > > 5149ISO8859-bg -- Boris Gaertner -- 15 November 2002 > Jean-Marie Zajac pointed out that accented characters in ISO-8859-1 > encoding are not displayed as expected. Scamper is not > encoding-aware, but it translates ISO-8859-1 to the encoding that is > used in Squeak. Unfortunately, due to a subtle bug the translation is > done twice: first, the entire source is translated, later parsed > entities are translated again. This change set drops the translation > of parsed entites. To make it work, it adds the translation of > character entity references (characters that are written in the form > &#<integer>; or in the form &<character name>; see sections 5.3.1 and > 5.3.2 of the HTML 4.0 specification.) > Jean-Marie tested a first version and found a new bug, later he > tested a second version that is seemingly ok. With his test he helped > me to understand where the real problem was burried. Thanks a lot! > > 5150UUID-Fix-CdG -- Cees de Groot -- 19 November 2002 > This patch tries to make it less likely that the same UUID is generated twice: > - On startup, the default generator is flushed; > - The system tries harder to get a quality random seed, first from /dev/urandom > (on lots of Unix systems), then from the sound input. If they both fail, it > generates one based on the millisecond clock and the current date/time > > 5151DNSerror-ls -- Lex Spoon -- 3 November 2002 > This makes several DNS lookup failures to immediately abort the > surrounding HTTP or FTP request. Without this changeset, the system > will try to ask the user whether to try again. However, this query > doesn't work when the HTTP code is run from the user interface thread. > Instead of fixing the query, this changeset removes the query. The > idea is that, nowadays, these are low-level routines and that a > higher-level routine should be responsible for asking the user > whether to retry, anway. > > 5152ArchiveFixes2-nk -- Ned Konz -- 12 November 2002 > This fixes zip archive extraction so that: > - directories are created as needed > - zip members with absolute path names or '..' portions have their > names cleaned up so they don't cause security problems when extracted > This will allow (for instance) Connectors to install properly from SqueakMap. > I will include the appropriate methods with a new version of the > SARInstaller code on SqueakMap. > > 5153RelZipExtractFix-nk -- Ned Konz -- 16 December 2002 > Version: 3.4b > 16 Dec: > This fixes a problem with re-opening a zip in an ArchiveViewer under > Windows (by opening zips read-only), as well as fixing extraction > with subdirectories under Windows. > 13 Dec: > This ensures that zip extraction relative to a given directory works > properly, and should eliminate the infinite recursion noted on the > Mac. > It lacks AcornFileDirectory>>relativeNameFor: ; this should be added > if necessary before adding to the update stream. > > 5154FileListRefactor1-nk -- Ned Konz -- 7 December 2002 > This is a minor refactoring of the FileList that puts the services > query on the class side where it belongs (at least if you want to use > it for your own FileList, as I did). > > 5155WeakMessageSend2-nk-rw -- Ned Konz and Rob Withers -- 8 December 2002 (v2) > v2: Eliminated WeakMessageSendError; value* now silently returns nil > if receiver or arguments have been GC'd. > This defines a simple MessageSend where the receiver and arguments > are held onto weakly. > And it changes the NuBlue event registration to use the > WeakMessageSends instead, so that subscribers can be garbage > collected. > > 5156revertClassEditFix -- 17 December 2002 > Reverts the change made in 5137classEditFix-th which had made it > difficult to add class-side instance variables.

6 6

Latest patches freeze squeak
by Martin Drautzburg 21 Dec '02

21 Dec '02

I have followed all the patches via "update code from server". After installing the lastest patches I can no longer "save an exit". I get an excpetion MessageNotUnterstood: isReceiverOrAnyArgumentGa[rbage] (I cannot see all of it) ActionSequence(Object)>>doesNotUnderstand PasteUpMorph(Object)>>actionForEvent: PasteUpMorph(Object)>>triggerEvent: PasteUpMorph class >> shutDown PasteUpMorph class (Behavior)>>shutDown: an the Display freezes Alt. does not solve it. All I get is "User interrupt" and the display is still frozen. Can anyone help.

2 1

← Newer
1
...
5
6
7
8
9
10
11
...
46
Older →

Jump to page: