April 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo sprint at Brussels Friday 15th of April

by Sven Van Caekenberghe

On 04 Apr 2011, at 11:56, Johan Brichau wrote: >> And the timeframe ? > > 9:00 early enough for you? ;-) > > We can be there until 18:00. Super ! Traffic jams won't allow 9h, it will be closer to 10h. Greetings, Sven

April 4, 2011

Re: [Pharo-project] [ANN 1.2] 1.2.1 Full Release Image

by Hannes Hirzel

On 4/4/11, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 03 Apr 2011, at 09:35, Marcus Denker wrote: > >> https://gforge.inria.fr/frs/download.php/28435/Pharo-1.2.1-11.04.03.zip >> >> >> Marcus > > Marcus et al, > > I have to agree with Laurent: you and the rest of Pharo are being way too > modest here. Like most users I have been waiting for 1.2.x to be announced > with a big splash. +1. It was just the download link. I would have expected some 'release notes'. I'm glad to download it and the moose-dev image which builds on it. --Hannes

April 4, 2011

[Pharo-project] Issue 3951 in pharo: Invisible text cursor

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3951 by Yuriy.Sk...(a)gmail.com: Invisible text cursor http://code.google.com/p/pharo/issues/detail?id=3951 Pharo image: Pharo 1.2.1 Pharo core version: #12345 Text cursor becomes invisible when disabling option "Blinking text cursor". Steps to reproduce: 1. Disable "Blinking text cursor" option 2. Switch between editor windows

April 4, 2011

Re: [Pharo-project] Pharo sprint at Brussels Friday 15th of April

by Johan Brichau

On 04 Apr 2011, at 11:45, Sven Van Caekenberghe wrote: > > On 04 Apr 2011, at 11:41, Johan Brichau wrote: > >> Place: Software Languages Lab, 10th floor of building F, Vrije Universiteit Brussel, Belgium > > And the timeframe ? 9:00 early enough for you? ;-) We can be there until 18:00.

April 4, 2011

Re: [Pharo-project] [ANN 1.2] 1.2.1 Full Release Image

by Serge Stinckwich

On Mon, Apr 4, 2011 at 4:16 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 03 Apr 2011, at 09:35, Marcus Denker wrote: > >> Â Â Â https://gforge.inria.fr/frs/download.php/28435/Pharo-1.2.1-11.04.03.zip >> >> >> Â Â Â Marcus > > Marcus et al, > > I have to agree with Laurent: you and the rest of Pharo are being way too modest here. Like most users I have been waiting for 1.2.x to be announced with a big splash. I know and understand how it has been a long and boring process at the end. > > Like you said, a release is just a release: a group of developers deciding that the current state of the system is 'good enough'. I have been using a #12333 hudson/jenkins built Seaside 3.0.3 image for more than a month for development and server deployment and it has been a very nice experience (in other words, it worked perfectly). > > So, from my part: thank you for all the efforts, the results are fantastic! > > So please, organize some kind of splash! +1 Yes i agree, we need to release Pharo 1.2. This is not perfect but this is usuable without too much problems. The next release will be better ;-) A big applause for the Pharo core team !!! -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

April 4, 2011

Re: [Pharo-project] Pharo sprint at Brussels Friday 15th of April

by Sven Van Caekenberghe

On 04 Apr 2011, at 11:41, Johan Brichau wrote: > Place: Software Languages Lab, 10th floor of building F, Vrije Universiteit Brussel, Belgium And the timeframe ?

April 4, 2011

Re: [Pharo-project] Pharo sprint at Brussels Friday 15th of April

by Johan Brichau

Hi guys, Time flies... I had forgotten all about it ;-) So here is the info: Place: Software Languages Lab, 10th floor of building F, Vrije Universiteit Brussel, Belgium Directions: http://www.vub.ac.be/english/infoabout/campuses/index.html#etterbeek Map: http://www.vub.ac.be/english/infoabout/campuses/etterbeek.html In case you have trouble finding it, please phone Andy: +32 494 42 32 56 or Johan: +32 476 78 64 45 If you are coming by car, you will need a barcode to access the campus. I will send that in a following email. cheers Johan On 04 Apr 2011, at 09:21, Sven Van Caekenberghe wrote: > > On 02 Apr 2011, at 09:31, StÃ©phane Ducasse wrote: > >> Johan Brichau and Andy Kellens are organizing a sprint at VUB. >> Please let us know who will join. >> I will join > > That's an offer I can't refuse: so yes, I'll be joining too. > > What are the details, timeframe & place ?

April 4, 2011

Re: [Pharo-project] Let's get rid of Core vs. Full

by Stuart Herring

On Mon, Apr 4, 2011 at 3:56 AM, Dale Henrichs <dhenrich(a)vmware.com> wrote: > Rather than abandon core vs full, here's a thought on a slightly different approach... > > Do development in the FULL version. That way the tools are used and bugs in the tools are fixed as the changes are made in the CORE...you are keeping the FULL alive, not adding new features, etc, since that kind of work is the responsibility of the maintainers ... > > Use the build server to run tests against the CORE and the set of CORE tools... > This is what makes the most sense to me as a user - and one that uses both core and dev. Dev is what I spend 99% of my time in, and of course core is what I actually deploy my applications on. But pretty much all of my impression of Pharo comes from Dev. The worry I would have about having only core releases, or core + untested Dev script would be that given the "clean design over backward compatibility" philosophy, none of the development tools would ever keep up with the changes in Core. You'd effectively have a product that was unusable to a developer (or at least, not a fair representation of how good Smalltalk can be for development). It basically comes down to this: Either you want to provide developer tools with Pharo or you do not. If you do not, then ditch Dev entirely, and make it very clear that Pharo is just a platform, and the third party developers of development tools will need to support Pharo specifically. If you do, then the Development tools need to be first class citizens. You need to develop in Dev - which is built from Core. And Dev needs to benefit from the same sorts of refactorings and cleanings as Core does, and tests in Dev must always be green (blue). Given that the webpage currently states that providing excellent development tools is a primary goal of Pharo, I feel that Dale's approach is what makes the most sense. Regards, Stuart

April 4, 2011

Re: [Pharo-project] SMx ToDo

by Fernando Olivero

I've started from the latest implementation of SMx, from the latest CUIS image. Juan did many differences, specially in the layout. For the ToDo list, i went thru the system categories of Morphic, detecting changed classes and additions. For the importing i'm also looking at the SMx in the latest Pharo Core image. People in the Squeak community, started a similar project. They chose to import the editor hierarchy as well, i prefer to go merge Pharo and CUIS, to detect the needed behavior of current Text-based morphs, and the new ones. I will start the (initial) port today, and hope to get it done before a couple of days. Maybe, when you have time we could discuss how to plug the EditorState behavior into the (new) PluggableTextMorph. Fernando On Fri, Apr 1, 2011 at 11:50 PM, Alain Plantec <alain.plantec(a)yahoo.com> wrote: > Hi Farnando, > > maybe I've missed something, do you want to merge > cuis morphic with Morphic of with SMxMorphic ? > another question, SMxMorphic is really out-to-date regarding current cuis ? > Alain > > Le 01/04/2011 16:04, Fernando Olivero a Ã©crit : >> >> Alain, this is the notes i gathered so far. >> >> I list the Cuis morphs i believe we should integrate, and those which >> we shouldn't. >> >> "Kernel" >> LayoutMorph. >> LayoutSpec. >> Morph. >> BorderedMorph. >> PluggableMorph. >> >> "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" >> "Common: merge?" >> MouseClickState. "check". >> MorphExtension. >> GrafPort. >> FormCanvas. >> DamageRecorder. >> EllipseMidpointTracer "for the GrafPort, check in Pharo?". >> HandMorph. >> PasteUpMorph. >> WorldState. >> >> "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" >> "basic Morphs" >> ImageMorph. >> RectangleMorph. >> PolygonMorph. >> StringMorph. >> TransformMorph. >> EllipseMorph. >> >> "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" >> "basic widgets-cuis" >> PluggableButtonMorph. >> PluggableMessageCategoryListMorph. >> BareTextMorph. >> TextModelMorph. >> >> "basic widgets-common" >> PluggableListMorph. >> LazyListMorph. >> PluggableListMorphByItem. >> PluggableListMorphOfMany. >> >> "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" >> "extra widgets" >> SketchMorph. >> FillInTheBlankMorph. >> >> "CUIS-extra-widgets" >> OneLineEditorMorph. >> >> "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" >> "Menus" >> MenuItemMorph. >> MenuLineMorph. >> MenuMorph. >> >> "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" >> "windows-common" >> ScrollPane. >> ScrollBar. >> ScrollbarButton. >> SystemWindow. >> >> "windows-new" >> BrowserCommentTextMorph. >> LayoutAdjustingMorph. >> WindowEdgeAdjustingMorph. >> >> "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" >> "other widgets" >> ColorPickerMorph. >> ProgressMorph. >> ProgressBarMorph. >> TranscriptMorph. >> >> "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" >> "MorphicEvents" >> "the same?" >> >> "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" >> "ENHANCEMENTS" >> "EditorState: Alains work that uses UndoManager, to provide unlimited >> undos, and visual feedback or search and replace in the proper Text >> presentation morphs" >> "Add the icon management to THEME" >> "Evaluate the polymorph features that are missing from (Cuis) Theme". >> "more ?" >> >> "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" >> "ommitted or removed" >> HaloMorph. " and family, no halos for now" >> BalloonMorph. "remove or replaced by a tooltip morph?, do we need a >> special morph?" >> MenuIcons. "moved to the themes in Pharo, themes own the icons to use" >> UpdatingMenuItemMorph. "?" >> TheWorldMenu. "pragma menu building on the WorldState in Pharo" >> MinimalStringMorph. "no usage for now, omit until a real usage appears" >> CurveMorph. "redundant maybe" >> MVCMenuMorph. "removed MVC-morphic integration" >> LimitedHeightTextMorph. "not used, only in examples, omit until a real >> usage appears". >> "LineMorph". "redundant: doesnt add behavior: remove?: replace by >> PolygonMorph lineFrom:to: color: width:" >> >> > > >

April 4, 2011

Re: [Pharo-project] [ANN 1.2] 1.2.1 Full Release Image

by Sven Van Caekenberghe

On 03 Apr 2011, at 09:35, Marcus Denker wrote: > https://gforge.inria.fr/frs/download.php/28435/Pharo-1.2.1-11.04.03.zip > > > Marcus Marcus et al, I have to agree with Laurent: you and the rest of Pharo are being way too modest here. Like most users I have been waiting for 1.2.x to be announced with a big splash. I know and understand how it has been a long and boring process at the end. Like you said, a release is just a release: a group of developers deciding that the current state of the system is 'good enough'. I have been using a #12333 hudson/jenkins built Seaside 3.0.3 image for more than a month for development and server deployment and it has been a very nice experience (in other words, it worked perfectly). So, from my part: thank you for all the efforts, the results are fantastic! So please, organize some kind of splash! Regards, Sven

April 4, 2011