Squeak-dev November 2008

squeak-dev@lists.squeakfoundation.org

119 participants
135 discussions

Re: [squeak-dev] Re: what is holding back Smalltalk?
by Paul D. Fernhout 22 Nov '08

22 Nov '08

Jecel Assumpcao Jr wrote: > [Something snipped on clean room implementations.] > But to understand what happened to Smalltalk you must look at the > history more than at technical aspects. I don't know a good text I can > link to, but Eliot spent some time on this in his AoSTA talk - > http://video.google.com/videoplay?docid=-8988857822906068209 I wrote some on this to a Python-related list (Edusig) about two years ago it various posts. Some excerpts: "[Edu-sig] Freedom: some Smalltalk history and Python implications" http://mail.python.org/pipermail/edu-sig/2006-August/006871.html """ In the syntax case, I am continuing to point out that Smalltalk's keyword syntax (e.g. "Point x: 10 y: 20" versus "Point(10, 20)" ) produces code where all arguments are labeled and so it is easier to read and understand. As I see it, that is a fact independent of licensing, object models, breadth of libraries, size or quality of community, or engineering reliability of the VM, and so on (areas which Python often has as an advantage over any specific Smalltalk). ... And I am still unable to bring across the massive decrease in effectiveness and immersion I feel programming a large system in Python compared to Smalltalk, like were when an exception is raise I cannot immediately change the code and then carry on from the point in the program where the exception was generated, without either restarting the entire application. ... Now, I have repeatedly agreed Python has many benefits over Smalltalk. You've mentioned some. I'll add, Python is more "prototypish" than Smalltalk because it uses a dictionary instead of fixed slots for variables (at least, usually) which make it easy to specialize instances of a class. Python as a major language had a free license unlike the major Smalltalk dialects (i.e. there are free Smalltalks but they are still marginal to the overall Smalltalk community, Squeak being the closest to an exception). Python has had its internal complexity managed fairly well, compared to say, Squeak because of having namespace from the start. I like indentational syntax (though not as much as keywords). Metaclass support is nice. And so on. """ "[Edu-sig] Freedom: some Smalltalk history and Python implications" http://mail.python.org/pipermail/edu-sig/2006-August/006868.html "Anyway, I don't want to drift too far off-topic. Suffice to say, if there is any truth to Smalltalk being a "dead" language, it has more to do with companies mismanaging the technology, and not the technology itself. Python has been well managed as a labor-of-love by someone who cares about it for itself (Guido) and as a community Python could ride the free and open source software wave without distracting conflicts with "commercial Python vendors". Squeak tried, but was both a latecomer and not completely free, and had some other difficulties (including for a long time a core team with priorities other than stability or supporting industrial use)." "[Edu-sig] Python & Smalltalk (was Re: OLPC related: pyGTK)" http://mail.python.org/pipermail/edu-sig/2006-December/007476.html """ Smalltalk came out of an industrial research lab (Xerox PARC). The people who invented and then built it and refined it were paid industrial employees working in the scope of their duties on company time (though very unusual ones, even by such R&D standards. :-) Its subsequent history for decades involved mainly development by commercial organizations (either as Smalltalk or also as the Macintosh OS which in some sense was a Smalltalk-derivative, but Steve Jobs just got the window system because he left too soon. :-). http://gagne.homedns.org/~tgagne/contrib/EarlyHistoryST.html ... Smalltalk's demise as a major player on the commercial scene in terms of VisualWorks and its predecessor ObjectWorks (*the* leading Smalltalk product, and still the most comprehensive and definitive and most cross-platform -- excepting perhaps Squeak is more cross-platform in theory) was mostly due to greed and mismanagement IMHO by a now defunct company (the current VisualWorks owners bought it cheaply from them). IBM's VisualAge Smalltalk's demise, on the other hand, was mostly due to IBM's decision to back Java (shortsighted and unfortunate I think as IBM had the clout to push Smalltalk syntax through to the masses IMHO). Smalltalk is still actively used by many, but is more of a niche player at the moment (like, say, OCaml or Haskell or Common Lisp), having been eclipsed by Java. The support community for Smalltalk was (at first) mostly commercially oriented, and remains so to some degree. While there were academic users, and in the past decade, especially with Squeak, the number of people using it for academic or free or open source type applications has grown, that has not been the bulk of the history. Even Squeak's most recent evolution was driven by work at Apple and then at Disney, with the Smalltalk principals reprising their roles as employees of large industrial research and development labs, with the licensing ambiguity that sometimes entails in navigating for-profit corporate waters in an emerging free-and-open-source way (i.e. Alan Kay claims Disney is OK with the Squeak changes done there being released, but there is no "peace of mind" letter from Disney signing off on them I am aware of, or related licensing statement in the code). Python on the other hand, was started as a hobby by one person who was based in an academic research lab. It was always given freely. Excepting one bobble with licensing issues (which was corrected and involved a not-for-profit), the licensing situation has always been pretty straightforward from a free software perspective (and is even now GPL compatible). For most of Guido's time with python (except the last few years) he was affiliated with one of two non-profits. Even now his job is at a pro-"open source" corporation which is also releasing several other free and open source projects. The community that grew around Python, while with many commercial users, had a very different emphasis to it. Part of that early community spirit was also from the "Monty Python" humorous yet playfully radical themes (although Guido has said by now he has heard enough Monty Python jokes. :-) Python also has one core definitive free code base as a reference standard implementation (even as there are spinoffs like Jython). Personally, I feel Smalltalk is the better syntax for kids to learn as that purpose was what it was supposedly designed for (if you ignore that most adult programmers come from Algol syntax and have trouble adapting to the syntax initially); Smalltalk keyword: syntax is certainly the easier syntax to use to maintain large bodies of code using powerful tools and is easily extendable by the end user programmer for many new uses including new control structures and iteration concepts; Smalltalk historically also has the better development tools (in part due to the syntax) and also has a better library architecture (e.g. Streams, Magnitude) and better VMs and garbage collection(especially in VisualWorks, and less so in Squeak), and also has benefited from a culture of Smalltalk all-the-way-down (as Squeak exemplifies); Smalltalk has a powerful notion of bracketed nameless code blocks and is a tour de force of one paradigm (objects and message passing). However, Python has the better community (from a free and open source perspective), better license and licensing history, and better breadth and modularity of libraries; Python also is more easily taken up by adult programmers who already know C or a similar Algol-style language because of its Algol-like syntax and also because you can use familiar text-oriented tools like emacs or vi or Scite with it (which makes it easier for it to gain commercial acceptance as a new thing); Python code is clear and concise and maintainable because of the decision to use significant indentation instead of braces or brackets (like Occam); Python also is a standard defined by a reference implementation, which is much better than a standard defined by an ambiguous or incomplete textual specification; Python is easier to do small projects in for people who only know a little of the language, so in that sense it has an easier learning curve as a system. I feel, especially with Ruby's increasing popularity [as effectively a Smalltalk with Algol syntax plus some other bells and whistles], that the *themes* in Smalltalk are the future of most programming. Even Python continues to get more Smalltalk-like, such as the "new classes" changes. Yet, I want to write some programs now, as part of a free and secure ecosystem of such programs. :-) Ironically, in my own case as a typical Smalltalk programmer, because of my own history as a Smalltalk developer working on commercial projects with commercial versions which nonetheless included source as most Smalltalks do, I am in some ways "contaminated" by that experience and the current overly broad reading of copyright and that puts into potential question anything I develop which is a Smalltalk-derivative (unless I do it very, very carefully, say by using mostly GNU Smalltalk sources); not to say I ever would use such commercial code, just that I might face the effectively impossible task of proving I had not if there was any coincidental similarity at all (which is a much smaller problem when I am working with something very different like Python). If I perhaps oversimplify, essentially the choice right now is between elegant syntax, uniform abstractions, and powerful tools, embodied in a system originally designed for kids by big corporate R&D (Smalltalk) versus practical syntax, uniform community history of freedom, and powerful economic forces, embodied in a system originally designed for adult programmers by an academic researcher as a hobby project which grew beyond initial expectations (Python). :-) Both languages along with their communities have different strengths and weaknesses, and also both have subcultures which are in opposition to the main (e.g. mostly commercial Smalltalk has several free versions, mostly free Python has heavy proprietary commercial usage where no doubt such users have large interesting and yet proprietary libraries). That the strengths and weaknesses are so different in different areas and that one must also assess where trends are heading when embarking on big projects is why I am in conflict about which to use (especially for writing educational simulations), and that is why I tried to mix the best features of the two in the PataPata experiment -- though perhaps ended up with the worst features of the two in some ways (Smalltalk's . :-). Barring moving that PataPata project forward somehow, I am left with a situation that I either have to put a lot of work into a free Smalltalk (Squeak, GNU, A Little Smalltalk, Bistro, Sharp Smalltalk, etc.) to make it more to my liking (e.g. mainstream widgets for Squeak, build tools for GST or Bistro, etc.) or I have can use Python + GTK or wxWidgets or Jython + Swing out of the box, and just accept greater maintenance issues down the road (e.g. debugging and modifying a running program is so easy in Smalltalk, in Python it doesn't quite work right, even with tools I have built to make it easier [posted to the Jython list]). While I haven't made a big point of it, in the past, my choice of Python in the past has also been motivated by the "contamination" issue I mentioned above as well. It may well be the deciding factor once again, sadly -- ironic to not be able to use and improve a wonderful thing you have experienced precisely because you have experienced it.(*) :-( """ "[Edu-sig] Python & Smalltalk" http://mail.python.org/pipermail/edu-sig/2006-December/007482.html """ On a practical reality, I fired up the latest Squeak the other day and beyond my usual confusion with it relating to not mapping right mouse to popup a context-determined menu, :-) within minutes I was generating exceptions and so on as I tried to use other-than-trivial code included with the system (e.g. running the script to change underscores to colon equals, as well as some other things I forget off hand). I knew more than one person who in years past inspired by an Alan Kay presentation have tried Squeak only to encounter lots of bugs and problems with the core tools or trying to duplicate the demos he shows. Python never has done that to me. That's why I tend not to recommend Squeak to anybody but either die-hard Smalltalkers or people looking specifically to stretch their minds (which of course in theory includes kids :-). Whereas almost all the people I recommend Python to, on a practical basis, come away impressed and become users; Python fits into their ecosystem of tools and existing ideas fairly easily. That makes me sad because I know Smalltalk does not have to be that way; I know if I recommended, say, VisualWorks to people, they would not be experiencing those basic problems (and there is no reason Squeak's features like eToys or 3D Croquet could not run on such a stable platform, in theory). Unfortunately VisualWorks is not "free" in a "free as in freedom" sense the mainline Python version is. Of course I could fix Squeak's specific problems (as I see and experience them) with enough effort (in theory, with enough free time, which is limited at the moment), since the source is there. But then I am left with the licensing issues including the status of Disney contributions (which the community is slowly moving to resolve). And then I have my own fork to maintain, which is extra effort. I have wrestled with the Squeak community before on those issues, and realized, like any community and mailing list, a self-selection process has already gone on a long time there, so if you don't like Squeak how it already is, you are probably not hanging around on the main lists there. So there may be plenty of people who want a different Squeak, but most of them are not easily reachable (at least via the Squeak mailing list). The Python community is more inclusive by comparison, in the sense that Python as a language is much more agnostic on several points (including GUI and tools). So there is more room for experimentation there in some ways. Or, at least, there is a bigger potential audience of users and collaborators for a successful experiment, like perhaps the Pyglet OpenGL GUI system you mention. Python better supports such effort in some ways because of its modularity and community history (which I outlined previously). Some Squeakers have been so defensive for so long (often, though not always, with good reason) that innovation or adopting certain standards is harder there (witness a recent conflict about whether keyboard input focus should follow the mouse (Squeak) or follow a mouse click to shift focus (almost everyone else), not to say there isn't a good argument for the Squeak way). Plus, the copyright "contamination" issue sadly will always remain; there is no denying I have exposed to the source of commercial Smalltalk incidentally in the process of using them. I could never work in a Smalltalk-rebuilding "clean room" effort. In other free software development contexts, say, people working on GNU ClassPath as an alternative set of libraries to Java, the biggest "no, no" is to have seen a related vendor's source and then contribute to that project. Example: http://developers.slashdot.org/article.pl?sid=05/03/17/0155235 "Read the fine license, in particular the definition of Modifications in SCSL 2.3. Sun claims copyright on any code independently implementing any portion of the SCSL-licensed technology *if* you agree to their license. So please don't look at their code if you intend to contribute to free runtimes in the future. It's the same as Microsoft's Shared Source in a different wrapping." There is probably almost no significant Squeaker who has not been exposed to the core code of one of VisualWorks, Smalltalk/V, Dolphin, VisualAge, or a few other commercial Smalltalks. Of course, how well an overly broad attempt against Squeak would stand up in court is a different issue; it certainly also would not play well politically in terms of negative PR to the vendor. In some ways, in the end, this single issue may mean the death of free Smalltalks long term (barring one major vendor freeing their version) -- the fact that Smalltalk was "open source" (taken literally) embodied in proprietary products for so long but not "free". Which is one reason Richard Stallman dislikes the term "open source" as it deemphasizes the freedom aspect. :-) In essence, the history of Smalltalk is "brilliance shackled". Since its conception, the history of Python is "pragmatism unshackled". :-) """ Personally, I still feel that now that the JVM is free-as-in-freedom, a Squeak derivative on the JVM has the possibility of being an amazing success (perhaps one built step-by-step using GNU Smalltalk parts to deal with licensing issues). But it would take most of the community here getting behind it. Maybe once the relicensing is resolved, this might be more possible. It is the *image* itself where the licensing needs to be cleanest, given the VM itself is very small. That's the problem IMHO with the current JVM implementations I've seen (like the one based on Dan Ingall's work) -- they take the image for granted when that is what matters. Spoon was a great step in the right direction (building the system up rather than stripping it down), but has received not enough support. In the meantime, I mostly use Jython on the JVM and pine for the days of Smalltalk when debugging was easier and classes and their methods were more consistently named... But I would love to use a great Smalltalk on the JVM that had Squeak's following. Suddenly a lot of the issues I mention above would go away and others -- it would be deployable as a jar or with webstart or as an applet, it would have a new freely licensed core, it would play well with other code, it would be easy to do part of a system in Smalltalk, it would have access to standard widgets as well as custom ones, it would have robust libraries for 3D graphics and sound and other things it could easily call on all platforms it runs on, and so on. And then gradually, Smalltalk could expand outwards from there... But it's just a dream and I have too little time as it is. Sigh. --Paul Fernhout

2 1

Re: [squeak-dev] Re: what is holding back Smalltalk?
by Casimiro de Almeida Barreto 22 Nov '08

22 Nov '08

Jecel Assumpcao Jr escreveu: > (...) > In fact, we can generalize this and of nearly all objections that were > pointed out there is some Smalltalk to which it doesn't apply. Now it > might be that only a perfect Smalltalk to which none of the objections > apply could have succeeded, but I think what we have here is a case of > > http://www.dreamsongs.org/WorseIsBetter.html > About that I have an interesting anedocte: in 1998 I was working for the "Department of Education of São Paulo State" (SEESP) under UNDP contract. There, people were having hard times trying to implement a system for the management of schools. That system would feed other systems at the "Department" so the person in charge ("Secretary of Education") would have real time data about schools (including student performance, teachers performance, etc). The problem itself is simple and, from the tech point of view, the system should not be complicated. So, where was the trouble? Easy: the "Department" board kept issuing incredible specifications for the system. So, it was not enough that the goals were achieved, but the system should be "up to date with the best in the world" (what the hell did that meant????!!!!). In short: some people didn't want any system controlling their lack of competence and bombed the initiative through rejecting specifications and issuing over and over more complex and unintelligible ones. Years later an auditing consultant observed that the best way of keeping the status quo is always demanding the excellent even when you don't have the satisfactory. > Smalltalk had higher upfront costs than the alternatives, but scaled > much better. When I pointed out Self (Sun's own version of Smalltalk) to > people in the mid 1990s they would reply "but you need a 24MB Sun > machine to run that! Practically all deployed workstations only have 8MB > and Java works just fine there." I would claim that this was only > because Java wasn't doing anything yet (animating a funny little man) > and that by the time it did half of what Self did it would be twice as > large. It turned out that I was actually generous to Java, but when my > prediction came true typical PCs had 256MB each. > Not to mention that Sun not only killed Self but did the same to SpringOS... :( Now they face the reality of selling mostly Intel servers running RedHat Linux... > But to understand what happened to Smalltalk you must look at the > history more than at technical aspects. I don't know a good text I can > link to, but Eliot spent some time on this in his AoSTA talk - > > http://video.google.com/videoplay?docid=-8988857822906068209 > > -- Jecel > > > > Thnx Jecel for both the reading and the video !!!

2 1

Functional keys and squeak
by Igor Stasenko 21 Nov '08

21 Nov '08

On my win desktop, a functional keys (F1 - F12) generating a key codes 'p' F2 'r' 's' 't' ... 'x' 'y' 'z' '{' which i can see when turning events with: HandMorph showEvents: true all of them seem ignored by image somewhere in EventSensor, except F2 which pops up the VM Preferences menu (but this completely handled by windows VM). I wonder is there's any way to use/handle these keys in squeak in platform transparent way? Since squeak originally came from macs, image expects key codes in 'mac' format. But i have no idea how things working on macs. In old ages not all keyboards has functional keys , some of them has 5 to 10 functional keys. But now, i think it is standard to all keyboards to come with at least 10 functional keys. And macs is not exception http://cache.gizmodo.com/assets/resources/2007/07/imac-slim-keyboard-1.jpg :) So, my question is, is squeak images aware of existance of functional keys? And second, if yes, then what correct key codes VM should generate to make image feel happy ? -- Best regards, Igor Stasenko AKA sig.

7 8

Re: [Vm-dev] Re: [squeak-dev] Building (Linux) VM - with segfaults. that point to audio
by Brad Fuller 21 Nov '08

21 Nov '08

On Thu, Nov 20, 2008 at 3:17 PM, Brad Fuller <bradallenfuller(a)gmail.com> wrote: > On Wed, Nov 19, 2008 at 4:19 AM, David T. Lewis <lewis(a)mail.msen.com> wrote: >> You can get a VMMaker with SlangBrowser support from SqueakSource. >> VMMaker-dtl.107 would be the most recent in that branch. > > Where can I find VMMaker 107? I only see 106 on SqueakSource Also, how does one use the SlangBrowser? I don't see it anywhere. I also don't think that the vm-sound-ALSA C code was generated from Slang. I can't seem to locate it, so I assume that it was generated outside of Squeak. Can anyone (Ian?) confirm this? -- Brad Fuller

2 1

Re: [Pharo-project] Event history question
by John M McIntosh 20 Nov '08

20 Nov '08

Ok, tthe TheInterruptSemaphore is signalled in checkForInterrupts() via usage of setInterruptPending(). As far as I know the only place that it is used is by the VM host platform keyboard handling logic only *IF* you are using an image that predates EventSensor (Aug 2000) Now since most people use an image that has this class what happens is (a) The process running EventSensor>>processEvent: looks at the incoming VM generated keyboard event and if it decides that the keys pressed meet it's criteria of what an interrupt is then it signals in the EventSensor interruptSemaphore That then wakes up the interrupt watcher process InputSensor>>userInterruptWatcher running at Processor lowIOPriority. This means of course the process that is running EventSensor>>processEvent: has to be able to run. You could simplify things here and fork off the userInterruptWatcher logic in EventSensor>>processEvent: and as I think Michael noticed rip out the InterruptWatcherProcess and InterruptSemaphore On 20-Nov-08, at 7:18 AM, Igor Stasenko wrote: > 2008/11/20 Michael Rueger <m.rueger(a)acm.org>: >> Igor Stasenko wrote: >> >>> If i remember correctly, an interrupt semaphore is used to awake a >>> process which watching for interrupts. >>> And indeed, when key combination matching an interrupt key code, >>> it calls setInterruptPending(), which is then eventually leads to >>> signaling a semaphore which registered as interrupt semaphore. >>> You can't handle it on image side, because you may not have chance >>> to >>> get to it (if there's another process running on same or higher >>> priority than event ticker process). >>> While in VM, regardless what image does, it periodically checks for >>> interrupts, and during handling OS events, it checks if an interrupt >>> key pressed, and if so, then signals the semaphore. >>> At least, this is how it looks on Win32. >> >> The question really was if it is in the VM but rather if it (still) >> should >> be in the VM. >> After some discussions with John I'm pretty sure we can remove the >> interrupt >> semaphore code from the VM. For now that would mean that the image >> code >> still referring to it should/can be removed. >> > > In this case, i'd like to read John's reasoning, why its safe to > remove it from VM. >> From my perspective , it should stay, because you can't imitate same > behavior on language side safely. > >> Michael >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

3 6

Falcon
by Benoit St-Jean 20 Nov '08

20 Nov '08

Anyone knows what is happening with Falcon? The Falcon team seems strangely silent... ----------------- Benoit St-Jean Yahoo! Messenger: bstjean Blog: lamneth.wordpress.com A standpoint is an intellectual horizon of radius zero. (Albert Einstein)

2 2

[squeak-dev] [BUG]UndefinedObject(Object)>>doesNotUnderstand: #emphasis:
by Greg A. Woods 19 Nov '08

19 Nov '08

I'm working with an image which has most of the developer packages loaded from the Package Universe, including Wisker, but no other local changes except the beginngings of a few new classes for a new project, and now when I open a Selector Browser (drag Method Finder from the Tools flap) and, type a selector in the top left pane and press return, then try to choose an item in the top right pane I get the following crash, which seems to be the result of a fairly straight forward programming bug within Wisker itself. The problem, as far as I can see, is that the initWithContents:prior:forList:indentLevel: method immediately does "self initWithContents: anObject asString font: nil emphasis: nil." but the initWithContents:font:emphasis: method is not expecting its font: parameter to be nil. At this point I'm lost. I don't know anything about Wisker's internals and I can't quite believe that a released version is so broken in this way. >From the debugger window cmd-v on the initWithContents:prior:forList:indentLevel: method shows only one version, "2002-11-06 12:55:00 dew WhiskerListItemMorph {initialization}", but there's no change set, perhaps because I was forced to do "Smalltalk condenseChanges" while loading the many packages. One more thing to check -- the version of the method that's assuming its font: parameter won't be null (WhiskerListItemMorph(IndentingListItemMorph)>>initWithContents:font:emp hasis:). Ah ha! It is much newer: "2008-09-15 16:35:00 dr IndentingListItemMorph {*ob-enhancements}". That's probably the change which causes this bug, but I'm not sure where it Damn that condeseChanges! ACK! An then if I accidentally close the debug window, poof, away go the details from this message too! Argh! OK, now we start over, cut&paste from the old message window, and be careful to send this message before closing any other windows. 19 November 2008 1:59:58 pm VM: Mac OS - a SmalltalkImage Image: Squeak3.10.2 [latest update: #7179] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir /Users/woods/Squeak/Squeak3.10.2-7179-basic Trusted Dir /Users/woods/Squeak/Squeak3.10.2-7179-basic Untrusted Dir /Users/woods/Library/Preferences/Squeak/Internet/My Squeak UndefinedObject(Object)>>doesNotUnderstand: #emphasis: Receiver: nil Arguments and temporary variables: aMessage: emphasis: 0 Receiver's instance variables: nil WhiskerListItemMorph(IndentingListItemMorph)>>initWithContents:font:emph asis: Receiver: a WhiskerListItemMorph(2143)nil Arguments and temporary variables: aString: 'Object' aFont: nil emphasisCode: nil Receiver's instance variables: bounds: nil owner: nil submorphs: nil fullBounds: nil color: nil extension: nil font: nil emphasis: nil contents: nil hasFocus: nil indentLevel: nil isExpanded: nil complexContents: a ClassInHierarchyWrapper(2136) on Object firstChild: nil container: a MultiSelectHierarchicalListMorph(2378) nextSibling: nil icon: nil WhiskerListItemMorph>>initWithContents:prior:forList:indentLevel: Receiver: a WhiskerListItemMorph(2143)nil Arguments and temporary variables: anObject: a ClassInHierarchyWrapper(2136) on Object priorMorph: nil hostList: a MultiSelectHierarchicalListMorph(2378) newLevel: 0 Receiver's instance variables: bounds: nil owner: nil submorphs: nil fullBounds: nil color: nil extension: nil font: nil emphasis: nil contents: nil hasFocus: nil indentLevel: nil isExpanded: nil complexContents: a ClassInHierarchyWrapper(2136) on Object firstChild: nil container: a MultiSelectHierarchicalListMorph(2378) nextSibling: nil icon: nil [] in MultiSelectHierarchicalListMorph(SimpleHierarchicalListMorph)>>addMorphs To:from:allowSorting:withExpandedItems:atLevel: {[:item | priorMorph := self indentingItemClass basicNew initWithContent...]} Arguments and temporary variables: morphList: an OrderedCollection() aCollection: an Array(a ClassInHierarchyWrapper(2136) on Object) sortBoolean: false expandedItems: #() newIndent: 0 priorMorph: nil newCollection: an Array(a ClassInHierarchyWrapper(2136) on Object) firstAddition: nil a: nil b: nil item: a ClassInHierarchyWrapper(2136) on Object --- The full stack --- UndefinedObject(Object)>>doesNotUnderstand: #emphasis: WhiskerListItemMorph(IndentingListItemMorph)>>initWithContents:font:emph asis: WhiskerListItemMorph>>initWithContents:prior:forList:indentLevel: [] in MultiSelectHierarchicalListMorph(SimpleHierarchicalListMorph)>>addMorphs To:from:allowSorting:withExpandedItems:atLevel: {[:item | priorMorph := self indentingItemClass basicNew initWithContent...]} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Array(SequenceableCollection)>>do: MultiSelectHierarchicalListMorph(SimpleHierarchicalListMorph)>>addMorphs To:from:allowSorting:withExpandedItems:atLevel: MultiSelectHierarchicalListMorph(SimpleHierarchicalListMorph)>>list: MultiSelectHierarchicalListMorph>>on:list:selected:changeSelected:menu:k eystroke: MultiSelectHierarchicalListMorph class(SimpleHierarchicalListMorph class)>>on:list:selected:changeSelected:menu: WhiskerWindow>>addClassHierarchyPane WhiskerWindow>>initializeFromModel: WhiskerBrowser>>openAsMorphEditing: WhiskerBrowser class>>open WhiskerBrowser class>>openExistingBrowserOnClass:selector: Browser class>>fullOnClass:selector: SelectorBrowser>>classListIndex: PluggableListMorph>>changeModelSelection: PluggableListMorph>>mouseUp: PluggableListMorph(Morph)>>handleMouseUp: MouseButtonEvent>>sentTo: PluggableListMorph(Morph)>>handleEvent: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>dispatchEvent:with: PluggableListMorph(Morph)>>processEvent:using: PluggableListMorph(Morph)>>processEvent: PluggableListMorph>>handleFocusEvent: [] in HandMorph>>sendFocusEvent:to:clear: {[ActiveHand := self. ActiveEvent := anEvent. e := anEvent transformedB...]} [] in PasteUpMorph>>becomeActiveDuring: {[aBlock value]} BlockContext>>on:do: PasteUpMorph>>becomeActiveDuring: HandMorph>>sendFocusEvent:to:clear: HandMorph>>sendEvent:focus:clear: HandMorph>>sendMouseEvent: HandMorph>>handleEvent: ...etc...

5 4

leadership team meeting notes for 2008-11-19
by Craig Latta 19 Nov '08

19 Nov '08

Hi-- - Full attendance: Bert, Craig, Edgar, Giovanni, Igor, Randal, and Yoshiki. - Yoshiki contacted Matthew Fulmer and Keith Hodges about Squeak 4 (see [1] for a recap of the next planned releases as discussed at the last meeting). No activity yet. - Craig said he's got Spoon's remote class browsers working with Naiad (the module system, see the design at [2]). He now has a headless minimal memory which can use a headful history memory (instead of changes/sources files, with the history features mentioned in the Naiad design), browsable from a GUI memory. He's now creating a headless history memory, to go with the minimal memory as the next release of Spoon, 5 alpha 1 (roughly, "not the whole Naiad design, but enough so that multiple people can work on it"). Estimated release date is solstice (2008-12-21). In the meantime, he would very much like feedback on the Naiad design. - Randal says there's been no progress mentioned by the web team, since the last meeting, in setting up a "captcha" system for community communication with the leadership team via web mail. He says he'll take the lead on implementing it. In the meantime, please send agenda item suggestions to Craig. - Bert says Marcus would like to pass responsibility for the Squeak project servers' bills from Squeak e.V. to the nascent Squeak project organization. While we will eventually pay Squeak's bills from our Software Freedom Conservancy account (after we've joined, after we have the license-clean release 4), Craig said he'd pay the server bills in the meantime from money we set aside when we were going to incorporate independently (USD 2000 in a PayPal account of Craig's). Giovanni said he also holds Squeak project funds from the Google Summer of Code program. Craig suggested that anyone holding Squeak project money keep it until we have an SFC account, unless they don't want to, in which case he volunteered to aggregate it in the aforementioned PayPal account. thanks again, -C [1] From the 2008-10-15 meeting: - Yoshiki says he's created a license-clean EToys 4.0 image based on Squeak 3.8. We decided to use a similar process to create Squeak 4 from Squeak 3.11 (and whatever other license-clean changes the 3.11 release team, currently Matthew Fulmer and Keith Hodges, wants to include). Yoshiki will consult with them about ensuring license-cleanliness. Randal will coordinate with the release team and report on their progress. - We decided in principle to have two board-appointed release teams working at any given moment: one producing the next release (I'll call it "one-ahead"), and one producing the release after that ("two-ahead"). We decided that Spoon is the two-ahead release now, or Squeak 5. Craig is leading the two-ahead team, and will add people to it when Naiad can support their work. [2] http://netjam.org/spoon/naiad

1 0

Sparkle automatic update framework for Squeak OS-X
by John M McIntosh 19 Nov '08

19 Nov '08

With some funding help from Impara I built a plugin to enable the use of Sparkle to receive update information about the macintosh carbon VM. This lets you auto-update your Squeak based application by pushing update notifications via rss to users. Numerous one-click squeak based apps come to mind... Based on feedback and experience reports at some point I will consider if this should be part of the mainstream Squeak Carbon VM. http://www.squeaksource.com/Sparkle.html Which contains the plugin source, the class based interface, and of course SUnits. A 1.0.0 plugin can be found via the usual places in the experimental directory as SparklePlugin.1.0.0.bundle.zip http://www.smalltalkconsulting.com/squeak.html -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

2 2

Building (Linux) VM - with segfaults. that point to audio
by Brad Fuller 19 Nov '08

19 Nov '08

Objective: I'm trying to build the VM out of the box, nothing fancy. I want to use ALSA. Problem: I'm getting segfaults when playing any audio object (from the Objects>Multimedia panel) I svn'd fresh source from the trunk, and followed the directions in README.SVN [1]. I then moved to unix subdir and made. Everything went fine, no errors and installed fine. Squeak seems to run fine.e.g. I exercised the network retrieving the Universe packages. However, when I start up an image and pull out any of the audio objects, a segfault happens immediately: Segmentation fault 17753728 [] in >playLoop 17753820 [] in Semaphore>critical: 17753544 BlockContext>ensure: 17753360 Semaphore>critical: 17720844 >playLoop 17720660 [] in >startPlayerProcessBufferSize:rate:stereo:sound: 17720752 [] in BlockContext>newProcess Aborted I get the same segfault using a command option: $ squeak -vm sound=ALSA Squeak3.10.2-7179-basic.image If I specify "none": $ squeak -vm sound=none Squeak3.10.2-7179-basic.image then no segfault, and of course, no sounds. the plugin does exist in the squeak directory: $ lsa /usr/local/lib/squeak/3.10-4 total 22540 4 drwxr-xr-x 2 root root 4096 2008-11-14 15:35 . 4 drwxr-xr-x 5 1000 1000 4096 2008-11-14 15:32 .. 28 -rwxr-xr-x 1 root root 26820 2008-11-14 15:32 AioPlugin 172 -rwxr-xr-x 1 root root 170451 2008-11-14 15:32 B3DAcceleratorPlugin 32 -rwxr-xr-x 1 root root 29332 2008-11-14 15:32 ClipboardExtendedPlugin 76 -rwxr-xr-x 1 root root 71250 2008-11-14 15:32 DBusPlugin 24 -rwxr-xr-x 1 root root 20934 2008-11-14 15:32 FileCopyPlugin 184 -rwxr-xr-x 1 root root 182395 2008-11-14 15:32 GStreamerPlugin 32 -rwxr-xr-x 1 root root 32161 2008-11-14 15:32 ImmX11Plugin 88 -rwxr-xr-x 1 root root 85971 2008-11-14 15:32 KedamaPlugin 140 -rwxr-xr-x 1 root root 138507 2008-11-14 15:32 KedamaPlugin2 44 -rwxr-xr-x 1 root root 44065 2008-11-14 15:32 MIDIPlugin 792 -rwxr-xr-x 1 root root 803221 2008-11-14 15:32 Mpeg3Plugin 24 -rwxr-xr-x 1 root root 23088 2008-11-14 15:32 npsqueak.so 36 -rwxr-xr-x 1 root root 36765 2008-11-14 15:32 PseudoTTYPlugin 144 -rwxr-xr-x 1 root root 142582 2008-11-14 15:32 RomePlugin 2472 -rwxr-xr-x 1 root root 2525072 2008-11-14 15:32 squeak 208 -rwxr-xr-x 1 root root 205337 2008-11-14 15:32 Squeak3D 17200 -rw-r--r-- 1 root root 17584742 2008-11-14 15:35 SqueakV39.sources 116 -rwxr-xr-x 1 root root 113755 2008-11-14 15:32 UnixOSProcessPlugin 20 -rwxr-xr-x 1 root root 17974 2008-11-14 15:32 UUIDPlugin 100 -rwxr-xr-x 1 root root 96184 2008-11-14 15:32 VideoForLinuxPlugin 112 -rwxr-xr-x 1 root root 110434 2008-11-14 15:32 vm-display-fbdev 28 -rwxr-xr-x 1 root root 26121 2008-11-14 15:32 vm-display-null 272 -rwxr-xr-x 1 root root 271778 2008-11-14 15:32 vm-display-X11 56 -rwxr-xr-x 1 root root 49985 2008-11-14 15:32 vm-sound-ALSA 20 -rwxr-xr-x 1 root root 16870 2008-11-14 15:32 vm-sound-null 84 -rwxr-xr-x 1 root root 79461 2008-11-14 15:32 vm-sound-OSS 28 -rwxr-xr-x 1 root root 25109 2008-11-14 15:32 XDisplayControlPlugin I thought maybe it was because SoundPlugin was not there, but it's in: $ ls src/vm/intplugins/SoundPlugin SoundPlugin.c and: $ cat src/plugins.int # Automatically generated makefile include for internal plugins INTERNAL_PLUGINS = ADPCMCodecPlugin AsynchFilePlugin BMPReadWriterPlugin B2DPlugin BitBltPlugin CroquetPlugin DSAPrims ZipPlugin DropPlugin FFTPlugin FilePlugin FloatArrayPlugin FloatMathPlugin GeniePlugin JPEGReadWriter2Plugin JPEGReaderPlugin JoystickTabletPlugin Klatt LargeIntegers LocalePlugin Matrix2x3Plugin MiscPrimitivePlugin RePlugin SecurityPlugin SerialPlugin SocketPlugin SoundCodecPrims SoundGenerationPlugin SoundPlugin StarSqueakPlugin SurfacePlugin I assume it got built and is located internally in the vm proper. Any ideas? I have a feeling I just missed something completely easy in the setup. Or, could this be because I'm running 64bit? Since everything else is working? [1] the first instruction in README.SVN is incorrect. It should be: $ svn co http://squeakvm.org/svn/squeak/trunk squeak - .i.e. the path is a bit wrong. Perhaps I should write up a bug? (should these types of messages go to the squeak-vm list? I long-ago unsubscribed to that since it had little traffic) -- Brad Fuller

5 11

← Newer
1
...
4
5
6
7
8
9
10
...
14
Older →

Jump to page: