- Pharo-dev - lists.pharo.org

[Pharo-project] Repaint does not work
by StÃ©phane Ducasse Nov. 9, 2008

Nov. 9, 2008

Hi adrian do you remember if you did something with the SketchEditorMorph when you optimise memory, because now I cannot repaint a form, I get a plainCursor error since the palette is nil. To reproduce bring halos on the pharo logo click on repaint you get one DNU because Prototype classVariable is nil and not a PaintBoxMorph then if you bring again the halos and move the mouse over the area we get a plainCursor DNU. I was not working on this area so I imagine that it may be your cleans. was working 10107 but not in 10133 Sytef

2 5

[Pharo-project] Fwd: FOSDEM 2009, call for participation
by Damien Pollet Nov. 9, 2008

Nov. 9, 2008

---------- Forwarded message ---------- From: Mattias 'Tias' Guns <mguns(a)fosdem.org> Date: Sun, Nov 9, 2008 at 1:52 PM Subject: FOSDEM 2009, call for participation To: Fosdem Lightning Talks <lightningtalks(a)fosdem.org> Hello Lightningtalk speakers of last year, I hope you enjoyed participating in FOSDEM 2008 (if not, let me know). We are currently preparing for FOSDEM 2009, and we have sent out a joint call for participation, including devrooms, stands and lightningtalks, see http://fosdem.org/2009/ To maximize project's chances, we do not allow projects that participated in fosdem last year to do a lightningtalk this year. However if you liked participating, may I ask you to help spread the word, and inform other projects and developers about the opportunities at FOSDEM. Below is our call for participation. Thank you for sending it around, Tias FOSDEM Lightning Talks FOSDEM is probably the most developer-oriented Free and Opensource conference, taking place in Brussels, Belgium on Saturday 7 and Sunday 8 February 2009. Apart from having many invited speakers, the conference offers developer rooms, stands and lightning talks to projects from the Free and Opensource community. We hereby welcome proposals from projects to participate in organizing a devroom, manning a stand or holding a lightning talk. As every year, we have only a limited number of rooms, space for stands and lightning talk slots. Since we always receive more requests than we can host, a committee within the FOSDEM organizing team will review all proposals. Selection will be based on possible impact, our experience of previous editions and diversity in the offerings. *** Devrooms We offer large projects a devroom during the conference. A devroom is a room in which projects can organize their own schedule made of presentations, brainstorming and hacking sessions. Our goal is to stimulate developer collaboration and cross-pollination between projects, and as such we strongly favor projects with similar goals and domains to host a devroom together. See http://fosdem.org/2009/call_for_devrooms_and_stands *** Stands We offer stands to projects that want to present themselves to the visitors in a more personal fashion. Stands can be used to share information, demo software, sell merchandizing or give away goodies. See http://fosdem.org/2009/call_for_devrooms_and_stands *** Lightning talks We offer lightning talks to all other projects that want to present themselves. A lightning talk is a short talk in which a project can introduce itself, talk about recent developments, or share exciting new directions. See http://fosdem.org/2009/call_for_lightningtalks FOSDEM 2009 will be the 9th edition of the event, which has been steadily growing every year in importance and in the number of visitors. Our goal is to provide a platform to Free and Opensource projects to meet, discuss, present their current and future developments, both to their own developer and user community as to other projects that are present. Given the large amount of active contributors from many different projects present during the conference, it is an exceptionally well suited occasion to share goals and ideas with people from other communities, which is something we strongly encourage and do our best to support. Of course, the event only lives through the projects that take part in it, and through the many FOSS contributors who attend. We merely do our best to provide the best possible service to the FOSS community at large. *** Key dates: * 2008-11-22: Deadline for devroom & stand requests * 2008-11-30: Devroom & stand acceptance notification * 2008-12-26: Deadline for lightning talk requests * 2008-12-29: Lightning talk acceptance notification * 2009-01-09: Deadline for final devroom & lightning talk schedules * 2009-02-07 to 2009-02-08: FOSDEM 2009 For more information, visit http://fosdem.org/ -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

1 0

[Pharo-project] [ANN] pharo-core #10142
by Marcus Denker Nov. 9, 2008

Nov. 9, 2008

https://gforge.inria.fr/frs/download.php/10926/Pharo0.1Core-10142.zip -> Issue 296: Logo inside Pharo window should be locked ... ChangeLog: ========================================================== update10134 - copyrith removed - MC enh from lukas - Dictionary Collect This is http://bugs.squeak.org/view.php?id=7095 and http://code.google.com/p/pharo/issues/detail?id=292 Fix Dictionary>>collect: to return a Dictionary of mapped values (instead of an OrderedCollection). Also provide tests for #select:, #reject:, and #collect: which should all behave in a similar way ------------------------------------------------------ update10135 - Issue 83: squeakToUtf8 and utf8ToSqueak convenience methods - improved ScriptLoader robustness ------------------------------------------------------ update10136 Issue 305: TODO: garbage collection parameters Issue 312: Typo in PasteUpMorph>>keyboardNavigationHandler Issue 309: Color>hex: should be brought back Issue 306: file stream not closed after drag and drop of CS in postscript: (Preferences preferenceAt: #allowEtoyUserCustomEvents) changeInformee: nil changeSelector: nil. ------------------------------------------------------ update10137 simple etoy cleaning from gary list. ------------------------------------------------------ update10138 HaloMorphEtoyCleaning ------------------------------------------------------ update10139 EtoyUnsentMessageRemoval ------------------------------------------------------ update10140 Object etoy cleaning (treated so far) ? assured ? beViewed ? belongToUniClass ? browseOwnClassSubProtocol ? categoriesForViewer: ? categoriesForVocabulary: aVocabulary limitClass: aLimitClass ? chooseNewNameForReference ? defaultLimitClassForVocabulary: ? eToyStreamedRepresentationNotifying: ? infoFor: anElement inViewer: aViewer Object (to fix later so far) ? presenter ? currentVocabulary ? defaultNameStemForInstances ------------------------------------------------------ update10141 3 timesRepeat: [SystemNavigation default removeUnsentMessagesWithProgressBarInPackageNamed: EToys] ------------------------------------------------------ update10142 Issue 317: lessMethodSendsInFontUsage Issue 301: UIManager enhacements -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

2 1

[Pharo-project] [update] #10142
by Marcus Denker Nov. 9, 2008

Nov. 9, 2008

Issue 317: lessMethodSendsInFontUsage Issue 301: UIManager enhacements -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

1 0

[Pharo-project] [ANN] Part of Etoy removal updates
by StÃ©phane Ducasse Nov. 8, 2008

Nov. 8, 2008

update10137 simple etoy cleaning from gary list. ------------------------------------------------------ update10138 HaloMorphEtoyCleaning ------------------------------------------------------ update10139 EtoyUnsentMessageRemoval ------------------------------------------------------ update10140 Object etoy cleaning (treated so far) assured beViewed belongToUniClass browseOwnClassSubProtocol categoriesForViewer: categoriesForVocabulary: aVocabulary limitClass: aLimitClass chooseNewNameForReference defaultLimitClassForVocabulary: eToyStreamedRepresentationNotifying: infoFor: anElement inViewer: aViewer Object (to fix later so far) presenter currentVocabulary defaultNameStemForInstances

1 0

[Pharo-project] [update] #10136
by Marcus Denker Nov. 8, 2008

Nov. 8, 2008

Issue 305: TODO: garbage collection parameters Issue 312: Typo in PasteUpMorph>>keyboardNavigationHandler Issue 309: Color>hex: should be brought back Issue 306: file stream not closed after drag and drop of CS in postscript: (Preferences preferenceAt: #allowEtoyUserCustomEvents) changeInformee: nil changeSelector: nil. -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

1 0

[Pharo-project] adrian .... help :)
by StÃ©phane Ducasse Nov. 8, 2008

Nov. 8, 2008

adrian could you have a look at the scriptloader because it gets desynchronised (I had to change the number by hand this morning again and I followed exactly the process). May be my image counter was not correct. I think that this counter is brittle. I would just do what we did before taking the lastest updateXXX number + 1 Stef

2 3

[Pharo-project] About Pharo - text to go with version 1.0
by Matthias Berth Nov. 8, 2008

Nov. 8, 2008

Hello, I am thinking that some "getting started" info is a good idea for Pharo 1.0. As a first part, I have tried to compile various statements "about pharo" and what I read on the mailing list into a short text (see below). Does that capture what people doing the work are thinking about the project? Anything I should add? Anything you don't like? Cheers Matthias =About Pharo= The goal of the Pharo Project is to produce a clean and lean open-source Smalltalk for professional software development: * great tools, e.g. OmniBrowser with refactoring support * polished user interface with TrueType fonts and Polymorph widgets * clean and lean image * works out-of-the-box, with clear ways to add functionality Starting from version 1.0, Pharo wants to be stable to make sure that we can produce ideas based on it. An important test for Pharo is that mission critical Seaside (http://www.seaside.st) applications should run on it. Pharo started from Squeak (http://www.squeak.org) [which version, 3.10?] but it is a fork: Do not expect Etoy/Nebraska to work in Pharo. We will try to avoid to reinvent the wheel but will change if changing is better. Pharo wants to take a fresh look at the Smalltalk philosophy and current implementations. Ideally by 2011 we would like to have a small kernel and some cool packages that we can load on top. The current focus is not to produce such a kernel but good packages. Everybody is welcome to contribute. You can find a wiki, bug tracker, and a mailing list via the Pharo home page at http://www.pharoproject.org ==License== [A few words about the code that is already there in Pharo, please] Any code developed and committed to the SqueakSource/Pharo and PharoInbox repository is by default under the MIT License.

3 4

Nov. 8, 2008

Begin forwarded message: > From: Keith Hodges <keith_hodges(a)yahoo.co.uk> > Date: November 8, 2008 2:18:32 AM CEST > To: Alexandre Bergel <Alexandre.Bergel(a)inria.fr> > Cc: stephane ducasse <stephane.ducasse(a)free.fr> > Subject: Re: [Pharo-project] Sunit Extensions breaking the TestRunner > > Alexandre Bergel wrote: >> The situation is getting messy. >> >> Cheers, >> Alexandre > exactly... everyone doing their own thing for their own reasons. Will > you be willing to help restore some coherence to the picture. > > I set a few goals that are fulfilled in my derived implementation. My > improvements are based upon more than 10 years of experience of using > SUnit and things like it. These have been out there for 2 years, so > there is no reason why people cannot build upon this base. > > 1. Ability to define test suites, and have a UI for running test > suites. > I have been using this facility for 8 years in st/x and always miss it > in squeak. I want to be able to define a suite for "My Project". > > 2. Ability to flag which tests are expected to work in which > situation, > which image version and which platform. So that I can run with "all > tests green" even if I happen to have a few windows specific tests, > when > I am running on a mac. > > 3. Ability to use tests to specify behaviour and requirements even > before the tests work. I.e. mark tests as #toDo. > > 4. Ability to run tests in an automated tool, without a UI. > > 5. Ability to sort tests so that they are run fastest first. 95% of > the > tests will run in 10% of the time. > > 6. Ability to determine whether a test used the network or not, and > filter out those tests if necessary. > > 7. Ability to integrate other testing technologies like SSpec. (not > actually done, but conceptually possible now) > > A couple of other improvements are also included, such as the > ability to > define a custom exception handler around all of your tests. > > In my opinion some members of the Pharo team have a big problem with > "Not Invented Here". They don't even look at the existing stuff before > diving in. > > I spent several months integrating the fixes from 3 separate streams > of > Monticello, specifically with the goal of promoting coherence within > all > of the the squeak communities. I did this work for the benefit of all > squeak users, not for the benefit of my health or financial well > being. > In fact it has cost me several thousands of pounds in lost revenue. > > I am actually fairly insulted by the attitude of the Pharo team > towards > this work. Since they take MC and continue to work on it > separately, it > actually renders all of my effort a waste of time. > > perhaps we can rescue sunit before it is too late. > > Keith > >

1 1

[Pharo-project] Strange primitives doing nothing
by Igor Stasenko Nov. 7, 2008

Nov. 7, 2008

I'm exploring the exception support in VM, and found two strange primitives used by BlockClosure, which simply fail and doing nothing. primitiveMarkUnwindMethod "Primitive. Mark the method for exception unwinding. The primitive must fail after marking the context so that the regular code is run." self inline: false. ^self primitiveFail primitiveMarkHandlerMethod "Primitive. Mark the method for exception handling. The primitive must fail after marking the context so that the regular code is run." self inline: false. ^self primitiveFail Any ideas, why they still in use? Can there be something in between, when interpreter enters the method? Or, if nothing, then why they still there? :) -- Best regards, Igor Stasenko AKA sig.

1 0