Squeak-dev July 2007

squeak-dev@lists.squeakfoundation.org

140 participants
214 discussions

Start a nNew thread

3.4 image download
by Thushar G R 27 Jul '07

27 Jul '07

Hi group, Could anyone pls tell me where to get a 3.4 image. Thanks in advance, G R Thushar

3 2

RE: Error updating universe list
by J J 27 Jul '07

27 Jul '07

> Date: Thu, 26 Jul 2007 14:05:13 +0100> From: keith_hodges(a)yahoo.co.uk> To: squeak-dev(a)lists.squeakfoundation.org> Subject: Re: Error updating universe list> > I have discovered that Universes do not appear to support Monticello > dependencies. This means that packages such as 'Magma Server' and > variants are not likely to work out of the box.How would that work? Monticello would need some way to flag branches as "stable", "dev" and so on so that the Universe would know which branch to use. _________________________________________________________________ PC Magazine’s 2007 editors’ choice for best web mail—award-winning Windows Live Hotmail. http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migrati…

3 2

[ANN] Swazoo web server 2.0 beta2 released
by Janko Mivšek 27 Jul '07

27 Jul '07

Dear Smalltalkers, I just published Swazoo 2.0 beta2 for Squeak and VisualWorks. What is new since first beta? 1. Input streaming of post data in requests, very handy for large file uploads; 2. Optimizations of HTTP responding, especially for large files. What is planned until final release? 1. Output streaming, that is responding in chunked format, which doesn't need a content length in advance. This is needed for downloading large files (streaming file content directly to a TCP socket) and also for responding to a request gradually, starting when part of web page is already ready, without waiting that a complete page is done. This will improve user perception of responsiveness of web apps. 2. More optimizations of input streaming; 3. Testing, testing testing! New beta of Swazoo is available on: - Squeak: on SqueakSource (http://www.squeaksource.com/Swazoo). - VisualWorks: on public Store (Swazoo 2.0beta2,mivsek) After installation you can start a simple 'Hello World' demo site. Follow instructions on http://www.swazoo.org/installation.html and short explanation on http://www.swazoo.org/documentation.html. Description of streaming with example, benchmarks and development notes is here: http://www.swazoo.org/streaming.html I hope that you will find Swazoo useful and help us achieve its main goal: to become a web server of choice for all dialects of Smalltalk. Best regards Janko Mivšek maintainer of Swazoo

2 1

[ANN] SuperSwiki2 upgraded
by Masashi UMEZAWA 27 Jul '07

27 Jul '07

Hi all, I have updated SuperSwiki2. http://swikis.ddo.jp/SuperSwiki2/3 SuperSwiki2 is a web application specially designed for e-Toys project sharing. It is a refactored version of the original SuperSwiki and has lots of improvements. You can see a sample site here: (in Japanese) http://squeakland.jp/super2 New features: - Language menu to change language dynamically - Simple Wiki - More fine grained access control - Backward compatibility with Old SuperSwiki (etc...) Platform Independent Downloads: http://swikis.ddo.jp/SuperSwiki2/19 Windows installer: http://swikis.ddo.jp/SuperSwiki2/18 I'll do SuperSwiki2 hands-on workshop in SqueakFest'07. Meet at Chicago! Regards, -- [:masashi | ^umezawa]

2 2

WeakRegistry>>finalizeValues & WeakKeyDictionary
by Igor Stasenko 27 Jul '07

27 Jul '07

I found few questionable places in WeakRegistry/WeakKeyDictionary which want to discuss with list. a WeakRegistry uses associationsDo: to determine which keys are GCed, and to collect values needed to send #finalize. There are at least two things to object: - why WeakRegistry shows up the keys = nil in associationsDo:, while in #keys, #keysDo: it just skips over them, indicating that there no associations with nil keys? This breaks the behavior consistency IMHO. - if you carefully check the WeakRegistry>>finalizeValues method, you'll see that dictionary will be scanned twice (first time in associationsDo:, second time in valueDictionary>>finalizeValues: ). Its scanned once only in case if there's no keys=nil and no values needed to be finalized. For both issues above, i think its better to add a method into WeakKeyDictionary , lets say #collectNilKeyValues , which will do good things for WeakRegistry by cleaning itself from nil keys and at same time return a collection of values needed to be finalized. And then, there will be no need to show up keys = nil in #associationsDo: and WeakKeyDictionary will behave as if there no keys=nil for any request outside. I'm also wonder, why WeakRegistry uses WeakKeyDictionary instead of WeakIdentityKeyDictionary. Just consider example: WeakRegistry default add: myObject executor: myExecutor. WeakRegistry default add: myObject copy executor: myCopyExecutor. (suppose myObject = myObject copy return true , and myObject hash = myObject copy hash too) I din't tested it, but i think that in result you'll get myCopyExecutor>>finalize sent when myObject will be GCed, but not its copy. -- Best regards, Igor Stasenko AKA sig.

1 2

[Meta] Standard packages?
by Andreas Raab 26 Jul '07

26 Jul '07

Hi - I just spent some in 3.10 and while I felt that there wasn't much that personally excited me about it, there were still plenty of fixes that were interesting enough for me so that I'll have to spend significant time to integrate them into Croquet. And if you look at what has recently gone into Croquet [1] I'm pretty sure you'll find the same the other way around (for example the font caching fixes come directly from Croquet). After looking over 3.10 it again occurred to me how splintered the larger Squeak community is when it comes to some of the core parts of its software. I think that at some point we'll have to admit that using individual images is a reality that we simply need to accept and deal with it accordingly. And one of the key parts is to understand how to share code across these different images. The trouble with code sharing is that the most important packages are still completely bound to particular images. There is no "Collection" package that I can load in from 3.4 through 3.10 and expect it to work. There is no common "Numbers", no "Streams", no "Files", Sockets, Sound, Exceptions, anything package. While there are plenty of application-level packages that support a range of images, there is almost nothing at the core of Squeak that can be used across different images. And I'm curious if there is interest in changing this. At least on the level where it's fairly non-controversial (e.g., I wouldn't be planning on starting with metclasses, m17n, or compiler) it could be a pretty interesting for various projects to be able to have a common code base, with decent tests to ensure it runs on all the the supported image versions etc. So that, for example, if there is an improvement to Dictionary you can benefit from it implicitly regardless of whether you are using a particular image or not. In short, what I'm looking for is something like a set of "standard packages" which are supported beyond the particular image they apply to. In thinking about this, two questions came to my mind: 1. Is this technically feasible? I'm not certain about this given how tightly various of the core packages depend on the particular idiosyncrasies of particular images. But it'd be interesting to find out whether (for example) we could make up a "standard Number package" that can easily be installed and supported in various versions. 2. Perhaps more importantly, is there any interest in doing something like this? Since it would most certainly require serious work it could only be done if other people feel the same like I do and are willing to put in some time and effort. If people are happy with where they are today (which is quite possible) then this is a no-win situation. *If* something like this works, it may be one step out of the image lock-in that we currently endure. It could also help focusing various (currently completely disjoint) parts of the community on help improving a shared base. Comments welcome. Cheers, - Andreas [1] https://lists.duke.edu/sympa/arc/croquet-dev/2007-05/msg00035.html

14 27

RE: Message Eating Null - article
by J J 26 Jul '07

26 Jul '07

What on earth are you talking about????? That is #inject:into:, known in functional programming as a fold. Perl doesn't even have a fold operator. The only part that looks bad is the block, and only because I don't know what #ifNotNil: returns if the block isn't nil. Plus with this I have the option of doing a home return when I first encounter the nil, while your Null will have to keep chomping until the end. :)> Date: Thu, 26 Jul 2007 20:06:32 +0100> From: keith_hodges(a)yahoo.co.uk> To: squeak-dev(a)lists.squeakfoundation.org> Subject: Re: Message Eating Null - article> > > >> >> > Yuck, I wouldn't do either of those. I would do:> >> > widget setStringValue: #(office phone lastNumberDialed asString) > > inject: person into: [:obj :sel| o == nil ifTrue: [ nil ] ifFalse: [ > > obj sel ] ]> >> > ------------------------------------------------------------------------> you would?> > To me the above looks as close to perl as smalltalk is hopefully ever > likely to get!> > ;-)> > Keith> > p.s. Someone once accused me of being a PL/1 programmer in a former life.> > _________________________________________________________________ See what you’re getting into…before you go there. http://newlivehotmail.com

3 2

RE: Message Eating Null - article
by J J 26 Jul '07

26 Jul '07

oh, and I forgot that I actually needed: obj perform: selFrom: azreal1977(a)hotmail.comTo: squeak-dev(a)lists.squeakfoundation.orgDate: Thu, 26 Jul 2007 19:23:42 +0000Subject: RE: Message Eating Null - article What on earth are you talking about????? That is #inject:into:, known in functional programming as a fold. Perl doesn't even have a fold operator. The only part that looks bad is the block, and only because I don't know what #ifNotNil: returns if the block isn't nil. Plus with this I have the option of doing a home return when I first encounter the nil, while your Null will have to keep chomping until the end. :)> Date: Thu, 26 Jul 2007 20:06:32 +0100> From: keith_hodges(a)yahoo.co.uk> To: squeak-dev(a)lists.squeakfoundation.org> Subject: Re: Message Eating Null - article> > > >> >> > Yuck, I wouldn't do either of those. I would do:> >> > widget setStringValue: #(office phone lastNumberDialed asString) > > inject: person into: [:obj :sel| o == nil ifTrue: [ nil ] ifFalse: [ > > obj sel ] ]> >> > ------------------------------------------------------------------------> you would?> > To me the above looks as close to perl as smalltalk is hopefully ever > likely to get!> > ;-)> > Keith> > p.s. Someone once accused me of being a PL/1 programmer in a former life.> > See what you’re getting into…before you go there. Check it out! _________________________________________________________________ PC Magazine’s 2007 editors’ choice for best web mail—award-winning Windows Live Hotmail. http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migrati…

1 0

RE: Error updating universe list
by J J 26 Jul '07

26 Jul '07

Ah right. My bad. But I still like the idea of the revision system providing some kind of tagging so the Universe code can automatically look for updates in specific "guaranteed to be stable" branches.> Date: Thu, 26 Jul 2007 19:23:56 +0100> From: keith_hodges(a)yahoo.co.uk> To: squeak-dev(a)lists.squeakfoundation.org> Subject: Re: Error updating universe list> > I am not saying that Monticello doesnt know how to provide resolution of > Universe dependencies.> > I am saying that if you install a monticello package from a url, and > that package attempts to load other 'specific' packages due to its > internal dependencies, the url loading context may have no repositories > registered in which monticello can look to find those requirements.> > Keith> _________________________________________________________________ Don't get caught with egg on your face. Play Chicktionary! http://club.live.com/chicktionary.aspx?icid=chick_wlmailtextlink

1 0

RE: How to access stdout on Mac OS X when using open
by J J 26 Jul '07

26 Jul '07

stdout is normally buffered (no idea how OSProcess is implemented). Maybe you need to send a #flush command first?> To: squeak-dev(a)lists.squeakfoundation.org> From: Serge.Stinckwich(a)info.unicaen.fr> Date: Thu, 26 Jul 2007 10:02:59 +0200> Subject: How to access stdout on Mac OS X when using open> > Hi all,> i'm using OSProcess to write something on the mac OS X terminal but when > i execute : OSProcess thisOSProcess stdOut nextPutAll: 'Hello World'. > nothing seems to happen ...> > I'm using Squeak 3.8.18beta1U Mac OS X VM, sq3.9-7067dev07.01.1 image > and OSProcess 4.3.3. I launch Squeak from the terminal with the open > command.> > When i launch the Squeak binary inside the Squeak application,> the previous expression write the 'Hello World' string on the terminal.> > > -- Serge Stinckwich> http://doesnotunderstand.free.fr/> > _________________________________________________________________ Don't get caught with egg on your face. Play Chicktionary! http://club.live.com/chicktionary.aspx?icid=chick_wlmailtextlink

1 0

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

Jump to page: