- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Class-side hierarchy to show meta-classes?

by StÃ©phane Ducasse

I think that it can be quite confusing for beginners. I would put at the minimum a setting to disable it. Stef > Working on case 12498 [1] has evolved to the idea of the class-side hierarchy showing meta-classes per attached snapshot. I'd like some community feedback on the idea. Note the metaclasses are bolded similar to how bold indicates class-side methods. > > Thanks Nicolai for your help so far. > cheers -ben > > [1] https://pharo.fogbugz.com/f/cases/12498/ > <Case12498-4.png>

Dec. 27, 2013

Re: [Pharo-dev] problem while parsing xml

by StÃ©phane Ducasse

I do not know but monty adding worth behavior. Now we could always revert to the previous configuration version. Stef Here is the mail that he sent a while ago: These updates add validation against internal and external DTDs, proper replacement of general and parameter entites, customizable resolution of external parsed entities using Zinc and FileSystem, awareness of notations and unparsed entities, preservation of the internal DTD subset by the DOM parser (so printing a parsed doc with a DTD will produce approximately what was input), line numbers reporting in error messages, and better well-formed and validity constraints. I had to largely rewrite the tokenizer to make everything work, but I followed the spec closely, and it is about the same speed as long as there is no DTD to validate against. One problem is that while the tests I added and the existing tests all pass, for some reason helper messages in some test classes starting with "should" (in the style of should:raise:) are being interpreted as tests and run by TestRuner, even though they don't begin with "test" and take arguments! This is possibly a bug in TestRunner. Another problem is that there are so many deprecated methods cluttering up classes, some of which have been deprecated for years! It is confusing and hard to see which methods to use just by browsing the protocols. I would really suggest using this code to get rid of the XML-Parser methods that have been deprecated for at least a year: expiry := 1 year. (SystemNavigation default allClassesInPackageNamed: 'XML-Parser') do: [:class | class selectors do: [:selector | | compiledMethod timeStamp | compiledMethod := class compiledMethodAt: selector. timeStamp := compiledMethod timeStamp copyAfter: Character space. (compiledMethod isDeprecated and: [(DateAndTime now - (DateAndTime fromString: timeStamp)) > expiry]) ifTrue: [class removeSelector: selector]]]. I ran and checked it myself and it doesn't break anything. Running the above with XML-Writer-Core might not be a bad idea either. I also updated BitmapCharacterSet to use less memory. > In an image with XML-Parser-NorbertHartl.141 both expression work. > > I see that in PharoExtras/XMLParser there are many commits by âmontyâ all with empty log messages - how is that possible ?? > > On 27 Dec 2013, at 16:57, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" standalone="no"?> >> <!DOCTYPE score-partwise PUBLIC >> "-//Recordare//DTD MusicXML 3.0 Partwise//EN" >> "http://www.musicxml.org/dtds/partwise.dtd"> >> <score-partwise version="3.0"> >> <part-list> >> <score-part id="P1"> >> <part-name>Music</part-name> >> </score-part> >> </part-list> >> </score-partwise> >> ' readStream. >> >> produces the error >> while >> >> XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" standalone="no"?> >> <score-partwise version="3.0"> >> <part-list> >> <score-part id="P1"> >> <part-name>Music</part-name> >> </score-part> >> </part-list> >> </score-partwise> >> ' readStream. >> >> does not. >> >> Stef >> > >

Dec. 27, 2013

Class-side hierarchy to show meta-classes?

by btc＠openinworld.com

Working on case 12498 [1] has evolved to the idea of the class-side hierarchy showing meta-classes per attached snapshot. I'd like some community feedback on the idea. Note the metaclasses are bolded similar to how bold indicates class-side methods. Thanks Nicolai for your help so far. cheers -ben [1] https://pharo.fogbugz.com/f/cases/12498/

Dec. 27, 2013

Re: [Pharo-dev] problem while parsing xml

by Sven Van Caekenberghe

In an image with XML-Parser-NorbertHartl.141 both expression work. I see that in PharoExtras/XMLParser there are many commits by âmontyâ all with empty log messages - how is that possible ?? On 27 Dec 2013, at 16:57, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" standalone="no"?> > <!DOCTYPE score-partwise PUBLIC > "-//Recordare//DTD MusicXML 3.0 Partwise//EN" > "http://www.musicxml.org/dtds/partwise.dtd"> > <score-partwise version="3.0"> > <part-list> > <score-part id="P1"> > <part-name>Music</part-name> > </score-part> > </part-list> > </score-partwise> > ' readStream. > > produces the error > while > > XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" standalone="no"?> > <score-partwise version="3.0"> > <part-list> > <score-part id="P1"> > <part-name>Music</part-name> > </score-part> > </part-list> > </score-partwise> > ' readStream. > > does not. > > Stef >

Dec. 27, 2013

Re: [Pharo-dev] Call for fixing the selection in the debugger

by Andrei Chis

PluggableTextMorph maintains its own selectionInterval. When the PluggableTextMorph >>selectionInterval: it is called it sets the selection in the model. This will trigger MorphicTextAdapter>>setSelectionFromModel: that should adapt the selection in the morph: MorphicTextAdapter >>setSelectionFromModel: aSelection self widget ifNotNil: [:w | w selectionInterval ~= aSelection ifTrue: [ w setSelection: aSelection ]]. However, the second test (w selectionInterval ~= aSelection) will always return false. This is because PluggableTextMorph>>selectionInterval has the following implementation '^ textMorph editor selectionInterval' And in the editor the selection is already correct (even before PluggableTextMorph >>selectionInterval: is called). Actually most of the methods from PluggableTextMorph that change the selection also explicitly update the selectionInterval instance variable. So the previous solution should work. @Doru this is related with Spec, so we should not have it in Glamour. On Fri, Dec 27, 2013 at 5:07 PM, Benjamin < Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > I think that when the model is notified, it will set it in the morph > So it will happen twice > > Ben > > On 27 Dec 2013, at 15:52, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Wouldn't then explicitly setting the selection of the morph before setting > it in the model be ok? > > PluggableTextMorph>>selectionInterval: sel > selectionInterval := sel. > setSelectionSelector > ifNotNil: [ self model perform:setSelectionSelector with: sel ] > > > On Fri, Dec 27, 2013 at 4:28 PM, Benjamin < > Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > >> ok :( >> Then I run out of brilliant idea :P >> >> >> Ben >> >> On 27 Dec 2013, at 15:25, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: >> >> Adding 'self changed' at the end of the current PluggableTextMorph>>selectionInterval: >> doesn't solve the problem. >> >> >> On Fri, Dec 27, 2013 at 4:15 PM, Benjamin < >> Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >> >>> Because when the focus changes, the morph is proposed to redraw itself >>> Try with a >>> >>> self changed >>> >>> at the end >>> >>> Ben >>> >>> On 27 Dec 2013, at 14:44, Andrei Chis <chisvasileandrei(a)gmail.com> >>> wrote: >>> >>> >>> The change that seems to have caused this problem is in >>> PluggableTextMorph>>selectionInterval: The selectionInterval instance >>> variable of the morph is not set any more; only the model is updated, which >>> doesn't seem to update the morph. >>> >>> PluggableTextMorph>>selectionInterval: sel >>> setSelectionSelector >>> ifNil: [ selectionInterval := sel ] >>> ifNotNil: [ self model perform:setSelectionSelector with: sel ] >>> >>> This could be solved like bellow, though I'm not sure it is the best >>> solution. >>> If I put a halt in PluggableTextMorph >>inspectIt and hit proceed the >>> the selection is inspected correctly, without this modification. >>> >>> PluggableTextMorph>>selectionInterval: sel >>> selectionInterval := sel. >>> setSelectionSelector >>> ifNotNil: [ self model perform:setSelectionSelector with: sel ] >>> >>> >>> >>> >>> >>> On Fri, Dec 27, 2013 at 3:11 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: >>> >>>> >>>> On 27 Dec 2013, at 13:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>> wrote: >>>> >>>> > Hi guys >>>> > >>>> > we should not let the system in such state. We cannot inspect print >>>> expression in the debugger. >>>> > Does anybody have an idea of the change that broke it? >>>> > >>>> Yes: >>>> >>>> https://pharo.fogbugz.com/f/cases/12144/TextModel-getSelection >>>> >>>> it was added in 655, so for reverting the easiest is to dl 654, do a >>>> merge and look at all the changes >>>> (there are just 4-5 that are not re-catorizations). >>>> >>>> This is on my TODO nextâ¦ >>>> >>>> Marcus >>>> >>>> >>>> >>> >>> >> >> > >

Dec. 27, 2013

Re: [Pharo-dev] problem while parsing xml

by StÃ©phane Ducasse

XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE score-partwise PUBLIC "-//Recordare//DTD MusicXML 3.0 Partwise//EN" "http://www.musicxml.org/dtds/partwise.dtd"> <score-partwise version="3.0"> <part-list> <score-part id="P1"> <part-name>Music</part-name> </score-part> </part-list> </score-partwise> ' readStream. produces the error while XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" standalone="no"?> <score-partwise version="3.0"> <part-list> <score-part id="P1"> <part-name>Music</part-name> </score-part> </part-list> </score-partwise> ' readStream. does not. Stef

Dec. 27, 2013

Re: [Pharo-dev] Change Sorter

by StÃ©phane Ducasse

A bug I thought it was fixed during the sprint. Ben this is an opportunity to contribute :) On 27 Dec 2013, at 16:45, btc(a)openinworld.com wrote: > In build 30644 I notice that ChangeSorter seems to have lost most of its usual menu items. For example... > * Copy class to the other change set > * Move class to the other change set > * File out > > Is this intentional as a transition to something else? > cheers -ben > >

Dec. 27, 2013

Re: [Pharo-dev] problem while parsing xml

by Sven Van Caekenberghe

It seems logical that a CharacterSet contains Characters even if its internal implementation uses a bitmap, its API should - I would expect. If nextChar is an Integer in the first code piece, maybe you are reading from a binary stream instead of from a character stream ? On 27 Dec 2013, at 16:34, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > Iâm trying to understand asciiValue > > skipSeparators > | nextChar | > [(nextChar := self peek) not Nil > and: [SeparatorCharacters includes: nextChar]] > whileTrue: [self next]. > > > SeparatorCharacters is a CharacterSet > > nextChar is an integer > > and > > CharacterSet>>includes: aCharacter > aCharacter asciiValue >= 256 > ifTrue: [^ false]. > ^ (map at aCharacter asciiValue + 1) >0 > > but Iâm stuck. > > Stef > > >

Dec. 27, 2013

Re: [Pharo-dev] Call for fixing the selection in the debugger

by Tudor Girba

Hi, I reported the problem already: https://pharo.fogbugz.com/f/cases/12479/SpecDebugger-cannot-inspect-from-th… I just tried the GTDebugger in the latest Pharo and it works just fine. If the problem would be in the PluggableTextMorph, it should affect the GTDebugger, too since it is using only a slightly more specialized widget. Or? Andrei, do you have an idea? Cheers, Doru On Fri, Dec 27, 2013 at 4:40 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > **thanks** guys for looking into that because this is blocking. > > Stef > > > > I think that when the model is notified, it will set it in the morph > So it will happen twice > > Ben > > On 27 Dec 2013, at 15:52, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > Wouldn't then explicitly setting the selection of the morph before setting > it in the model be ok? > > PluggableTextMorph>>selectionInterval: sel > selectionInterval := sel. > setSelectionSelector > ifNotNil: [ self model perform:setSelectionSelector with: sel ] > > > On Fri, Dec 27, 2013 at 4:28 PM, Benjamin < > Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > >> ok :( >> Then I run out of brilliant idea :P >> >> >> Ben >> >> On 27 Dec 2013, at 15:25, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: >> >> Adding 'self changed' at the end of the current PluggableTextMorph>>selectionInterval: >> doesn't solve the problem. >> >> >> On Fri, Dec 27, 2013 at 4:15 PM, Benjamin < >> Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >> >>> Because when the focus changes, the morph is proposed to redraw itself >>> Try with a >>> >>> self changed >>> >>> at the end >>> >>> Ben >>> >>> On 27 Dec 2013, at 14:44, Andrei Chis <chisvasileandrei(a)gmail.com> >>> wrote: >>> >>> >>> The change that seems to have caused this problem is in >>> PluggableTextMorph>>selectionInterval: The selectionInterval instance >>> variable of the morph is not set any more; only the model is updated, which >>> doesn't seem to update the morph. >>> >>> PluggableTextMorph>>selectionInterval: sel >>> setSelectionSelector >>> ifNil: [ selectionInterval := sel ] >>> ifNotNil: [ self model perform:setSelectionSelector with: sel ] >>> >>> This could be solved like bellow, though I'm not sure it is the best >>> solution. >>> If I put a halt in PluggableTextMorph >>inspectIt and hit proceed the >>> the selection is inspected correctly, without this modification. >>> >>> PluggableTextMorph>>selectionInterval: sel >>> selectionInterval := sel. >>> setSelectionSelector >>> ifNotNil: [ self model perform:setSelectionSelector with: sel ] >>> >>> >>> >>> >>> >>> On Fri, Dec 27, 2013 at 3:11 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: >>> >>>> >>>> On 27 Dec 2013, at 13:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>> wrote: >>>> >>>> > Hi guys >>>> > >>>> > we should not let the system in such state. We cannot inspect print >>>> expression in the debugger. >>>> > Does anybody have an idea of the change that broke it? >>>> > >>>> Yes: >>>> >>>> https://pharo.fogbugz.com/f/cases/12144/TextModel-getSelection >>>> >>>> it was added in 655, so for reverting the easiest is to dl 654, do a >>>> merge and look at all the changes >>>> (there are just 4-5 that are not re-catorizations). >>>> >>>> This is on my TODO nextâ¦ >>>> >>>> Marcus >>>> >>>> >>>> >>> >>> >> >> > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 27, 2013

Re: [Pharo-dev] [Seaside-dev] [Seaside] [ANN] Seaside 3.1 and 3.0.10 release

by Sven Van Caekenberghe

On 27 Dec 2013, at 11:57, Philippe Marschall <philippe.marschall(a)gmail.com> wrote: > We are pleased to announce the releases of Seaside 3.1 and 3.0.10. That is great news. Congratulations and thank you to the whole team. > Seaside 3.1 is a feature release and contains a range of improvements > and fixes from a variety of people. Seaside 3.0.10 is a minor release > of Seaside 3.0 containing only a single bug fix. > > The changes can be view here: > http://code.google.com/p/seaside/wiki/Seaside310Changelog and here: > http://code.google.com/p/seaside/wiki/Seaside3010Changelog > > A one-click image is available here: > http://www.seaside.st/distributions/Seaside-3.1-OneClick.zip and here: > http://www.seaside.st/distributions/Seaside-3.0.10-OneClick.zip > Mavericks user beware the one click images are not signed. Itâs a pity those are still based on Pharo 1.3, which is becoming quite old now. > Seaside's Metacello configuration has been updated, so Seaside 3.1 can > be loaded into Pharo with: > > Gofer new > url:'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; > package: 'ConfigurationOfSeaside3'; > load. > ((Smalltalk at: #ConfigurationOfSeaside3) project version: #stable) load. Images of Pharo 2.0 or 3.0 with Seaside preloaded can be found here: https://ci.inria.fr/pharo-contribution/job/Seaside/ Sven > For more control over what gets loaded check out the class comment of > ConfigurationOfSeaside3 that lists the supported groups. > > We would like to thank everybody who contributed to these releases. > > The Seaside Team > _______________________________________________ > seaside-dev mailing list > seaside-dev(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Dec. 27, 2013