Squeak-dev August 2004

squeak-dev@lists.squeakfoundation.org

154 participants
394 discussions

[ANN][Jacaranda] Squeak 3.7 version released
by Hernan Tylim 04 Aug '04

04 Aug '04

Hi, I just wanted to comment that its available on SqueakMap a new version of Jacarandá which will work on Squeak 3.7. Please take into account that this version is just the old one but with Squeak 3.7 compatibility. A new version of Jacarandá for Connectors 2 will be released hopefully shortly. P.S: As usual the Jacarandá loadscript will load everything it needs. Regards, Hernán

1 0

[DEPS][SM] bounce problem
by Stephan Rudlof 03 Aug '04

03 Aug '04

Dear All, probably I've missed postings here for about 3 hours, so: if I don't reply to a mail, where you expect I should, please send it to me again... I've just gotten a bounce problem mail (never gotten such a thing before) and reenabled my account here. I'm writing this since I'm currently quiet involved in some discussions regarding the tags in the subject line... Thanks, Stephan PS: In a few hours I'm away from here until the weekend. -- Stephan Rudlof (sr(a)evolgo.de) "Genius doesn't work on an assembly line basis. You can't simply say, 'Today I will be brilliant.'" -- Kirk, "The Ultimate Computer", stardate 4731.3

1 0

Re: [FIX][3.7] DeprecatedFixesFor37-nk
by Doug Way 03 Aug '04

03 Aug '04

This changeset makes a lot of changes, around 70 methods. I'm not sure if they're really critical for 3.7 at this late stage. I think it's probably OK to have some sends to deprecated methods in the final release... those methods will still work. (Hmm, I guess it could be annoying to test your own app in 3.7 for deprecated methods by turning on deprecationWarnings, and then have a bunch of popups come up for things in the release which are still calling deprecated methods... but still, it's not a critical problem IMHO.) Plus I see at least one bug in here... SmalltalkImage>>aboutThisSystem calls #m17nVersion, which doesn't exist. These fixes should all go into 3.8alpha, of course. If there are any really important bug fixes in here for 3.7, we could separate them and incorporate them. Any other thoughts on this? - Doug p.s. still shooting for putting out a 3.7gamma candidate tonight, and 3.7final on Sunday or so if all goes well. On Tuesday, August 3, 2004, at 10:02 AM, Ned Konz wrote: > from preamble: > > "Change Set: DeprecatedFixes3.7g-nk > Date: 3 August 2004 > Author: Ned Konz > > Fixes for > > - sends of various deprecated messages to well-known globals like > Smalltalk > > - double-initialize in constructors > > Deprecates some new methods in SystemDictionary and moves them to > SmalltalkImage. > > "! > <DeprecatedFixesFor37-nk.cs.gz>

2 1

CVS innaccesible?
by Tim Rowledge 03 Aug '04

03 Aug '04

Dang! I can't seem to get sourceforge to talk to my cvs program on either the Acorn or my winXP laptop - both of which used to be fine. Is it working for anyone out there? tim -- Tim Rowledge, tim(a)sumeru.stanford.edu, http://sumeru.stanford.edu/tim Useful random insult:- She's a screensaver: Looks good, but useless.

4 6

Re: Morphic, I still don't get it...
by Lyndon Tremblay 03 Aug '04

03 Aug '04

I'll reply to myself here, as it was prematurely sent. > Why stop at a GUI builder? why not go for a full application/object builder? > Squeak itself is already this. Having a GUI builder seems somewhat like > having a chair on a bench... perhaps this can still be desireable, though. > > Why not say something like... Squeak's factory interface objects are "not > good"? > "Not visually pleasing or consistant enough"? Etc. > > Atomically, consistance/standardism here consists of sharing the same class > and class heirarchy. Ie. if it is a Morph and also a BasicButton, it can be > considered a standard button "widget". Though BasicButton is only a template > or convenience wrapper for a predefined definition of a Morphic state > representing a basic button; enough to draw, show clicks, carry out itself. > As long as media(external) and memory(internal) technology remain seperate, their interfaces and representation always will as well. The class library is an interface to memory; concerning objects, functionality, and comfortable concepts and ideas for working with it. Age and maturity has neared this basic Smalltalk core foundation to a state where it is difficult to "make better" - near perfection, to where itself and its dependants (implementors, users, inspirators) are concerned. The class library for visual representation is imperfect, and perhaps always will be. The guts of this is memory and data. When the distance between visual and nonvisual representations actually shortens, as is the case especially with Morphic - you can start considering changes like "what to name a variable or method" as "what color to choose, what line thickness to choose"... --Lyndon > From: "Noury Bouraqadi" <bouraqadi(a)ensm-douai.fr> > > > > Hi, > > > > lex(a)cc.gatech.edu wrote: > > > > >Everyone, be aware that there are also "rubber stamps" available; they > > >simply aren't in the main image. Check out things like Bob's UI, Prefab, > > >or Zurgle. > > > > > > "GUI Building Tools" > > > http://minnow.cc.gatech.edu/squeak/1576 > > > > > >It is probably worth picking one of these and making it available > > >in a "full" image in the future, along with a good Play With Me that > shows > > >how to use it. IMHO, we should accept into the "full" image the first > GUI > > >library whose maintainer promises to build and maintain a Play With Me > > >for it. > > > > > > > > > > > Yes, I totally agree. The question about GUI building is too recurent. > > > > > > -- > > > > Noury > > ------------------------------------------ > > Dr. Noury Bouraqadi - Enseignant/Chercheur > > Ecole des Mines de Douai - Dept. G.I.P > > http://csl.ensm-douai.fr/noury > > > > European Smalltalk Users Group > > http://www.esug.org > > > > Squeak: an Open Source Smalltalk > > http://www.squeak.org > > ------------------------------------------ > > > > > > >

1 0

[BUG][FIX] WeakGCFix-wbk
by bryce＠kampjes.demon.co.uk 03 Aug '04

03 Aug '04

from preamble: "Change Set: WeakGCFix-wbk Date: 21 March 2004 Author: Bryce Kampjes Weak references can leave dangling pointers if the weak object is in old space and it points to a new space object. The problem occurs when the new space object is incrementally collected but the old space weak object remains. The weak object now has a dangling pointer to where the new space object was. This change set adds a little code to ObjectMemory>>sweepPhase so that it will finalise any weak rootTable objects. There is still the chance that an interpreter variable may contain a pointer to a weak object. However interpreter variables have very specific uses. I'm not sure if they should be checked for weak references. "!

5 14

[FIX][3.7] DeprecatedFixesFor37-nk
by Ned Konz 03 Aug '04

03 Aug '04

from preamble: "Change Set: DeprecatedFixes3.7g-nk Date: 3 August 2004 Author: Ned Konz Fixes for - sends of various deprecated messages to well-known globals like Smalltalk - double-initialize in constructors Deprecates some new methods in SystemDictionary and moves them to SmalltalkImage. "!

1 0

RE: [BUG] ReviewerPost(Object)>>doesNotUnderstand: #morph trying to post a review from BFAV2. ([closed] - reported in another thread)
by Frank Shearar 03 Aug '04

03 Aug '04

Yep, we know about this bug (several other people have reported it already). We've fixed it in the latest SqueakSource version. We'll release that Real Soon Now - we're just waiting on some reports from heavy users who use the bleeding-edge BFAV versions as to whether we've missed anything. BFAV has become a vital part of the Squeak community, and we appreciate the patience of the community in not throwing tomatoes at us! frank > -----Original Message----- > From: German Arduino [mailto:gsa@softhome.net] > Sent: 29 July 2004 12:38 > To: squeak-dev(a)lists.squeakfoundation.org > Subject: Re: [BUG] ReviewerPost(Object)>>doesNotUnderstand: #morph > trying to post a review from BFAV2. > > > To fix it, as Göran said in irc, in: > > DecentReviewerNotepad>>send > > change: self morph allMorphsDo: [ :aMorph | (aMorph > respondsTo: #accept) > ifTrue: [aMorph accept]] > > by: self allMorphsDo: [ :aMorph | (aMorph respondsTo: > #accept) ifTrue: > [aMorph accept]]. > > (Remove the morph word). > > gsa. > > > When I press the button Send, to post a review from > Reviewer Notepad I > > get the error of the subject. > > > > I've installed BFAV with the proper install package. > > > > Attached is the log. > > > > Thanks. > > gsa. <snip> ******************************************************************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent RNID policy. If you are not the intended recipient you are advised that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. If you have received this email in error please notify the RNID Helpdesk by telephone on: +44 (0) 207 296 8282. The Royal National Institute for Deaf People Registered Office 19*23 Featherstone Street London EC1Y 8SL No. 454169 (England) Registered Charity No. 207720 ********************************************************************

3 2

Squat progress 2 August 2004: "imprinting"
by Craig Latta 03 Aug '04

03 Aug '04

Hi-- I've implemented the more brute-force means of transferring behavior on demand, as mentioned in my 3 July message. I have successfully transferred, from one snapshot to another, all the methods run in the first million sends of an application, without using the compiler, and without any special consideration for which methods those were. I call this process "imprinting". The main benefit of this approach, as I'm using it now, is making an application smaller by leaving unused behavior behind. (This is useful because I want to minimize the download time of the resulting snapshot.) I can see other interesting uses as well; for example, "behavior broadcasting", in people "tune in" to a running system (e.g., at a demo during a conference), and come away with all the behavior needed to run the demo again for themselves. It's also a good way of transferring unmodularized behavior from one place to another without having to understand its architecture or dependencies. [This reminds me a little of the first Matrix movie, where characters have martial-arts or helicopter-flying skills imprinted onto them. :) But notice they didn't start fighting or flying before the imprinting was finished. That'd be similar to the first on-demand transfer approach I tried, and later shelved (see the Squat mailing list archive). I suppose for reference I'll call the previous approach "active imprinting", and the current one "passive imprinting".] The process works by running the application in a copy of the source snapshot (the "input" snapshot), which reports the ID of each method run to the original source snapshot (via a special virtual machine); the source then ensures that the corresponding methods are installed in the target. The communication between the input and the source, and between the source and the target, is done with remote message-sending (a message-event server in the input sends messages to a message-event client in the source, which then sends messages to a Squat module in the target). In my current sessions, the source is a 3.6 snapshot, and the target is a 2.2 snapshot. This encourages me that the technique will work between snapshots of any likely vintage. -C -- Craig Latta improvisational musical informaticist craig(a)netjam.org www.netjam.org [|] Proceed for Truth!

2 1

[ANN] fresh Glorp port
by radoslav hodnicak 03 Aug '04

03 Aug '04

Glorp 0.3.80 is available on SM. Note that this version will work in 3.6 (and likely in some older versions) but not in 3.7 Glorp is object-relational mapping framework somewhat similar to TopLink, developed by Alan Knight. Regards, radoslav -- "Everyone wins, except art and people with brains or education" - Dr. Thorpe

1 0

Jump to page: