December 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3485 in pharo: VMMaker does not load on Pharo 1.2

by StÃ©phane Ducasse

> > The documented format is: > > Timestampstrings can be of the form: > <authorname><date><time>. > <authorname><date> > <date><time> > <date><time><authorname> > <date><authorname> > <historical> > > > Says /who/? When I created all these timestamps to document a refactoring change there was no documented restriction on timestamps I could see. Why impose restrictions which have little value? Why needlessly break compatibility? That timestamp *contains useful information*. Why ban it? > > If you *want* VMMaker to load in Pharo you need to ensure that Pharo supports the timestamps *that exist* not the timestamps you want to impose on the community. Eliot we do not impose anything to the community. Please do not bash us we have enough to do without that! Apparently the code was like that and people (may be johan) started to make sense out of it. Stef

Dec. 29, 2010

Re: [Pharo-project] RecentMessages -> MessageNotUnderstood: PluggableTextMorph>>stylerStyled:

by StÃ©phane Ducasse

Hi benjamin can you explain a bit the problem/solution because it looks like a lot of code :) Stef On Dec 28, 2010, at 4:43 PM, Benjamin wrote: > Yes I know, I've written a fix, but forget to post it :) > > Now it's done, try that: http://code.google.com/p/pharo/issues/detail?id=3486 > > > Ben > > On Dec 28, 2010, at 12:36 PM, Mariano Martinez Peck wrote: > >> Hi. With the pharo dev 1.2 from here: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/… >> >> if I open a RecentMessages and click over one of the classes, I get the MessageNotUnderstood: PluggableTextMorph>>stylerStyled: >> >> I attach PharoDebug.log >> >> Cheers >> >> mariano >> >> >> <PharoDebug copy.log> >

Dec. 29, 2010

[Pharo-project] Issue 3491 in pharo: Preferences are still referenced in Pharo-dev 1.2

by pharo＠googlecode.com

Status: Accepted Owner: Torsten....(a)astares.de New issue 3491 by Torsten....(a)astares.de: Preferences are still referenced in Pharo-dev 1.2 http://code.google.com/p/pharo/issues/detail?id=3491 see Pen>>arrowHead and EnvelopeEditorMorph>>wantsRoundedCorners also in Soundsystem (see http://code.google.com/p/pharo/issues/detail?id=3489) and the metacello config (see http://code.google.com/p/pharo/issues/detail?id=3490)

Dec. 29, 2010

Re: [Pharo-project] Issue 3490 in pharo: ConfigurationOfPharo still uses Preferences

by pharo＠googlecode.com

Updates: Labels: Milestone-1.2 Comment #1 on issue 3490 by Torsten....(a)astares.de: ConfigurationOfPharo still uses Preferences http://code.google.com/p/pharo/issues/detail?id=3490 (No comment was entered for this change.)

Dec. 29, 2010

Re: [Pharo-project] are we going to remove MethodFinder and MessagesNames for Pharo 1.2?

by Mariano Martinez Peck

On Wed, Dec 29, 2010 at 10:18 AM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > No preference plague. > Now we will keep the tool in 1.2 and remove them in 1.3. > Ok, it is cool...but, as I said...image it is your first time you open pharo...you will have THREE tools which looks similar. You don't know its differences, nor which to use. And the menu is starting to be long. Can we at least remove them from the menu as I suggested (not the code) ? Poeple that prefer MessagesSend / MethodFInder know how to put them back on the menu or open them by hand. > And we should bug fixes the new tool on the way. > > Stef > > On Dec 28, 2010, at 1:53 PM, Guillermo Polito wrote: > > > Maybe that can be a preference... > > > > On Tue, Dec 28, 2010 at 8:51 AM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > > yes, yes, depreacting. But....it is confusing having THREE things for the > same stuff. > > > > So, since we now have "Finder" and we want to push that, what about > removing MethodFinder and MessagesNames for Pharo 1.2? > > > > At least, what about removing them from the menu so that not to confuse > new comers. And then, those hacky guys that prefer MethodFinder or > MessagesNames can add it to the menu or open it by hand. And then, in 1.3 we > really remove not only form menu but the code itself. > > > > Cheers > > > > mariano > > > > >

Dec. 29, 2010

[Pharo-project] Issue 3490 in pharo: ConfigurationOfPharo still uses Preferences

by pharo＠googlecode.com

Status: Accepted Owner: Torsten....(a)astares.de New issue 3490 by Torsten....(a)astares.de: ConfigurationOfPharo still uses Preferences http://code.google.com/p/pharo/issues/detail?id=3490 - see #preloadForPharo and #postloadForPhaor - same in ConfigurationOfNonPharo

Dec. 29, 2010

Re: [Pharo-project] Issue 3489 in pharo: Pharo 1.2-dev still uses Preferences in BaseSoundSystem

by pharo＠googlecode.com

Comment #4 on issue 3489 by Torsten....(a)astares.de: Pharo 1.2-dev still uses Preferences in BaseSoundSystem http://code.google.com/p/pharo/issues/detail?id=3489 But there is no setting similar to the old "Preferences soundQuickStart"

Dec. 29, 2010

Re: [Pharo-project] Issue 3489 in pharo: Pharo 1.2-dev still uses Preferences in BaseSoundSystem

by pharo＠googlecode.com

Comment #3 on issue 3489 by Torsten....(a)astares.de: Pharo 1.2-dev still uses Preferences in BaseSoundSystem http://code.google.com/p/pharo/issues/detail?id=3489 Could be replaced with "SoundSettings soundEnabled"

Dec. 29, 2010

Re: [Pharo-project] Issue 2130 in pharo: cleanUpForRelease and friends should use new cleanUp protocol

by pharo＠googlecode.com

Comment #5 on issue 2130 by stephane.ducasse: cleanUpForRelease and friends should use new cleanUp protocol http://code.google.com/p/pharo/issues/detail?id=2130 so what is left to do?

Dec. 29, 2010

Re: [Pharo-project] Pharo 1.2 - default packages

by StÃ©phane Ducasse

Hi guys May be we should focus more on the metacello repositories because PharoDev could just be one config in the 1.2 repository and with metacello repositories we could have more structuring impact. Stef

Dec. 29, 2010