Squeak-dev April 2008

squeak-dev@lists.squeakfoundation.org

146 participants
187 discussions

FFI and FreeTypePlus problem?
by Torsten Bergmann 23 Oct '08

23 Oct '08

I already created a bug report for this, Andreas may be able to tell you more: http://bugs.squeak.org/view.php?id=6980 As a workaround you can can use FFI-Kernel-ar6.mcz instead of FFI-Kernel-ar-8.mcz. Bye Torsten -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/?mc=sv_ext_mf@gmx

10 13

3.10 is done
by Ralph Johnson 08 Sep '08

08 Sep '08

3.10 is done. It has been stable for a long time, and Edgar was just waiting for me to write a welcome screen. I've done that, so he can make a final image. The thing that we did that I like the best is making Package Universe prominent. While not perfect, it has worked well. The thing that disappoints me the most is that there are still a few tests that are not green. It looks like a committee has formed to work on the next release, and I wish them the best. I want to thank Edgar for all the hard work he did on 3.10. He did almost all the work, and did an excellent job. -Ralph Johnson

4 4

3.10 image
by itsme213 15 Jul '08

15 Jul '08

I the damien-3.10-web image size is quite large (129M) compared to a comparably (not identical) loaded 3.9 Ramon's image (42M). Is that expected, or is it because as a beta it has not been trimmed etc.? Thanks - Sophie

8 13

Process bug introduced in 3.10
by bryce＠kampjes.demon.co.uk 10 Jun '08

10 Jun '08

Run the following in a 3.10 image: 100 timesRepeat: [processes := (1 to: 10) collect: [:each| [[(MessageTally spyOn: [(Delay forMilliseconds: 500) wait]) ] repeat] fork ]. (Delay forSeconds: 1) wait. processes do: [:each| each terminate].] It locks up the image, debuggers will start popping up at some stage. This works on 3.9. I've run the code above in a fresh 3.10 image and reproduced the problem. I'll try to find time to investigate further. It's probably the final showstopper to me upgrading to 3.10. The code above is reworked from on of Exupery's SUnits which locks up the image intermittently. Bryce

7 20

Funding (was: What Constitutes a Complete and Final Release?)
by Stephen Pair 29 May '08

29 May '08

On Sun, Apr 6, 2008 at 4:11 AM, Hilaire Fernandes <hilaire(a)ofset.org> wrote: > tim Rowledge a écrit : > > > > On 4-Apr-08, at 8:49 PM, Klaus D. Witzel wrote: > > > > > > It seems to me that the board has a problem here, with both 3.9 and > > > 3.10 :( > > > > Well, no. It's not the board that has any sort of problem; the board is > > a bunch of people that meet every couple of weeks to discuss an agenda that > > is primarily organisation based (ie getting to a state where we can join the > > SFLC foudation thingy). The board is not a team that can be asked or > > expected to solve all *our* problems. *You lot* get to do the actual work. > > Until and unless you provide funds to pay a team.... > > I found this statement pretty irresponsible :( > And reading this statement one may think what is the Sqf good for (beside > the never ending registration in SFLC...) and outsiders may even fell that > Squeak community is not a good place to go (no clear roadmap). > > Hilaire > I think you're overstating things a bit. The point is that unless you are willing to jump in and help, or provide other means of help (i.e. funding), one shouldn't complain about the state of affairs. The people doing this work are doing it as a free service to others and for that, we should be grateful. At the same time, maybe we should be thinking about alternative means of funding. The way I see it, funding is a means of enabling more people to spend more of their time working on squeak (presumably something they enjoy). I think the bounty model doesn't work all that well, and I think being dependent on benevolent commercial ventures to develop and donate substantial code is also sub-optimal. With commercial ventures, their attention is always going to be focused on their product. Innovating and developing the core squeak system will consequently only get their attention when it is necessary to further the commercial product. And then, they will only develop it as far as it needs to go to serve their interests and no further. I find it a real shame that the economy around core platforms and tools seems to have evaporated with the open source movement. It seems that there is precious little funding available to those that want to develop new languages, new operating systems, new development tools and the like. There is a modest amount of innovation going on in spite of this reality, but progress is frustratingly slow. Here's an idea for a funding model. Instead of always releasing new stuff immediately under MIT, how about releasing some stuff under a time limited proprietary license with a specific date at which it reverts to MIT (this would be baked into the original license such that the "freedom date" is irrevocable). The date could be 3 months, 6 months or even a year or two into the future. In the interim, anyone wishing to use that software would need to pay some fee to the author(s). This is the essentially the same idea that is behind copyright laws, but on a dramatically shorter timeframe that is more appropriate for software (the life of copy rights in the US extends for life+70 years I believe, which certainly doesn't work for software). If we could make something like this work successfully (and I'd say that success means that more people are able to spend more of their time working on squeak (instead of other endeavors to pay the bills)), I think people would quickly take notice. Imagine if this came to be an expectation of all software licenses. Imagine if all commercial software were sold like this. To me, this is more in line with basic economics. The cost to produce software is substantial, but the marginal cost to distribute software is effectively zero. So, over time the price of software (or any intellectual property) must approach zero. It's unnatural for software to be locked up under proprietary licenses for what is effectively an indefinite period of time. It's also unnatural in my opinion to rely solely on indirect means of funding (relying on people deriving inherent fun in the work or commercial benevolence or services associated with the free software, etc). Musicians will deal with this by deriving money from live performances or associated merchandising and hence be able to offer recordings for free right from the start. I doubt too many people will pay to watch many of us as we write code, so we have to think of alternative means. Maybe if enough people were willing to pay $10 for a high quality 3.10, it would be enough to entice a few people into spending a larger chunk of their time working on that problem. The compromise we make is that for the first 6 months (or whatever the author decides), it's not free software...you must pay $10. The small size of the squeak community won't make people rich in so doing, but over time, a better squeak means a larger community and a larger community means that more people will have an opportunity to participate as a supplier in such an economy. - Stephen

36 78

Re: [squeak-dev] Renaming "Squeak"
by Bill Schwab 20 May '08

20 May '08

Alan, Agreed. The name is not nearly so important as the fundamentals of a solid Smalltalk system. Focusing on the latter serves everyone: the children for whom all this was started; the adults who will set them up with something they can use; and other developers wanting to work in Smalltalk. If we do create a ViewPoints Smalltalk, or whatever it gets named, then we should do it right. Fix the gratuitous incompatibilities with other dialects, clean up the look and (far more important) the feel of the GUI, and arrange for the toys and the experiments to be built on top of vs. into the core language and environment. However, that is good advice whether the names changes or not. Bill ==================================== Alan Lovejoy <squeak-dev.sourcery@...> wrote: Squeak is not the most professional-sounding name that could have been chosen. One very important purpose of a name is marketing, and the name "Squeak" doesn't do that very well in a few rather important markets. Of course, if you're marketing to children (and those who educate them,) then Squeak is not at all a bad name. But that's all water under the bridge at this point. Changing the name only, in the absence of any other substantive changes, would at best be ignored as a shameless (and not well-motivated) marketing ploy. At worst, it would be seen as an act of desperation. Change Squeak so that it deserves a new name. Then the new name will be perceived as having been earned, and so will serve as an effective marketing tool to advertise the new, improved "Open Source Smalltalk." --Alan Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029

11 13

Renaming "Squeak"
by Michael van der Gulik 14 May '08

14 May '08

On Sun, Mar 2, 2008 at 3:22 AM, K. K. Subramaniam <subbukk(a)gmail.com> wrote: > On Saturday 01 March 2008 5:34:52 am Craig Latta wrote: > > Let's turn our attention to Squeak 4 now. Let's create a kernel > > with nothing extraneous in it, and a module system we can use to keep > > the organization clear. I think the result will be much easier to learn, > > and far more pleasant to use. Getting there will be difficult, but it > > will be worth it. > If we are going to strip Squeak down and rebuild it, should we consider > picking a new name for the project? The name Squeak has been around for > more > than a decade and has strong associations (good or bad) with certain > feature > sets and intended uses. A legally clear open source base is a good time to > invent a new platform that can consolidate the lessons learnt from the > Squeak > project and build a new system for the next generation - just as Squeak > emerged from Smalltalk-80. > > Spoon? Hydra? Athena? Phoenix? Roar :-)? > I've thought about this too. "Squeak" is a name that's hard to take seriously, and I for one would be less inclined to advertise that any product I make is based on "Squeak". However, there's a large investment in the name - URLs, source code, public awareness, etc. The name is unlikely to change. In my opinion, Squeak should be a minimal image that is used as a base or a template to create other projects that have different names. Squeak could be thought of as an internal development name that only us coders need to be aware of. What is advertised to the outside world are the names of the other projects, with a small note on the bottom of the packaging saying "Made with Squeak". Mind you, Linux is taken seriously, and they use a fat penguin as a mascot. Gulik. -- http://people.squeakfoundation.org/person/mikevdg http://gulik.pbwiki.com/

22 37

talk on Newspeak online
by Michael Haupt 12 May '08

12 May '08

Hi, Gilad Bracha's talk on the Newspeak language (which he gave at the Hasso-Plattner-Institut in Potsdam, Germany on March 11) is now online at http://www.tele-task.de/page50_lecture3490.html. Best, Michael

21 67

Monticello error loading file : UndefinedObject(Object)>>doesNotUnderstand: #select:thenCollect:
by itsme213 06 May '08

06 May '08

I get this error when loading a mcz into Damien's 3.9.1 web image. The MCClassDefinition happens to be a trait, not sure if that has anything to do with it. Any suggestion? Thanks - Sophie ====================================== Subject: [BUG]UndefinedObject(Object)>>doesNotUnderstand: #select:thenCollect: 28 April 2008 4:18:06 pm VM: Win32 - a SmalltalkImage Image: Squeak3.9.1 [latest update: #7075] UndefinedObject(Object)>>doesNotUnderstand: #select:thenCollect: Receiver: nil Arguments and temporary variables: aMessage: select: [] in MCClassDefinition>>selectVariables: {[:v | v perform: a...etc... Receiver's instance variables: nil MCClassDefinition>>selectVariables: Receiver: a MCClassDefinition(TMyTrait) Arguments and temporary variables: aSelector: #isPoolImport v: nil Receiver's instance variables: name: #TMyTrait superclassName: nil variables: nil category: 'MyCat' type: nil comment: '' commentStamp: '' traitComposition: nil classTraitComposition: nil MCClassDefinition>>poolDictionaries Receiver: a MCClassDefinition(TMyTrait) Arguments and temporary variables: Receiver's instance variables: name: #TMyTrait superclassName: nil variables: nil category: 'MyCat' type: nil comment: '' commentStamp: '' traitComposition: nil classTraitComposition: nil MCClassDefinition>>requirements Receiver: a MCClassDefinition(TMyTrait) Arguments and temporary variables: Receiver's instance variables: name: #TMyTrait superclassName: nil variables: nil category: 'MyCat' type: nil comment: '' commentStamp: '' traitComposition: nil classTraitComposition: nil --- The full stack --- UndefinedObject(Object)>>doesNotUnderstand: #select:thenCollect: MCClassDefinition>>selectVariables: MCClassDefinition>>poolDictionaries MCClassDefinition>>requirements - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - MCDependencySorter>>unresolvedRequirementsFor: MCDependencySorter>>add: [] in MCDependencySorter>>addAll: {[:ea | self add: ea]} Array(SequenceableCollection)>>do: MCDependencySorter>>addAll: MCDependencySorter class>>items: MCPackageLoader>>sorterForItems: MCPackageLoader>>analyze MCPackageLoader>>loadWithNameLike: MCVersionLoader>>load MCVersionLoader class>>loadVersion: MCVersion>>load [] in MCFileRepositoryInspector(MCVersionInspector)>>load {[self version load]} BlockContext>>ensure: CursorWithMask(Cursor)>>showWhile: MCFileRepositoryInspector(MCVersionInspector)>>load MCFileRepositoryInspector>>load PluggableButtonMorphPlus(PluggableButtonMorph)>>performAction PluggableButtonMorphPlus>>performAction [] in PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp: {[:m | (m containsPoint: evt cursorPoint) ifTrue: [m performAction]]} Array(SequenceableCollection)>>do: PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp: PluggableButtonMorphPlus>>mouseUp: PluggableButtonMorphPlus(Morph)>>handleMouseUp: MouseButtonEvent>>sentTo: PluggableButtonMorphPlus(Morph)>>handleEvent: PluggableButtonMorphPlus(Morph)>>handleFocusEvent: [] in HandMorph>>sendFocusEvent:to:clear: {[ActiveHand := self. ActiveEvent := anEvent. result := focusHolder han...]} [] in PasteUpMorph>>becomeActiveDuring: {[aBlock value]} BlockContext>>on:do: PasteUpMorph>>becomeActiveDuring: HandMorph>>sendFocusEvent:to:clear: HandMorph>>sendEvent:focus:clear: HandMorph>>sendMouseEvent: HandMorph>>handleEvent: HandMorph>>processEvents [] in WorldState>>doOneCycleNowFor: {[:h | ActiveHand := h. h processEvents. capturingGesture := capturingGest...]} Array(SequenceableCollection)>>do: WorldState>>handsDo: WorldState>>doOneCycleNowFor: WorldState>>doOneCycleFor: PasteUpMorph>>doOneCycle [] in Project class>>spawnNewProcess {[[World doOneCycle. Processor yield. false] whileFalse. nil]} [] in BlockContext>>newProcess {[self value. Processor terminateActive]}

2 1

[ANN] ESUG 2008 Call for Contribution
by stephane ducasse 04 May '08

04 May '08

Hi all we are really happy to announce that ... --------------------------------------------------------------------- 16th International Smalltalk Joint Conference - Call for Contributions August 25-29, 2008 - Amsterdam, the Netherlands http://www.esug.org/conferences/2008/ ---------------------------------------------------------------------- For the past 16 years, the European Smalltalk User Group (ESUG) has organised the International Smalltalk Conference, a lively forum on cutting edge software technologies that attract people from both academia and industry for a whole week. The attendees are both engineers using Smalltalk in business and students and teachers using Smalltalk both for research and didactic purposes. As every year, this year's edition of the largest European Smalltalk event will include the regular Smalltalk developers conference with renowned invited speakers, a Smalltalk camp that proves fruitful for interactions and discussions. Besides, this year will be held the 4th edition of the Innovation Technology Awards where prizes will be awarded to authors of best pieces of Smalltalk-related projects. You can support the ESUG conference in many different ways: * Sponsor the conference. New sponsoring packages are described at http://www.esug.org/supportesug/becomeasponsor/ * Submit a talk, a software or a paper to one of the events. See below. * Attend the conference. We'd like to beat the previous record of attendance (116 people at Köthen, Germany in 2004)! * Students can get free registration and hosting if they enroll into the the Student Volunteers program. See below. The conference features the following events: * Camp Smalltalk - There will be a Smalltalk camp the 23-24th of august * Developers Forum * Technology Forum Developers Forum : International Smalltalk Developers Conference ------------------ This year we are looking for YOUR experience on using Smalltalk. The list of topics includes, but is not limited to the following: * XP practices * Development tools * Experience reports * Model driven development * Web development * Team management * Meta-Modeling * Security * New libraries & frameworks * Educational material * Embedded systems and robotics * SOA and Web services * Interaction with other programming languages Submissions due on 1st June 2008 Notification of acceptance on 15 of June 2008 More information at http://www.esug.org/conferences/2008 How to sumbit? ------------------ Pay attention: the places are limited so do not wait till the last minute to apply. Prospective presenters should submit a request to esug-info(a)esug.org following the template below. Please use this template since the email will be automatically processed! Subject: [ESUG 2008 Developers] + your name First Name: Last Name: Email where you can always be reached: Title: Abstract: Bio: Any presentation not respecting this form will be discarded automatically Technology Forum ------------------ We are proud to announce the 4th Innovation Technology Awards. The top 3 teams with the most innovative software will receive, respectively, 500 Euros, 300 Euros and 200 Euros during an awards ceremony at the conference. Developers of any Smalltalk-based software are welcome to compete. More information at http://www.esug.org/conferences/2008 Student Volunteer Program ------------------ If you are a student wanting to attend ESUG, have you considered being a student volunteer? Student volunteers help keep the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. More information at http://www.esug.org/conferences/2008 http://www.esug.org/conferences/16thinternationalsmalltalkjointconference20… We hope to see you there and have fun together.

1 1

Jump to page: