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

Re: [Pharo-project] SqueaSource is Down

by Mariano Martinez Peck

seems to be back, thanks On Fri, May 13, 2011 at 10:15 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > It will change soon. > > What we could do is to use the gemstone based squeaksource running at > gemstone > but I'm sure that if we invade it people will be happy. > > Stef > > > ... and they changed the passwd so I can not do anything. > > > > I feel very unprofessional now. > > > > -- > > Marcus Denker -- http://www.marcusdenker.de > > INRIA Lille -- Nord Europe. Team RMoD. > > > > > > > -- Mariano http://marianopeck.wordpress.com

May 13, 2011

Re: [Pharo-project] SqueaSource is Down

by StÃ©phane Ducasse

It will change soon. What we could do is to use the gemstone based squeaksource running at gemstone but I'm sure that if we invade it people will be happy. Stef > ... and they changed the passwd so I can not do anything. > > I feel very unprofessional now. > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

May 13, 2011

Re: [Pharo-project] SqueaSource is Down

by Fabrizio Perin

Yes is down at will stay down until i will not find the files committed with a fancy name. Squeaksource doesn't support strange character in the file names like Japanese or Cyrillic characters. 2011/5/13 Marcus Denker <marcus.denker(a)inria.fr> > ... and they changed the passwd so I can not do anything. > > I feel very unprofessional now. > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > >

May 13, 2011

[Pharo-project] SqueaSource is Down

by Marcus Denker

... and they changed the passwd so I can not do anything. I feel very unprofessional now. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

May 13, 2011

Re: [Pharo-project] Help "migrating" from classic streams to XStreams

by Nicolas Cellier

And concerning nextNumber nextString etc... this supposes a certain format, we can't guess. If you have a DSL for your data with known grammar, you could try a PEG parser. Otherwise, if your data are in a classical Smalltalk format in ASCII, you could use Number readFrom: yourXTCompatibilityReadStream. Otherwise if you have a specific binary encoded data, it's up to you... Nicolas 2011/5/13 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > Of course, another way is simply to define a > *XTream-classic-API-compatibility in upper level XTReadStream, but > that's less fun :) > > Nicolas > > 2011/5/13 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >> Don't do it exclusively for file, but do it for every XTream >> One way to do it would be with a wrapper. >> I mean create a new subclass of XTReadStream, say >> XTCompatibilityReadStream Â implement the compatibility methods you >> want. >> Same for WriteStream. >> You'll have to define a few XTream messages too that delegates to the >> source/destination >> >> blah >> Â Â ^source blah >> >> foo >> Â Â ^destination foo >> >> >> Then define something like >> >> XTReadStream>>classicalStreamAPI >> Â Â ^XTCompatibilityReadStream on: self >> >> My 2c. >> >> Nicolas >> >> 2011/5/13 Mariano Martinez Peck <marianopeck(a)gmail.com>: >>> Hi guys. We are developing Fuel with Martin Dias. Fuel is a binary >>> serializer similar to Parcels. More info in >>> http://rmod.lille.inria.fr/web/pier/software/Fuel >>> >>> For the moment, we are using the "classic" streams we want to give it a try >>> to XStreams. My knowledge on streams is very little, so if someone can give >>> me a hint I would really appreciate it. >>> What I want to do right now is an adaptor of XStreams to classic stream. I >>> mean, I want to create custom subclasses of XTFileWriteStream and >>> XTFileReadStream that implements the same API from classic streams that we >>> use in Fuel. And the implementations of such methods will do just a "self >>> something" where something is the way of doing that in XStreams. >>> >>> So, the following is the protocol we use in Fuel for streams, and what I >>> would love to know is the associated way to do it it XStreams. The left is >>> classic streams, and after the "->" it is XStreams: >>> >>> Reading: >>> >>> nextNumber: -> ?? >>> nextPutAll: -> write: >>> nextStringPut: -> ?? >>> nextPut:Â -> put: >>> nextNumber:put: -> ?? >>> nextWordPut: -> ?? >>> >>> Writing: >>> >>> nextNumber: -> ?? >>> next:Â -> read: >>> nextString -> ?? >>> nextÂ -> get >>> nextWord -> ?? >>> >>> Thanks a lot in advance, >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >>> >> >

May 13, 2011

[Pharo-project] [COTDC] 64 - UrlArgumentList

by laurent laffont

Today: UrlArgumentList Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

May 13, 2011

Re: [Pharo-project] Help "migrating" from classic streams to XStreams

by Nicolas Cellier

Of course, another way is simply to define a *XTream-classic-API-compatibility in upper level XTReadStream, but that's less fun :) Nicolas 2011/5/13 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > Don't do it exclusively for file, but do it for every XTream > One way to do it would be with a wrapper. > I mean create a new subclass of XTReadStream, say > XTCompatibilityReadStream Â implement the compatibility methods you > want. > Same for WriteStream. > You'll have to define a few XTream messages too that delegates to the > source/destination > > blah > Â Â ^source blah > > foo > Â Â ^destination foo > > > Then define something like > > XTReadStream>>classicalStreamAPI > Â Â ^XTCompatibilityReadStream on: self > > My 2c. > > Nicolas > > 2011/5/13 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> Hi guys. We are developing Fuel with Martin Dias. Fuel is a binary >> serializer similar to Parcels. More info in >> http://rmod.lille.inria.fr/web/pier/software/Fuel >> >> For the moment, we are using the "classic" streams we want to give it a try >> to XStreams. My knowledge on streams is very little, so if someone can give >> me a hint I would really appreciate it. >> What I want to do right now is an adaptor of XStreams to classic stream. I >> mean, I want to create custom subclasses of XTFileWriteStream and >> XTFileReadStream that implements the same API from classic streams that we >> use in Fuel. And the implementations of such methods will do just a "self >> something" where something is the way of doing that in XStreams. >> >> So, the following is the protocol we use in Fuel for streams, and what I >> would love to know is the associated way to do it it XStreams. The left is >> classic streams, and after the "->" it is XStreams: >> >> Reading: >> >> nextNumber: -> ?? >> nextPutAll: -> write: >> nextStringPut: -> ?? >> nextPut:Â -> put: >> nextNumber:put: -> ?? >> nextWordPut: -> ?? >> >> Writing: >> >> nextNumber: -> ?? >> next:Â -> read: >> nextString -> ?? >> nextÂ -> get >> nextWord -> ?? >> >> Thanks a lot in advance, >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> >

May 13, 2011

Re: [Pharo-project] Need help with 1.3 Full Image

by laurent laffont

On Fri, May 13, 2011 at 9:13 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > > Thanks to push Marcus. > > Yes! > > > > What I'm thinking about is that it's a lot of energy to fix stuff about > things we don't know. I rarely succeed in fixing something new (but I learn > a little more every day :). > > > > I tried to organize a Pharo sprint over internet / IRC for Pharo 1.2 but > there was only Guillermo and me (cool indeed). But I continue to think it's > a good way to fusion energy and more fun to fix stuff together (not alone). > > > > Fixing bugs is a good way to learn, but easier with other people. So can > we have some virtual sprints over Skype or IRC ? > > yes this would be fun. > I think that we should have more virtual meeting to talk about key actions. > Another way is to create the "Fix Of The Day Contest", one day, one fix :) Laurent.

May 13, 2011

Re: [Pharo-project] [COTDC] 63 - MimeConverter

by laurent laffont

On Thu, May 12, 2011 at 8:40 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Today: MimeConverter > I'm the base class for converting some data from a MIME type to another. Subclasses should implement #mimeDecode and #mimeEncode. Laurent. > > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent >

May 13, 2011

Re: [Pharo-project] Help "migrating" from classic streams to XStreams

by Nicolas Cellier

Don't do it exclusively for file, but do it for every XTream One way to do it would be with a wrapper. I mean create a new subclass of XTReadStream, say XTCompatibilityReadStream implement the compatibility methods you want. Same for WriteStream. You'll have to define a few XTream messages too that delegates to the source/destination blah ^source blah foo ^destination foo Then define something like XTReadStream>>classicalStreamAPI ^XTCompatibilityReadStream on: self My 2c. Nicolas 2011/5/13 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi guys. We are developing Fuel with Martin Dias. Fuel is a binary > serializer similar to Parcels. More info in > http://rmod.lille.inria.fr/web/pier/software/Fuel > > For the moment, we are using the "classic" streams we want to give it a try > to XStreams. My knowledge on streams is very little, so if someone can give > me a hint I would really appreciate it. > What I want to do right now is an adaptor of XStreams to classic stream. I > mean, I want to create custom subclasses of XTFileWriteStream and > XTFileReadStream that implements the same API from classic streams that we > use in Fuel. And the implementations of such methods will do just a "self > something" where something is the way of doing that in XStreams. > > So, the following is the protocol we use in Fuel for streams, and what I > would love to know is the associated way to do it it XStreams. The left is > classic streams, and after the "->" it is XStreams: > > Reading: > > nextNumber: -> ?? > nextPutAll: -> write: > nextStringPut: -> ?? > nextPut:Â -> put: > nextNumber:put: -> ?? > nextWordPut: -> ?? > > Writing: > > nextNumber: -> ?? > next:Â -> read: > nextString -> ?? > nextÂ -> get > nextWord -> ?? > > Thanks a lot in advance, > > > -- > Mariano > http://marianopeck.wordpress.com > >

May 13, 2011