Squeak-dev October 2003

squeak-dev@lists.squeakfoundation.org

178 participants
791 discussions

[ENH] UsableSiblingInstanceFix-nk
by Ned Konz 04 Aug '04

04 Aug '04

from preamble: "Change Set: UsableSiblingInstanceFix-nk Date: 11 October 2003 Author: Ned Konz Morph>>usableSiblingInstance was always adding the created sibling to the World, even though many of its callers would turn around and immediately add the result to other morphs or delete them from the World. This change set makes #usableSiblingInstance not add the newly created Morph to the World. This makes several uses of #usableSiblingInstance more bug-free and efficient. "!

2 1

[BUG][FIX] Morphic: File Selection Dialog [was MVC: File Selectio n Dialog]
by Magistrello Alejandro (SFA) 04 Aug '04

04 Aug '04

>De: Boris Gaertner [SMTP:Boris.Gaertner@gmx.net] >Asunto: Re: [BUG][FIX] MVC: File Selection Dialog (shows another bug) > >I tried to execute > (PluggableFileList oldFileMenu: (FileDirectory on: 'c:\windows\fonts')) > startUpWithCaption: 'Select a File, please:' >in a Mrophic project and receive a strange effect, that I cannot quickly >fix: >I put that statement into a workspace that I place more or less centered >on the screen. When I execute the statement, the selection dialog is >displayed above the workspace. This looks good, but as soon as a >call up one of the menues of the dialog, the selected text of the workspace >comes into the foreground. >I think that in PluggableFileList>>open one should have something like > Smalltalk isMorphic > ifTrue: [<...>] > ifFalse: [<...>] > >I tried to do that, the result can be found in MorphicFSD.1.cs <<MorphicFSD.1.cs>> >In SystemWindow>>update: I added a reaction to the >message #close. >In PluggableFileList>>openAsMorphLasbel:inWorld: >I added an event loop. The condition of the loop uses the >fact that the model of a SystemWindow is niled when the >window is deleted. >I am not very experienced user of the Morphic interface, >so comments are highly wellcome. > > >Greetings, >Boris > if you use the closeButton you'll get a walkback. btw, this is pretty similar to FileList2 modalFileSelector regards, Alejandro

2 1

[ENH] ExceptionDialogs-avi
by avi＠beta4.com 28 Jul '04

28 Jul '04

from preamble: "Change Set: ExceptionDialogs-avi Date: 31 August 2003 Author: Avi Bryant Adds Notifications for #inform:, #confirm:, and #confirm:orCancel:. By default these still use PopUpMenu, but they could be caught and dealt with more appropiately in different UI contexts."!

2 1

[ENH] ReUseViewerFlaps-nk
by ned＠bike-nomad.com 28 Jul '04

28 Jul '04

from preamble: "Change Set: ReUseViewerFlaps-nk Date: 21 September 2003 Author: Ned Konz This is a minor change for the eToys environment that will re-use an existing viewer flap when you open a viewer from an object halo. "!

2 1

[bug] stack overflow crashes Squeak.
by Michael van der Gulik 06 Jul '04

06 Jul '04

Hi all. If you make a naive class that calls itself: Forkbomb>>forkbomb ^ self forkbomb. Squeak 3.5 on Debian linux will eventually crash, leaving a huge stack dump in the terminal. Okay; it's really my fault for making such a stupid class, but I'm playing around with proxied objects, message sends etc and it's happening quite often while I'm debugging. Is there a way to limit the invocation stack to a sane level of deepness, after which a process/thread (whichever is Squeak terminology) gets suspended and an error thrown? Same probably applies to number of processes made by a thread. mikevdg.

12 19

The Magic Book - a design draft
by goran.hultgren＠bluefish.se 30 Jun '04

30 Jun '04

The idea of a "Magic Book" inside Squeak acting as both an introductory documentation for Squeak and as a reference manual is quite intriguing. A few basic ideas that got this started: - Tying unit tests to documentation in order to detect stale documentation - Not bloating the image - Easily maintain the book cooperatively (like swiki) Ok, what would be the STTCPW? (For all you non XP aware: "Simplest Thing That Could Possibly Work"). By applying reuse - what do we already have? We already have: - Projects: A very good format for "active content". I am not sure how easily they are backwardscompatible though. Could anyone post some insight in that matter? - StarBrowser: A universal UI kindof thing. We could easily let StarBrowser be the main UI of the Magic Book! It lends itself easily for the task - a treeview on the left, a dynamic area to the left etc. If we somehow find a good way to integrate a little search form then it would be quite perfect. - SqueakMap: In whichever form we choose to have the Chapters of the book (Projects) we could register them on SM (a few new categories would be nice) and thus get a distributed always up to date model of chapters for free. And when SM1.1 gets completed it will track versions of the chapters for us, etc. And in SM1.1 it will have a sensible smart diskcache for the packages (read Chapters) so we get that too. - Free text engine: Scott Crosby wrote a neat little engine for maintaining keyword indices that the book obviously should use. I have also been intending to integrate that into SM. We should be able to add it to SM in such a way that the Magic Book can simple get that "for free". So... we already have a bunch of cool technology to implement the Magic Book IMHO. We just need to knit it all together in a smart way. If we split the book in the following pieces: 1. The TOC. This is essentially a list of chapters organized in a hierarchy with names and a link to the corresponding SM package that is the chapter content - a Project. 2. The chapters themselves. These are simply Projects published as packages on SM. Perhaps we need to follow a few conventions for these Projects so that we easily can "jump into" them in a proper manner, extract keywords for indices etc. 3. The search indices and the index (as books have last). If 1 and 2 above also are packages on SM (in whichever suitable form, doesn't matter) it will be even more simplified. So the book *contents* are then managed as packages on SM. We get the possibility of having different owners for different chapters, release/version tracking etc. It is obvious when you think about it - why shouldn't they be packages? The StarBrowser is the obvious choice of a UI - it already has navigation mechanisms and it can also show contents from the book along with other things in a highly dynamic fashion. Why reinvent that? And SqueakMap gives us a lot of stuff like efficiently always updated content, a smart cache etc. And there will be no image bloat whatsoever. Well, ok, what do you all think? Darn, this sounds like real fun... I need to get cranking at my SM1.1 ... :-) regards, Göran

2 1

[BUG][FIX] PostscriptCharacterScanner DNU #setAlignment:
by Richard Staehli 04 Jun '04

04 Jun '04

This bug has been around a while, but I just discovered the workaround someone posted on the swiki. The problem can be reproduced simply: - in 3.6 image, open a new StackMorph - add a TextMorph to the first page - set text alignment to centered - from the Stack's red "menu" halo button, select "copy & print" -> "print Postscript to file" and accept defaults. - a walkback appears: "PostscriptCharacterScanner doesNotUnderstand: #setAlignment:?" This problem can be fixed by the suggestion posted on the swiki's "Postscript support" page. The fix is to modify the class 'PostscriptCharacterScanner' to be a subclass of 'CharacterScanner' and remove from the former the instance variable 'font'. I do not know if this fix causes other problems. Here is the change to PostscriptCharacterScanner: CharacterScanner subclass: #PostscriptCharacterScanner instanceVariableNames: 'canvas paragraph bounds curPos foregroundColor emphasis ' classVariableNames: '' poolDictionaries: '' category: 'Morphic-Postscript Canvases'

3 3

[BUG][FIX]MouseMoveEvtStartPos-ar
by Eddie Cottongim 04 Jun '04

04 Jun '04

>From Preamble: "Change Set: MouseMoveEvtStartPos-ar Date: 18 August 2003 Author: Eddie Cottongim Fixes a bug where MouseMoveEvents would not report their startPosition correctly. Change by Andreas Raab." To observe this bug, execute "HandMorph showEvents: true" and observe the starting point for mouse moves. Its usually wrong - most of the time, start point = end point. It makes much more sense after the patch. The change makes sense to me. startPosition is now set to the hand's current position. Since the hand hasn't yet been moved in response to the event being formed, it makes sense that the hand's current position will the the starting point for the next mouse move event. Someone should see if this helps/hurts Genie - Genie uses the start position for mouse moves. I'm suprised it would work at all given the old, broken behavior. Thanks, Eddie

3 2

RSS library?
by Brent Vukmer 04 Jun '04

04 Jun '04

Anybody got a RSS library available in Squeak, that they're willing to share?

16 51

[BUG] ExceptionTester>>simpleOuterTest fails
by Marcus Denker 29 May '04

29 May '04

ExceptionTester>>simpleOuterTest fails (3.6beta 5395) Reproduce with (ExceptionTester is part of the BaseImage Test Package): ExceptionTester new runTest: #simpleOuterTest) suiteLog Here's the test: simpleOuterTest "uses #resume" [[self doSomething. MyTestNotification signal. self doSomethingElse] on: MyTestNotification do: [:ex | ex outer]] on: MyTestNotification do: [:ex | self doYetAnotherThing. ex resume] -- Marcus Denker marcus(a)ira.uka.de -- Squeak! http://squeak.de

4 4

Jump to page: