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

Re: [Pharo-project] Mac App Store opens January 6

by Eliot Miranda

So we should be ready to provide Squeak, Pharo, Etoys et al on the Mac App Store on 6/1/2011. John, any advice or should I just go ahead and submit Cog and Squeak 4.1 trunk and see what happens? Other cautions suggestions anybody? best Eliot On Thu, Dec 16, 2010 at 11:21 AM, Apple Developer < noreply-appledev(a)apple.com> wrote: > [image: Apple Developer] > <http://insideapple.apple.com/redir/cbx-cgi.do?v=2&la=en&lc=us&a=xU17znNqOlP…> [image: > .] > We are thrilled to announce that on January 6 the Mac App Store will open > to millions of users around the world. By bringing the revolutionary App > Store experience to Mac OS X, the Mac App Store makes discovering, > purchasing, and downloading Mac apps easier than ever, and provides you with > the best place to distribute your Mac apps. > *Submit Your Mac Apps by December 31* > Be a part of the grand opening of the Mac App Store and take advantage of > this exciting opportunity to reach new customers. Build, test, and compile > your apps with Xcode 3.2.5, then submit them for review no later than > Friday, December 31 at 5 PM PST. > As a reminder, iTunes Connect will be shutdown from December 23 - 28. > During this time you will not be able to submit apps to the App Store. > [image: Log in now]<http://insideapple.apple.com/redir/cbx-cgi.do?v=2&la=en&lc=us&a=xU17znNqOlP…> > [image: .] > TM and copyright Â© 2010 Apple Inc. 1 Infinite Loop, MS 83-DM, Cupertino, > CA 95014. > All Rights Reserved <http://www.apple.com/legal/default.html> / Keep > Informed <http://www.apple.com/enews/subscribe/> / Privacy Policy<http://www.apple.com/legal/privacy/>/ My > Info <https://myinfo.apple.com/cgi-bin/WebObjects/MyInfo> > You are receiving this email because you are a Mac Developer Program > member who is opted-in to receive marketing or technical information. If you > would prefer not to receive future communications from Apple Developer you > may unsubscribe<http://developer.apple.com/unsubscribe/?email=eliot.miranda@gmail.com> > . > [image: 0] >

Dec. 16, 2010

Re: [Pharo-project] [Hudson] 1.2 build

by Marcus Denker

On Dec 16, 2010, at 7:17 PM, Marcus Denker wrote: > > On Dec 16, 2010, at 7:06 PM, Schwab,Wilhelm K wrote: > >> Is the server building 1.1 or 1.1.1? > > 1.1.1 > > But I don't want to have that in the name of the Build Target, as this then would need to be renamed for 1.1.2 > (and doing such point releases now has virtualy an overhead of 0, I should add). > The .zip should have an un-changing name for 1.1, too, so people can just download and get the latest *even* if we do a 1.1.2. But *inside* the zip, I would like to have more infos... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Dec. 16, 2010

Re: [Pharo-project] [Hudson] 1.2 build

by Marcus Denker

On Dec 16, 2010, at 7:06 PM, Schwab,Wilhelm K wrote: > Is the server building 1.1 or 1.1.1? 1.1.1 But I don't want to have that in the name of the Build Target, as this then would need to be renamed for 1.1.2 (and doing such point releases now has virtualy an overhead of 0, I should add). This will be better as soon as we add the version and update number as Adrian suggested. > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Marcus Denker [marcus.denker(a)inria.fr] > Sent: Thursday, December 16, 2010 12:55 PM > To: Pharo-project(a)lists.gforge.inria.fr > Cc: Moose-dev Moose Dev > Subject: Re: [Pharo-project] [Hudson] 1.2 build > > On Dec 16, 2010, at 5:26 PM, Tudor Girba wrote: > >> Great news! >> >> I already updated the Moose build to be based on the current 1.2: >> http://hudson.moosetechnology.org/job/moose-latest-dev-on-pharo-1.2/lastSuc… >> >> >> Maybe one suggestion: it would be good to name the image as pharo-1.2-dev, rather than just dev1.2. > > Ok, I will do that. In addition, it would be nice if the zip would contain inside some version number or date or something. > > Marcus > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Dec. 16, 2010

Re: [Pharo-project] [Hudson] 1.2 build

by Schwab,Wilhelm K

Is the server building 1.1 or 1.1.1? ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Marcus Denker [marcus.denker(a)inria.fr] Sent: Thursday, December 16, 2010 12:55 PM To: Pharo-project(a)lists.gforge.inria.fr Cc: Moose-dev Moose Dev Subject: Re: [Pharo-project] [Hudson] 1.2 build On Dec 16, 2010, at 5:26 PM, Tudor Girba wrote: > Great news! > > I already updated the Moose build to be based on the current 1.2: > http://hudson.moosetechnology.org/job/moose-latest-dev-on-pharo-1.2/lastSuc… > > > Maybe one suggestion: it would be good to name the image as pharo-1.2-dev, rather than just dev1.2. Ok, I will do that. In addition, it would be nice if the zip would contain inside some version number or date or something. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Dec. 16, 2010

Re: [Pharo-project] [Hudson] 1.2 build

by Marcus Denker

On Dec 16, 2010, at 5:26 PM, Tudor Girba wrote: > Great news! > > I already updated the Moose build to be based on the current 1.2: > http://hudson.moosetechnology.org/job/moose-latest-dev-on-pharo-1.2/lastSuc… > > > Maybe one suggestion: it would be good to name the image as pharo-1.2-dev, rather than just dev1.2. Ok, I will do that. In addition, it would be nice if the zip would contain inside some version number or date or something. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Dec. 16, 2010

Re: [Pharo-project] [Hudson] 1.2 build

by Igor Stasenko

On 16 December 2010 17:25, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Great news! > > I already updated the Moose build to be based on the current 1.2: > http://hudson.moosetechnology.org/job/moose-latest-dev-on-pharo-1.2/lastSuc… > > > Maybe one suggestion: it would be good to name the image as pharo-1.2-dev, rather than just dev1.2. > +1 > Cheers, > Doru > > > On 16 Dec 2010, at 12:11, Marcus Denker wrote: > >> Hi, >> >> Â Â Â - the pharo 1.2 (and 1.1) full builds are now triggered by a successful build of the core images (failing tests are ok, failing builds do not trigger) >> Â Â Â - One-Click of full is now build automatically: >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/20/artifact/PharoOne… >> Â Â Â - just image and sources are available at this link https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/… >> Â Â Â - tests are now run on 1.2 full. 24 are failing, of which 12 are from core: >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/t… >> >> >> Next step: >> >> Â Â Â - re-use the core images in the full image builds, do not update again. (saves 5 minutes build time) >> >> Later: >> Â Â Â - build all VMs from source automatically >> Â Â Â - run tests on MacOS and Windows in addition to linux (to validate the VM and to check that image side is working on all plattforms) >> >> >> >> -- >> Marcus Denker Â -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> > > -- > www.tudorgirba.com > > "Speaking louder won't make the point worthier." > > > -- Best regards, Igor Stasenko AKA sig.

Dec. 16, 2010

Re: [Pharo-project] WSDL, SOAP(HTTP) and XSD Schema (was Transforming WSDL in a local model)

by CÃ©drick BÃ©ler

> >> (2) the typing system is not implemented (I have a naive object wrapper on them - XSDSimpleType and XSDComplexType + XSDRestriction). >> - I gave a look at Brenda Larcom implementation of XSD (X Files project on squeaksource - it's MIT even if not specified yet) >> - I think I need a (clever) way to link XSDSimpleType/XSDComplexType with both my "wsdl" model and the soap implementation and of course map them back and forth with Smalltalk classes. > > > >>>> Any comments/idea here would be greatly appreciated ;-) - The "typing system" seems really important to me in term of interoperability with the outside world, but I'd like a clever way to have them mapped to smalltalk class/objects > > What do you need exactly do you have an example? > There are several datatypes systems, but in xml world, xml schema seems to be the norm. I'd like to map them back and forth to smalltalk. <naiveThought>would it be possible to make magritte xml schema compliant ?</naiveThought > - There are a list of simple types (see here for an overview - http://books.xmlschemata.org/relaxng/relax-CHP-19.html) [1]. - There is also the notion of restriction/facets that apply to type instance [2]. - Then there are complex type for Arrays, Structure likes, etc... - And last, there are encoded types (for whatever cannot be easily represented I guess) ******** To give an idea, here is what's done in SOAPOpera and some references at the end: ***For simple types (use of a typeDict): -- simpleTypes [#Boolean] : 'xsd:boolean' [#ByteString] : 'xsd:string' [#Double] : 'xsd:double' [#Float] : 'xsd:float' [#Integer] : 'xsd:integer' [#LargeNegativeInteger] : 'xsd:negativeInteger' [#LargePositiveInteger] : 'xsd:positiveInteger' [#SmallInteger] : 'xsd:integer' [#String] : 'xsd:string' ... ***For complexTypes there's a complexType dict that is populated by the encoder ***For encoded (during encoding, if the type is not defined, it's encoded): self typeDict at: type ifAbsent:[ ^self encodeObjectSoapVariable: aSoapVariable]. with for instance self encodeObjectSoapVariable: aSoapVariable = | <auau xsi:type="Squeak-ENC:ReferenceStream">CAAAAAQEAAAAAQQAAAACCAAAAAIGBWhlbGxvEQlTbWFsbHRhbGsEAAAAAw==</auau> **************************** In SoapEncoder 's (with Masashi Umezawa comments - :-) ) initTypeDict "Apparently this mapping is not so sophisticted. " "##TODO: Implement more serious mapping method " | pref | typeDict := super initTypeDict. pref := SoapConstants xsdPrefixColon. #( #(#double #Float) #(#decimal #ScaledDecimal) #(#base64Binary #ByteArray) #(#long #LargePositiveInteger) #(#dateTime #DateAndTime) ) do:[:each | typeDict at: (pref, each first) asSymbol put: each last]. "for Poor Squeak!" ^typeDict *********************References (w3c) http://www.w3.org/TR/xmlschema-2/#built-in-datatypes http://www.w3.org/TR/xmlschema-2/#dt-facet Facets Fundamental Facets (http://www.w3.org/TR/xmlschema-2/#rf-fund-facets) 4.2.1 equal 4.2.2 ordered 4.2.3 bounded 4.2.4 cardinality 4.2.5 numeric Constraining Facets (http://www.w3.org/TR/xmlschema-2/#rf-facets) 4.3.1 length 4.3.2 minLength 4.3.3 maxLength 4.3.4 pattern 4.3.5 enumeration 4.3.6 whiteSpace 4.3.7 maxInclusive 4.3.8 maxExclusive 4.3.9 minExclusive 4.3.10 minInclusive 4.3.11 totalDigits 4.3.12 fractionDigits {base type definition} applicable {facets} If {variety} is list, then [all datatypes] length, minLength, maxLength, pattern, enumeration, whiteSpace If {variety} is union, then [all datatypes] pattern, enumeration else if {variety} is atomic, then string length, minLength, maxLength, pattern, enumeration, whiteSpace boolean pattern, whiteSpace float pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive double pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive decimal totalDigits, fractionDigits, pattern, whiteSpace, enumeration, maxInclusive, maxExclusive, minInclusive,minExclusive duration pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive dateTime pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive time pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive date pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive gYearMonth pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive gYear pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive gMonthDay pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive gDay pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive gMonth pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive hexBinary length, minLength, maxLength, pattern, enumeration, whiteSpace base64Binary length, minLength, maxLength, pattern, enumeration, whiteSpace anyURI length, minLength, maxLength, pattern, enumeration, whiteSpace QName length, minLength, maxLength, pattern, enumeration, whiteSpace NOTATION length, minLength, maxLength, pattern, enumeration, whiteSpace

Dec. 16, 2010

Re: [Pharo-project] [Hudson] 1.2 build

by Tudor Girba

Great news! I already updated the Moose build to be based on the current 1.2: http://hudson.moosetechnology.org/job/moose-latest-dev-on-pharo-1.2/lastSuc… Maybe one suggestion: it would be good to name the image as pharo-1.2-dev, rather than just dev1.2. Cheers, Doru On 16 Dec 2010, at 12:11, Marcus Denker wrote: > Hi, > > - the pharo 1.2 (and 1.1) full builds are now triggered by a successful build of the core images (failing tests are ok, failing builds do not trigger) > - One-Click of full is now build automatically: > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/20/artifact/PharoOne… > - just image and sources are available at this link https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/… > - tests are now run on 1.2 full. 24 are failing, of which 12 are from core: > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastCompletedBuild/t… > > > Next step: > > - re-use the core images in the full image builds, do not update again. (saves 5 minutes build time) > > Later: > - build all VMs from source automatically > - run tests on MacOS and Windows in addition to linux (to validate the VM and to check that image side is working on all plattforms) > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- www.tudorgirba.com "Speaking louder won't make the point worthier."

Dec. 16, 2010

Re: [Pharo-project] Issue 3441 in pharo: Tests for Polymorph

by pharo＠googlecode.com

Comment #1 on issue 3441 by gazzaguru2: Tests for Polymorph http://code.google.com/p/pharo/issues/detail?id=3441 Some tests for KeyedTree that we had attached... Attachments: KeyedTreeTest.st 7.3 KB

Dec. 16, 2010

Re: [Pharo-project] Issue 3421 in pharo: Calls to deprecated methods break build

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3421 by marcus.denker: Calls to deprecated methods break build http://code.google.com/p/pharo/issues/detail?id=3421 fixed

Dec. 16, 2010