September 2013 - Pharo-dev - lists.pharo.org

[update 3.0] #30428

by Marcus Denker

Sept. 29, 2013

Re: [Pharo-dev] XMLParser & PharoExtras, XMLWriter, XPath: status?

by HernÃ¡n Morales Durand

El 28/09/2013 14:38, phil(a)highoctane.be escribiÃ³: > In the Pharo 20 image, I see that we do have XMLParser, XMLPullParser, > XMLWriter and XPath listed in the configuration (new install with > ZeroConf). > > I am also using Soup. > > That's because I am working on some OpenData and screen scraping work > and wondered what was okay to use. > > Is Soup depending on these? (I have XMLReader and Writer in my image but > don't know from where at the moment - but there are no tests, so only > something like #Core was loaded. > > Also what is different between XMLParser and XMLPullParser? > http://pharo.gemtalksystems.com/pier/book/LanguageAndLibraries/XML/XML-supp… > TIA > Phil

Sept. 28, 2013

Notes of our monthly iteration analysis

by StÃ©phane Ducasse

27 September 2013 TODO ---- - New debugger glitches / enhancements => need to merge with GSOC - OPAL methods withoutsource stalled - Metacello 2 not integrated integrated as soon as a BuilderCI is working Still issues in 30. should be Integrated in this release => change required to remove dependency to OSProcess - TxModel - refactoring immutable position selection - need to discuss camille model - visual is working - scrolling should be added - page up down should be added - morph widget - finish - Rubric - CI on linux is broken - Memory consumption backport 2.0 - Spec review - VM acceptance tests - fixed version of Moose - NewList Widget little glitches - NewSpec interpreter two days of work should be integrated in this iteration - Kill Package Info - Rpackage iteration under way - SmalltalkHub (in the next version) - Diff to the mailing-list (nicolas) - Inbox for projects - ControlKey on linux - nick will discuss with guille - Monkey - NativeBoost with new ASMJit version - NativeBoost on PharoS - Web site Progress is down - New look in feel - November - SystemEvents (may be) - Display VM Guile and Esteban are killing globals DONE ---- - FileTree integrated - New Inspector Glitch - Unloading the Old compiler - Memory consumption, weak announcements - insetBy: margin Pharo Workshop -------------- observer patterns trigger and announcement supports on:send:to: vs. dependent => and announcement are costly when no state. => probably the solution would be to use trigger: remove object>>changed: and dependentFields keep announcement for larger case. literal object syntax Morph>>on:send:to: Morph>>on:do: inconsistency on:do: for announcement is not nice for announcement may be we should have onAnnoucement: do:

Sept. 28, 2013

Re: [Pharo-dev] XMLParser & PharoExtras, XMLWriter, XPath: status?

by StÃ©phane Ducasse

Yes soup is using XMLReader. Have a look on PharoExtras/Soup Stef On Sep 28, 2013, at 7:38 PM, phil(a)highoctane.be wrote: > In the Pharo 20 image, I see that we do have XMLParser, XMLPullParser, XMLWriter and XPath listed in the configuration (new install with ZeroConf). > > I am also using Soup. > > That's because I am working on some OpenData and screen scraping work and wondered what was okay to use. > > Is Soup depending on these? (I have XMLReader and Writer in my image but don't know from where at the moment - but there are no tests, so only something like #Core was loaded. > > Also what is different between XMLParser and XMLPullParser? > > TIA > Phil

Sept. 28, 2013

Re: [Pharo-dev] XMLParser & PharoExtras, XMLWriter, XPath: status?

by StÃ©phane Ducasse

I migrated soup to smalltalkhub too have and normally it should loads well in 20 and 30. And all the soup subprojects have been migrated (by me) to smalltalkhub. Stef On Sep 28, 2013, at 7:38 PM, phil(a)highoctane.be wrote: > In the Pharo 20 image, I see that we do have XMLParser, XMLPullParser, XMLWriter and XPath listed in the configuration (new install with ZeroConf). > > I am also using Soup. > > That's because I am working on some OpenData and screen scraping work and wondered what was okay to use. > > Is Soup depending on these? (I have XMLReader and Writer in my image but don't know from where at the moment - but there are no tests, so only something like #Core was loaded. > > Also what is different between XMLParser and XMLPullParser? > > TIA > Phil

Sept. 28, 2013

Re: [Pharo-dev] XML...

by StÃ©phane Ducasse

I migrated everything to smalltalkhub. So this use is wrong :) Stef > After having an extra look, there is a ConfigurationOfXMLSupport in my image (coming from Seaside 3) which reads: > > baseline120: spec > <version: '1.2.0-baseline'> > spec > for: #common > do: [ > spec > blessing: #baseline; > repository: 'http://www.squeaksource.com/XMLSupport'. > spec > project: 'XML-Writer' > with: [ > spec > className: 'ConfigurationOfXMLWriter'; > repository: 'http://www.squeaksource.com/XMLWriter' ]; > package: 'Collections-OrderPreservingDictionary' > with: [ spec repository: 'http://www.squeaksource.com/OrderPreservingDict' ]; > package: 'Collections-BitmapCharacterSet' > with: [ spec repository: 'http://www.squeaksource.com/BitmapCharacterSet' ]; > package: 'XML-Parser' > with: [ spec requires: #('XML-Writer' 'Collections-OrderPreservingDictionary' 'Collections-BitmapCharacterSet') ]; > package: 'XML-Tests-Parser' > with: [ spec requires: 'XML-Parser' ]. > spec > package: 'Opax' > with: [ > spec > repository: 'http://www.squeaksource.com/OPAX'; > requires: 'XML-Parser' ]. > spec > group: 'default' with: #('Core'); > group: 'Core' with: #('XML-Parser'); > group: 'Tests' with: #('XML-Tests-Parser') ]. > spec > for: #squeakcommon > do: [ > spec > package: 'Pastell' > with: [ > spec > requires: #('XML-Parser'); > repository: 'http://www.squeaksource.com/Pastell' ] ]. > spec > for: #gemstone > do: [ > spec repository: 'http://seaside.gemstone.com/ss/XMLSupport'. > spec > project: 'Grease Core' > with: [ > spec > className: 'ConfigurationOfGrease'; > versionString: '1.0.3-baseline'; > loads: #('Core'); > repository: 'http://www.squeaksource.com/MetacelloRepository' ]. > spec > package: 'Collections-OrderPreservingDictionary' > with: [ > spec > file: 'Collections-OrderPreservingDictionary.g'; > repository: 'http://seaside.gemstone.com/ss/PharoCompat']. > spec package: 'SIXX' with: [ > spec > requires: #('XML-Parser' 'Grease Core'); > repository: 'http://seaside.gemstone.com/ss/SIXX']. > spec > package: 'XML-Observable'. > spec > package: 'XML-Parser' with: [ > spec > file: 'XML-Parser.g']. > spec > group: 'Core' with: #('XML-Observable'); > group: 'default' with: #('Core') ] > > And obviously picks things up from squeaksource... > > Damnit. > > Phil

Sept. 28, 2013

XML...

by phil＠highoctane.be

After having an extra look, there is a ConfigurationOfXMLSupport in my image (coming from Seaside 3) which reads: baseline120: spec <version: '1.2.0-baseline'> spec for: #common do: [ spec blessing: #baseline; repository: 'http://www.squeaksource.com/XMLSupport'. spec project: 'XML-Writer' with: [ spec className: 'ConfigurationOfXMLWriter'; repository: 'http://www.squeaksource.com/XMLWriter' ]; package: 'Collections-OrderPreservingDictionary' with: [ spec repository: 'http://www.squeaksource.com/OrderPreservingDict' ]; package: 'Collections-BitmapCharacterSet' with: [ spec repository: 'http://www.squeaksource.com/BitmapCharacterSet' ]; package: 'XML-Parser' with: [ spec requires: #('XML-Writer' 'Collections-OrderPreservingDictionary' 'Collections-BitmapCharacterSet') ]; package: 'XML-Tests-Parser' with: [ spec requires: 'XML-Parser' ]. spec package: 'Opax' with: [ spec repository: 'http://www.squeaksource.com/OPAX'; requires: 'XML-Parser' ]. spec group: 'default' with: #('Core'); group: 'Core' with: #('XML-Parser'); group: 'Tests' with: #('XML-Tests-Parser') ]. spec for: #squeakcommon do: [ spec package: 'Pastell' with: [ spec requires: #('XML-Parser'); repository: 'http://www.squeaksource.com/Pastell' ] ]. spec for: #gemstone do: [ spec repository: 'http://seaside.gemstone.com/ss/XMLSupport'. spec project: 'Grease Core' with: [ spec className: 'ConfigurationOfGrease'; versionString: '1.0.3-baseline'; loads: #('Core'); repository: 'http://www.squeaksource.com/MetacelloRepository' ]. spec package: 'Collections-OrderPreservingDictionary' with: [ spec file: 'Collections-OrderPreservingDictionary.g'; repository: 'http://seaside.gemstone.com/ss/PharoCompat']. spec package: 'SIXX' with: [ spec requires: #('XML-Parser' 'Grease Core'); repository: 'http://seaside.gemstone.com/ss/SIXX']. spec package: 'XML-Observable'. spec package: 'XML-Parser' with: [ spec file: 'XML-Parser.g']. spec group: 'Core' with: #('XML-Observable'); group: 'default' with: #('Core') ] And obviously picks things up from squeaksource... Damnit. Phil

Sept. 28, 2013

XMLParser & PharoExtras, XMLWriter, XPath: status?

by phil＠highoctane.be

In the Pharo 20 image, I see that we do have XMLParser, XMLPullParser, XMLWriter and XPath listed in the configuration (new install with ZeroConf). I am also using Soup. That's because I am working on some OpenData and screen scraping work and wondered what was okay to use. Is Soup depending on these? (I have XMLReader and Writer in my image but don't know from where at the moment - but there are no tests, so only something like #Core was loaded. Also what is different between XMLParser and XMLPullParser? TIA Phil

Sept. 28, 2013

Re: [Pharo-dev] Pharo3Inbox contributor request

by StÃ©phane Ducasse

> done, > happy contributing ;) welcome ben Stef > > On 2013-09-28, at 12:52, Ben Coman <btc(a)openInWorld.com> wrote: > >> I've recently been getting used to FogBugz and am now familiarizing myself with the Pharo 3 bug fix process. This is nicely described in a video by Camillo [1]. For practice I've logged a simple issue for a spelling correction [2]. To complete this, could SmalltalkHub user 'BenComan' be added to Pharo3Inbox. >> >> cheers -ben >> >> [1] http://vimeo.com/75183993 >> [2] https://pharo.fogbugz.com/f/cases/edit/11702/spelling-error-transferred >> >> >> >> >

Sept. 28, 2013

Re: [Pharo-dev] Pharo3Inbox contributor request

by Camillo Bruni

done, happy contributing ;) On 2013-09-28, at 12:52, Ben Coman <btc(a)openInWorld.com> wrote: > I've recently been getting used to FogBugz and am now familiarizing myself with the Pharo 3 bug fix process. This is nicely described in a video by Camillo [1]. For practice I've logged a simple issue for a spelling correction [2]. To complete this, could SmalltalkHub user 'BenComan' be added to Pharo3Inbox. > > cheers -ben > > [1] http://vimeo.com/75183993 > [2] https://pharo.fogbugz.com/f/cases/edit/11702/spelling-error-transferred > > > >

Sept. 28, 2013