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

[Pharo-project] Issue 3962 in pharo: More cleanup of PasteUpMorph

by pharo＠googlecode.com

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3962 by marcus.d...(a)gmail.com: More cleanup of PasteUpMorph http://code.google.com/p/pharo/issues/detail?id=3962 ... related to World-In-World support and general dead code Attachments: CleanPasteUpM.1.cs 4.4 KB

April 5, 2011

[Pharo-project] Issue 3961 in pharo: Fix order of worlmenu

by pharo＠googlecode.com

Status: FixToInclude Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3961 by marcus.d...(a)gmail.com: Fix order of worlmenu http://code.google.com/p/pharo/issues/detail?id=3961 ... System was wrong Attachments: fixMenu.1.cs 3.1 KB

April 5, 2011

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by Sven Van Caekenberghe

On 05 Apr 2011, at 07:09, laurent laffont wrote: > Remarks: > - group changed by categories: Morphic/Polymorph, Tools, Under the hood, ... > - Mocketry is not included in Pharo 1.2 Thanks for the feedback, I applied your suggestions. And uploaded a newer version. More comments ? Sven

April 5, 2011

Re: [Pharo-project] Issue 3960 in pharo: Catch all: Remove experimental + ancient backward compatibility code

by pharo＠googlecode.com

Comment #1 on issue 3960 by marcus.d...(a)gmail.com: Catch all: Remove experimental + ancient backward compatibility code http://code.google.com/p/pharo/issues/detail?id=3960 remove #fileOutChangeSet:andObject: reason "An experimental version to fileout a changeSet first so that a project can contain its own classes" Attachments: RemoveExperimental.1.cs 158 bytes

April 5, 2011

[Pharo-project] Issue 3960 in pharo: Catch all: Remove experimental + ancient backward compatibility code

by pharo＠googlecode.com

Status: Started Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3960 by marcus.d...(a)gmail.com: Catch all: Remove experimental + ancient backward compatibility code http://code.google.com/p/pharo/issues/detail?id=3960 There is still a lot of code in the image where the comment says things like "will be removed soon" "for backward compatibilty" "needed for loading old image segments" "experimental" This tracker entry is a place to put notes for them so we either deprecate for real or just remove

April 5, 2011

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by laurent laffont

On Mon, Apr 4, 2011 at 11:01 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > I have a draft for a release announcement for Pharo 1.2.1 > > http://homepage.mac.com/svc/Pharo/pharo-1.2.1-release.html Cool ! I will do a french translation this evening. Remarks: - group changed by categories: Morphic/Polymorph, Tools, Under the hood, ... - Mocketry is not included in Pharo 1.2 Cheers, Laurent. > > > [ THIS IS A DRAFT !! - DO NOT YET RELEASE ] > > Please check this for errors and omissions, I will try to integrate the > remarks tomorrow. Please check the links as well. > > I tried to stick with the basics, as one could write about so much > (introducing Pharo Smalltalk and its features could be useful, but is quite > challenging; everything loaded into dev could be described, and so on). I am > sure I am not doing justice to all efforts by everybody, please give > feedback. > > To give it a little twist, I started with a little 'story' called 'Update > #12345', maybe it is to geeky, but it felt like a good angle to cover the > basics about the process and the time spent. > > The most useful raw material was this > http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotTwo > > It feels as if more could be said about Dev. > > I also tried to stick with just a simple screenshot, I could come up with > more complicated ones, but we cannot put everything on one screenshot. > > Sven > > > >

April 5, 2011

Re: [Pharo-project] ci.pharo-project.org redirect should be changed?

by laurent laffont

On Mon, Apr 4, 2011 at 11:32 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi... currently ci.pharo-project.org redirects to > https://pharo-ic.lille.inria.fr/hudson/view/Pharo/ > but I think it should be https://pharo-ic.lille.inria.fr/ since > everything inside there is Pharo. Pharo is not just the Pharo image. > > what do you think? > +1 Laurent > > -- > Mariano > http://marianopeck.wordpress.com > >

April 5, 2011

[Pharo-project] Status of Weak enhancements in Pharo

by Miguel CobÃ¡

What is the status of the Weak enhancements that were applied to Squeak 4.2 (by Levente and Igor, mainly) and were targeted for inclusion in Pharo? Is there a list of them somewhere? which ones are integrated and which ones are not yet? Other question, is the plan to take the enhancements as they are and apply them on Pharo, that is, the versions in Squeak are the reference or there are conflicting versions in Pharo that are to be keep instead. I remember that some changes were made to Pharo in this regard. Cheers -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

April 5, 2011

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by Serge Stinckwich

On Tue, Apr 5, 2011 at 8:42 AM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > On Tue, Apr 5, 2011 at 4:01 AM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: >> I have a draft for a release announcement for Pharo 1.2.1 >> >> Â Â Â Â http://homepage.mac.com/svc/Pharo/pharo-1.2.1-release.html >> >> [ THIS IS A DRAFT !! - DO NOT YET RELEASE ] >> >> Please check this for errors and omissions, I will try to integrate the remarks tomorrow. Please check the links as well. > > Great Sven, maybe you could put this information on the wiki so the > people could modify it more easily. > >> I tried to stick with the basics, as one could write about so much (introducing Pharo Smalltalk and its features could be useful, but is quite challenging; everything loaded into dev could be described, and so on). I am sure I am not doing justice to all efforts by everybody, please give feedback. >> >> To give it a little twist, I started with a little 'story' called 'Update #12345', maybe it is to geeky, but it felt like a good angle to cover the basics about the process and the time spent. >> >> The most useful raw material was this http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotTwo >> >> It feels as if more could be said about Dev. > > StÃ©phane already suggest to look at all the issues solved during 1.2: > > http://code.google.com/p/pharo/issues/list?can=1&q=milestone=1.2 > http://code.google.com/p/pharo/issues/list?can=1&q=Milestone%3D1.2-DevImage > > The related issues could be added before the description of the changes: > #2943, #3036 SUnit 4 integration > > For future releases, i guess a semi-automatic changelog could be done > with the list of issues. This is quite difficult now to know exactly from the list of issues which one have been integrated effectively in 1.2 or not. Some issues are closed, some other are their fix/enhancements integrated in the image. Maybe for future releases, when a fix/enhancements is accepted, the issue could be tagged with a label like : in1.3 The idea is to be able to extract the list of updates directly from issues. What do you think about that ? Regards -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

April 5, 2011

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

by GermÃ¡n Arduino

Not my case, I use to use 1.1.1 and 1.2 even in a netbook Lenovo x100 with no problems (Under Linux of course :) 2011/4/4, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > Please someone clarify, are you going to kill the core? > > Honestly I don't know how people survive with the dev image, I guess > you have super fast laptops. > > Not my case, and the Core just run nice in "old" hardware. > > 2011/4/4 GermÃ¡n Arduino <garduino(a)gmail.com>: >> As I can understand the proposal of Marcus is not have anymore an >> image without the minimal set of tools for development. And I full >> agree with this option. >> >> Allways is possible to shrink the image in a next step if needed. In >> other words, to me Core is not useful witthout a minimal set of dev >> tools and I'm doing production deployments with such tools with no >> problems. By other hand, as most of the images are in remote servers I >> need to use them via VNC and with the dev tools. >> >> Just my opinion. >> >> Cheers. >> >> >> 2011/4/4 Tudor Girba <tudor.girba(a)gmail.com>: >>> This is what I understood from what Marcus said, too :) >>> >>> Cheers, >>> Doru >>> >>> >>> On 4 Apr 2011, at 15:57, StÃ©phane Ducasse wrote: >>> >>>> This is my ideas. >>>> >>>>> My proposition for 1.3: >>>>> 1) Add MetacelloBrowser and switch to version-separated repositories >>>>> (like MetaRepoForPharo11, etc. -I don't like the "abbreviated names" >>>>> but you get the idea) >>>>> 2) Reduce the "full" image to >>>>> Core+OB+RB+Shout+OCompletion+Finder+MetacelloBrowser >>>>> 3) If it is possible, develop Core image into this reduced full image. >>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing should have the right to be different." >>> >> >> > > > > -- > HernÃ¡n Morales > Information Technology Manager, > Institute of Veterinary Genetics. > National Scientific and Technical Research Council (CONICET). > La Plata (1900), Buenos Aires, Argentina. > Telephone: +54 (0221) 421-1799. > Internal: 422 > Fax: 425-7980 or 421-1799. > > -- ================================================= GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino Arduino Software & Web Hosting http://www.arduinosoftware.com PasswordsPro http://www.passwordspro.com =================================================

April 5, 2011