- Pharo-dev - lists.pharo.org

Re: [Pharo-project] 1.2 Dev and Hudson

by Marcus Denker

On Dec 20, 2010, at 9:41 AM, Marcus Denker wrote: > > On Dec 20, 2010, at 9:31 AM, Mariano Martinez Peck wrote: > >> Yes, as Guille said, using #lastVersion would be more interesting here: >> >> "Dev image" >> Gofer new >> squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfPharo'; >> load. >> >> ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: #silently: with: true; perform: #load. >> > > I will put that in. Done. next build will use that. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Dec. 20, 2010

Re: [Pharo-project] 1.2 Dev and Hudson

by Marcus Denker

On Dec 20, 2010, at 9:31 AM, Mariano Martinez Peck wrote: > Yes, as Guille said, using #lastVersion would be more interesting here: > > "Dev image" > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfPharo'; > load. > > ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: #silently: with: true; perform: #load. > I will put that in. > > And even more, what about loading the baseline directly? > It would be nice if we could load whatever so that if someone commits a bug-fix, the build server picks that up on the next load :-) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Dec. 20, 2010

Re: [Pharo-project] 1.2 Dev and Hudson

by Mariano Martinez Peck

Yes, as Guille said, using #lastVersion would be more interesting here: "Dev image" Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. ((Smalltalk at: #ConfigurationOfPharo) project lastVersion) perform: #silently: with: true; perform: #load. And even more, what about loading the baseline directly? cheers mariano On Mon, Dec 20, 2010 at 8:45 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Dec 20, 2010, at 4:21 AM, Guillermo Polito wrote: > > Marcus, > > How are we building 1.2 dev? Is it using always the last version of the > ConfigurationOfPharo? If not, how can we do it? :) > > > It does > > "Dev image" > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfPharo'; > load. > > ((Smalltalk at: #ConfigurationOfPharo) project version: '1.2-beta2') > perform: #silently: with: true; perform: #load. > > > So yes, right now we need to change the build script as soon as the version > changes. > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

Dec. 20, 2010

Re: [Pharo-project] Printing hexadecimal values of a string

by Levente Uzonyi

On Mon, 20 Dec 2010, StÃ©phane Ducasse wrote: > > > On Dec 19, 2010, at 9:55 PM, Geoffroy Couprie wrote: > >> Hello all, >> >> I get a strange behaviour while trying to print hexadecimal values of a string. >> >> Context: I get a SHA1 hash from a binary stream, store it into a >> string, and I want to display that string (using asHex). >> >> Problem: for values inferior to 16, the leading zero is ignored. (15 >> -> 'F' instead of '0F'). > > indeed printStringHex prints F instead of 0F > 15 printStringHex > 'F' > 15 hex > '16rF' > > Geoffroy could you add a variant that produces the correct behavior with some tests? No need to do that. As Sven pointed out, he can simply use ByteArray >> #hex. Since his stream is already binary, he can also avoid converting his data to a string. Levente > >> I could modify SmallInteger>>printStringBase: to always include the >> leading zero, but I fear I'm going to break a lot of code doing that. >> Is there a better way to fix my problem? apart from using directly the >> following: >> aStream do:[:val | val printStringBase:16 nDigits:2] >> >> Best regards, >> >> Geoffroy >> > > >

Dec. 20, 2010

Re: [Pharo-project] [Pharo-users] serial driver

by StÃ©phane Ducasse

what I know is that serge fixed the named ports but the code could be better. Stef On Dec 20, 2010, at 9:04 AM, Torsten Bergmann wrote: > Maybe > > http://news.squeak.org/2006/10/23/serial-port-howto/ > > Bye > T. > -- > GRATIS! Movie-FLAT mit Ã¼ber 300 Videos. > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome >

Dec. 20, 2010

Re: [Pharo-project] short circuit or redirecting selectors

by StÃ©phane Ducasse

On Dec 20, 2010, at 3:46 AM, Elliot Finley wrote: > Hello, > > If I have an object with accessors #firstName, #lastName and #age, how would I short shirt circuit or replace these selectors? In other words, how would I modify an object after it's already been created? Hello there are plenty of ways to do that but I think that this is not what you want to do. Tell us what you are trying to achieve? Did you read smalltalk by example from my web page? There is a chapter on object creation and instantiation. Stef > > Thanks, > Elliot >

Dec. 20, 2010

Re: [Pharo-project] Printing hexadecimal values of a string

by StÃ©phane Ducasse

max on which class do you define it? do you have some tests? Stef On Dec 19, 2010, at 11:40 PM, Max Leske wrote: > I know how your feel. My code: > > hexHashFrom: aByteString > "#hex will omit a leading 0. If that's the case insert leading 0." > ^aByteString asByteArray hex asLowercase forceTo: 40 paddingStartWith: $0 > > Max > > > On 19.12.2010, at 22:54, Sven Van Caekenberghe wrote: > >> Hi Geoffroy, >> >> On 19 Dec 2010, at 21:55, Geoffroy Couprie wrote: >> >>> Hello all, >>> >>> I get a strange behaviour while trying to print hexadecimal values of a string. >>> >>> Context: I get a SHA1 hash from a binary stream, store it into a >>> string, and I want to display that string (using asHex). >>> >>> Problem: for values inferior to 16, the leading zero is ignored. (15 >>> -> 'F' instead of '0F'). >>> >>> I could modify SmallInteger>>printStringBase: to always include the >>> leading zero, but I fear I'm going to break a lot of code doing that. >>> Is there a better way to fix my problem? apart from using directly the >>> following: >>> aStream do:[:val | val printStringBase:16 nDigits:2] >>> >>> Best regards, >>> >>> Geoffroy >> >> Why would you not use the ByteArray>>#hex method ? >> >> #(0 1 2 253 254 255) asByteArray hex >> >> '000102fdfeff' >> >> Sven >> >> > >

Dec. 20, 2010

Re: [Pharo-project] Printing hexadecimal values of a string

by StÃ©phane Ducasse

On Dec 19, 2010, at 9:55 PM, Geoffroy Couprie wrote: > Hello all, > > I get a strange behaviour while trying to print hexadecimal values of a string. > > Context: I get a SHA1 hash from a binary stream, store it into a > string, and I want to display that string (using asHex). > > Problem: for values inferior to 16, the leading zero is ignored. (15 > -> 'F' instead of '0F'). indeed printStringHex prints F instead of 0F 15 printStringHex 'F' 15 hex '16rF' Geoffroy could you add a variant that produces the correct behavior with some tests? > I could modify SmallInteger>>printStringBase: to always include the > leading zero, but I fear I'm going to break a lot of code doing that. > Is there a better way to fix my problem? apart from using directly the > following: > aStream do:[:val | val printStringBase:16 nDigits:2] > > Best regards, > > Geoffroy >

Dec. 20, 2010

[Pharo-project] [Pharo-users] serial driver

by Torsten Bergmann

Maybe http://news.squeak.org/2006/10/23/serial-port-howto/ Bye T. -- GRATIS! Movie-FLAT mit Ã¼ber 300 Videos. Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome

Dec. 20, 2010

Re: [Pharo-project] [Metacello] circling in on symbolic version release (1.0-beta.28)

by StÃ©phane Ducasse

On Dec 19, 2010, at 11:39 PM, Mariano Martinez Peck wrote: > Hi dale. This is awesome. SOrry for being quite out...but I am trying to focus on my duties :( > > maybe we will be able to build pharo dev 1.2 using symbolic versions? yes it would be good. > > cheers > > Mariano > > > On Fri, Dec 17, 2010 at 12:58 AM, Dale <dhenrich(a)vmware.com> wrote: > I've just done a series of checkins of the configurations referenced > from the Pharo development configuration. > > I've updated each of the configurations with the "correct symbolic > version" for Pharo1.0 and Pharo1.1 based upon what is loaded in the > one-click images and the ConfigurationOfPharo specifications ... when > in doubt I went with the specified version. > > Here's the list of configs: > > ProfStef > Shout > AutomaticMethodCategorizer > ObjectMetaTools > Nile > PharoMorphicExtras > NewInspector > OCompletion > PharoSound > ScriptManager > HelpSystem > OmniBrowser > RefactoringBrowser > PharoNonCore > Gofer > > The symbolic version methods are ignored by earlier versions of > Metacello, so they shouldn't affect anything ... > > I plan to perform validations on all of the configurations in > MetacelloRepository and will be checking in fixes for the critical > issues that can affect Metacello (there are some issues with the most > recent version of Pharo that I will fix shortly). > > Dale > >

Dec. 20, 2010