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

Re: [Pharo-project] Issue 3506 in pharo: TextMorph's #autoFit: and #wrapFlag: are confusing

by pharo＠googlecode.com

Comment #5 on issue 3506 by sean.p.d...(a)gmail.com: TextMorph's #autoFit: and #wrapFlag: are confusing http://code.google.com/p/pharo/issues/detail?id=3506 I can't find the mcz. I'm attaching the changes - "Fix-3506-TextMorphs-autoFit-and-wrapFlag-are-confusing-SeanDeNigris.1.cs". Attachments: Fix-3506-TextMorphs-autoFit-and-wrapFlag-are-confusing-SeanDeNigris.1.cs 571 bytes

Jan. 29, 2011

Re: [Pharo-project] Issue 3607 in pharo: MNU #stylerStyled: in Finder for basic usage

by pharo＠googlecode.com

Comment #2 on issue 3607 by Benjamin...(a)gmail.com: MNU #stylerStyled: in Finder for basic usage http://code.google.com/p/pharo/issues/detail?id=3607 I guess the dev image doesn't have the good version of PluggableTextMorph, I dunno :s

Jan. 29, 2011

[Pharo-project] [update 1.3] #13028

by StÃ©phane Ducasse

13028 ----- - Fully deprecate ParagraphEditor Stef

Jan. 29, 2011

Re: [Pharo-project] Issue 3610 in pharo: Should remove Morphic-Undo

by pharo＠googlecode.com

Updates: Labels: Milestone-1.3 Comment #5 on issue 3610 by stephane...(a)gmail.com: Should remove Morphic-Undo http://code.google.com/p/pharo/issues/detail?id=3610 ;) We cannot decently deprecate everything we would double the number of methods :) Stef

Jan. 29, 2011

[Pharo-project] [update 1.3] #13028

by StÃ©phane Ducasse

13028 ----- - Fully deprecate ParagraphEditor

Jan. 29, 2011

[Pharo-project] [update 1.3] #13027

by StÃ©phane Ducasse

13027 ----- - Deprecate Object>>notifyWithLabel: - Issue 3618: logError: aString inContext: aContext to: is used and it is deprecated Stef

Jan. 29, 2011

Re: [Pharo-project] Issue 3618 in pharo: logError: aString inContext: aContext to: is used and it is deprecated

by pharo＠googlecode.com

Comment #3 on issue 3618 by stephane...(a)gmail.com: logError: aString inContext: aContext to: is used and it is deprecated http://code.google.com/p/pharo/issues/detail?id=3618 in fact it did not make it in. So fixed in 12027 (strange). Too many people talking around probably.

Jan. 29, 2011

Re: [Pharo-project] Issue 3618 in pharo: logError: aString inContext: aContext to: is used and it is deprecated

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3618 by stephane...(a)gmail.com: logError: aString inContext: aContext to: is used and it is deprecated http://code.google.com/p/pharo/issues/detail?id=3618 Normally we fixed that yesterday in 13025 Let us know if this is not the case

Jan. 29, 2011

Re: [Pharo-project] Issue 3620 in pharo: Settings: OCompletion settings appear twice

by StÃ©phane Ducasse

But why the UI collects the squeak preferences? >> Comment #1 on issue 3620 by laurent....(a)gmail.com: Settings: OCompletion settings appear twice >> http://code.google.com/p/pharo/issues/detail?id=3620 >> >> Fix (naive) here: SLICE-Issue-3620-Settings-OCompletion-settings-appear-twice-LaurentLaffont.1 >> >> > > The actual problem is that SettingsBrowser is showing Squeak's pragma preferences as Pharo's system settings. See SettingTreeBuilder >> #preference:category:description:type: for the implementation. > > I see three possible scenarios to resolve this issue: > 1. Your fix will be accepted (which implies that OCompletion will be forked). > 2. We remove ECPreferences class >> #settingsOn: from OCompletion. > 3. You remove SettingTreeBuilder >> #preference:category:description:type: from Pharo. > > > Levente >

Jan. 29, 2011

Re: [Pharo-project] Uri vs. Url

by StÃ©phane Ducasse

I started to go over all the methods and tests + added comments. Now I would like to see URI really used. But I need also help. Stef On Jan 29, 2011, at 9:37 AM, Marcus Denker wrote: > > On Jan 29, 2011, at 9:17 AM, DeNigris Sean wrote: > >> It confuses me that the URI and Url class hierarchies are separate, given that a URL is a subset of URI (http://en.wikipedia.org/wiki/Uniform_Resource_Identifier#Relationship_to_UR…) Does it make sense to unify these? >> > > Hi, > > The history behind is the following. > > Impara implemented URI and used it for all their products and Sophie later. The idea was in 3.9 to integrate URI and then remove > Url later in another step. But sadly, already the first step was never really done: we integrated the URI package, but the (for 3.9)planed > second pass did never happen. (to replace Urls and just keep them for compatibility, together with syncing with sophie fixes). > > Wo should do another pass, yes. > > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

Jan. 29, 2011