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

[Pharo-project] 'Unnamed Topic' in Help

by Torsten Bergmann

Hi Mariano, hey, this was fixed and integrated in this issue some days ago: http://code.google.com/p/pharo/issues/detail?id=3512 This was integrated into #12293 but somehow it got reverted in a later update !???? I will open a new issue so it can be integrated again. We need this for 1.2 core even when 1.3 core is already prepared. ------------------------------------------------------ <explain> The help browser always displays the name of the topmost root topic, try HelpBrowser openOn: (HelpTopic named: 'MyName') If you add subtopics they will be displayed as books. By default it opens on "SystemHelp" which by accident creates an unnamed topic. The attached file fixes this. </explain> Bye T. -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

Jan. 19, 2011

[Pharo-project] Issue 3554 in pharo: CP1252TextConverter new does not work

by pharo＠googlecode.com

Status: Accepted Owner: stephane...(a)gmail.com Labels: Milestone-1.2 New issue 3554 by stephane...(a)gmail.com: CP1252TextConverter new does not work http://code.google.com/p/pharo/issues/detail?id=3554 when I execute CP1252TextConverter new in 1.1 it works Now in 1.2 I get DNU charcode CP1252TextConverter>>nextPut: aCharacter toStream: aStream aStream isBinary ifTrue: [^ aCharacter storeBinaryOn: aStream]. aCharacter charCode < 128 ifTrue: [aStream basicNextPut: aCharacter] ifFalse: [aStream basicNextPut: ((Character value: (self fromSqueak: aCharacter) charCode))]. aCharacter = $^ (self fromSqueak: aCharacter) = 128

Jan. 19, 2011

[Pharo-project] TextConverter 1.2 bug

by StÃ©phane Ducasse

Hi guys when I execute CP1252TextConverter new in 1.1 it works Now in 1.2 I get DNU charcode CP1252TextConverter>>nextPut: aCharacter toStream: aStream aStream isBinary ifTrue: [^ aCharacter storeBinaryOn: aStream]. aCharacter charCode < 128 ifTrue: [aStream basicNextPut: aCharacter] ifFalse: [aStream basicNextPut: ((Character value: (self fromSqueak: aCharacter) charCode))]. aCharacter = $^ (self fromSqueak: aCharacter) = 128 Does anybody have an idea? Thanks in advance. Stef

Jan. 19, 2011

Re: [Pharo-project] About XML Support in the 1.2

by Tudor Girba

Thanks, indeed. Does this mean that the next build will take this into account or must something else get changed as well? Cheers, Doru On 19 Jan 2011, at 21:24, StÃ©phane Ducasse wrote: > thanks laurent! > > On Jan 19, 2011, at 9:19 PM, laurent laffont wrote: > >> I've copied latest ConfigurationOfXMLSupport in MetacelloRepository. >> >> ConfigurationOfPharo-LaurentLaffont.121 >> >> XMLSupport: >> - update to release 1.1.6 >> - add project 'XMLSupport Tests' in group 'Dev Tools Tests' >> >> All 361 tests green. >> >> Laurent Laffont >> >> >> On Wed, Jan 19, 2011 at 1:18 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: >> The last version 1.1.6 is marked as #release. >> >> Cheers, >> Doru >> >> >> On 19 Jan 2011, at 12:26, laurent laffont wrote: >> >>> I put ConfigurationOfXMLSupport version 1.0 because blessing was #release. But I agree to change. >>> >>> Laurent >>> >>> On Wed, Jan 19, 2011 at 12:15 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> On Jan 19, 2011, at 11:43 AM, Tudor Girba wrote: >>> >>>> Indeed, this is a problem for Moose in general. We depend on XMLSupport, but now we cannot update it in PharoDev. I would also strongly support the idea of removing XMLSupport from PharoDev. >>>> >>> >>> What would be important: we need the latest version in Pharo 1.2... else how can we ever have a version where the tests are green? >>> (not of XML, but in general) >>> >>> Marcus >>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On 19 Jan 2011, at 11:32, Fabrizio Perin wrote: >>>> >>>>> Hi, >>>>> >>>>> I have a problem with the XMLSupport version from Pharo 1.2. >>>>> >>>>> The problem is that I need to work with one of the last version of XMLSupport but in the pharo image 1.2 is loaded an old version of XMLSupport (I mean a version from Jan 2010). I did try to load a newer version of XMLSupport using ConfigurationOfXMLSupport but some errors make this operation impossible. >>>>> So either Pharo-dev 1.2 load a newer (possibly the last) version of XMLSupport by default or Pharo-dev 1.2 should not load XMLSupport at all. >>>>> >>>>> I think that doesn't make sense to use by default such an old version, also considering that the last XMLSupport has nice and useful features like the XMLPluggableElementFactory. >>>>> >>>>> By avoiding to load XMLSupport in Pharo-dev 1.2 by default you let people free to use the version that they like. >>>>> >>>>> Thanks, >>>>> >>>>> Fabrizio >>>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "We cannot reach the flow of things unless we let go." >>>> >>>> >>>> >>>> >>> >>> -- >>> Marcus Denker -- http://www.marcusdenker.de >>> INRIA Lille -- Nord Europe. Team RMoD. >>> >>> >>> >> >> -- >> www.tudorgirba.com >> >> "If you interrupt the barber while he is cutting your hair, >> you will end up with a messy haircut." >> >> >> > > -- www.tudorgirba.com "Being happy is a matter of choice."

Jan. 19, 2011

Re: [Pharo-project] Issue 3543 in pharo: Merge latest Glamour theme

by pharo＠googlecode.com

Comment #3 on issue 3543 by stephane...(a)gmail.com: Merge latest Glamour theme http://code.google.com/p/pharo/issues/detail?id=3543 when we integrate we merge the package but now I imagine that the moose or glamour repo is not added in pharo so we cannot merge. Stef

Jan. 19, 2011

Re: [Pharo-project] Issue 3543 in pharo: Merge latest Glamour theme

by pharo＠googlecode.com

Comment #2 on issue 3543 by tudor.gi...(a)gmail.com: Merge latest Glamour theme http://code.google.com/p/pharo/issues/detail?id=3543 I am not sure I understand. In inbox you have Glamour.TudorGirba.25. Why did it try to search for version 23 somewhere else?

Jan. 19, 2011

Re: [Pharo-project] About XML Support in the 1.2

by StÃ©phane Ducasse

thanks laurent! On Jan 19, 2011, at 9:19 PM, laurent laffont wrote: > I've copied latest ConfigurationOfXMLSupport in MetacelloRepository. > > ConfigurationOfPharo-LaurentLaffont.121 > > XMLSupport: > - update to release 1.1.6 > - add project 'XMLSupport Tests' in group 'Dev Tools Tests' > > All 361 tests green. > > Laurent Laffont > > > On Wed, Jan 19, 2011 at 1:18 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > The last version 1.1.6 is marked as #release. > > Cheers, > Doru > > > On 19 Jan 2011, at 12:26, laurent laffont wrote: > > > I put ConfigurationOfXMLSupport version 1.0 because blessing was #release. But I agree to change. > > > > Laurent > > > > On Wed, Jan 19, 2011 at 12:15 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > On Jan 19, 2011, at 11:43 AM, Tudor Girba wrote: > > > >> Indeed, this is a problem for Moose in general. We depend on XMLSupport, but now we cannot update it in PharoDev. I would also strongly support the idea of removing XMLSupport from PharoDev. > >> > > > > What would be important: we need the latest version in Pharo 1.2... else how can we ever have a version where the tests are green? > > (not of XML, but in general) > > > > Marcus > > > >> Cheers, > >> Doru > >> > >> > >> On 19 Jan 2011, at 11:32, Fabrizio Perin wrote: > >> > >>> Hi, > >>> > >>> I have a problem with the XMLSupport version from Pharo 1.2. > >>> > >>> The problem is that I need to work with one of the last version of XMLSupport but in the pharo image 1.2 is loaded an old version of XMLSupport (I mean a version from Jan 2010). I did try to load a newer version of XMLSupport using ConfigurationOfXMLSupport but some errors make this operation impossible. > >>> So either Pharo-dev 1.2 load a newer (possibly the last) version of XMLSupport by default or Pharo-dev 1.2 should not load XMLSupport at all. > >>> > >>> I think that doesn't make sense to use by default such an old version, also considering that the last XMLSupport has nice and useful features like the XMLPluggableElementFactory. > >>> > >>> By avoiding to load XMLSupport in Pharo-dev 1.2 by default you let people free to use the version that they like. > >>> > >>> Thanks, > >>> > >>> Fabrizio > >>> > >> > >> -- > >> www.tudorgirba.com > >> > >> "We cannot reach the flow of things unless we let go." > >> > >> > >> > >> > > > > -- > > Marcus Denker -- http://www.marcusdenker.de > > INRIA Lille -- Nord Europe. Team RMoD. > > > > > > > > -- > www.tudorgirba.com > > "If you interrupt the barber while he is cutting your hair, > you will end up with a messy haircut." > > >

Jan. 19, 2011

Re: [Pharo-project] Issue 3553 in pharo: GeneralScrollPane should support both spaceFill and shrinkWrap

by pharo＠googlecode.com

Comment #1 on issue 3553 by tudor.gi...(a)gmail.com: GeneralScrollPane should support both spaceFill and shrinkWrap http://code.google.com/p/pharo/issues/detail?id=3553 I committed a SLICE in PharoInbox with Gary's changeset: Name: SLICE-Issue-3553-GeneralScrollPane-should-support-both-spaceFill-and-shrinkWrap-TudorGirba.1 Author: TudorGirba Time: 19 January 2011, 9:18:33 pm UUID: 88a790ab-e35b-49d7-b8d4-b4331a997211 Ancestors: Dependencies: Polymorph-Widgets-TudorGirba.368

Jan. 19, 2011

Re: [Pharo-project] About XML Support in the 1.2

by laurent laffont

I've copied latest ConfigurationOfXMLSupport in MetacelloRepository. ConfigurationOfPharo-LaurentLaffont.121 XMLSupport: - update to release 1.1.6 - add project 'XMLSupport Tests' in group 'Dev Tools Tests' All 361 tests green. Laurent Laffont On Wed, Jan 19, 2011 at 1:18 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > The last version 1.1.6 is marked as #release. > > Cheers, > Doru > > > On 19 Jan 2011, at 12:26, laurent laffont wrote: > > > I put ConfigurationOfXMLSupport version 1.0 because blessing was > #release. But I agree to change. > > > > Laurent > > > > On Wed, Jan 19, 2011 at 12:15 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > > > > On Jan 19, 2011, at 11:43 AM, Tudor Girba wrote: > > > >> Indeed, this is a problem for Moose in general. We depend on XMLSupport, > but now we cannot update it in PharoDev. I would also strongly support the > idea of removing XMLSupport from PharoDev. > >> > > > > What would be important: we need the latest version in Pharo 1.2... else > how can we ever have a version where the tests are green? > > (not of XML, but in general) > > > > Marcus > > > >> Cheers, > >> Doru > >> > >> > >> On 19 Jan 2011, at 11:32, Fabrizio Perin wrote: > >> > >>> Hi, > >>> > >>> I have a problem with the XMLSupport version from Pharo 1.2. > >>> > >>> The problem is that I need to work with one of the last version of > XMLSupport but in the pharo image 1.2 is loaded an old version of XMLSupport > (I mean a version from Jan 2010). I did try to load a newer version of > XMLSupport using ConfigurationOfXMLSupport but some errors make this > operation impossible. > >>> So either Pharo-dev 1.2 load a newer (possibly the last) version of > XMLSupport by default or Pharo-dev 1.2 should not load XMLSupport at all. > >>> > >>> I think that doesn't make sense to use by default such an old version, > also considering that the last XMLSupport has nice and useful features like > the XMLPluggableElementFactory. > >>> > >>> By avoiding to load XMLSupport in Pharo-dev 1.2 by default you let > people free to use the version that they like. > >>> > >>> Thanks, > >>> > >>> Fabrizio > >>> > >> > >> -- > >> www.tudorgirba.com > >> > >> "We cannot reach the flow of things unless we let go." > >> > >> > >> > >> > > > > -- > > Marcus Denker -- http://www.marcusdenker.de > > INRIA Lille -- Nord Europe. Team RMoD. > > > > > > > > -- > www.tudorgirba.com > > "If you interrupt the barber while he is cutting your hair, > you will end up with a messy haircut." > > >

Jan. 19, 2011

[Pharo-project] Issue 3553 in pharo: GeneralScrollPane should support both spaceFill and shrinkWrap

by pharo＠googlecode.com

Status: Accepted Owner: tudor.gi...(a)gmail.com Labels: Milestone-1.2 Importance-Low Type-RequestForEnhancement New issue 3553 by tudor.gi...(a)gmail.com: GeneralScrollPane should support both spaceFill and shrinkWrap http://code.google.com/p/pharo/issues/detail?id=3553 We should be allowed to have a scroll bar that #spaceFill along one dimensions and #shrinkWrap along another one. The attached CS from Gary fixes the situation for GeneralScrollPane, and the following script works as expected: |m| m := PanelMorph new. m fillStyle: Color green; hResizing: #spaceFill; vResizing: #spaceFill; changeTableLayout; layoutInset: 8. m addMorph: (Morph new height: 160; minWidth: 100; hResizing: #spaceFill; vResizing: #shrinkWrap). GeneralScrollPane new changeScrollerTableLayout; scrollTarget: m; openInWindow Attachments: GeneralScrollPaneLayout.2.cs 1.7 KB

Jan. 19, 2011