- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Examples for UITheme

by Cyrille Delaunay

It's done :) 2009/10/2 Marcus Denker <denker(a)acm.org> > > On 02.10.2009, at 10:32, Cyrille Delaunay wrote: > > > Hi, > > > > I have added comments to the UITheme classe description and into the > > examples methods, to evaluate directly the examples. > > I have saved that in 'PharoInBox' in squeaksource. > > Can you add an entry in the issue tracker for that? > > Marcus > > > > > -- > Marcus Denker - http://marcusdenker.de > PLEIAD Lab - Computer Science Department (DCC) - University of Chile > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 2, 2009

Re: [Pharo-project] Examples for UITheme

by Marcus Denker

On 02.10.2009, at 10:32, Cyrille Delaunay wrote: > Hi, > > I have added comments to the UITheme classe description and into the > examples methods, to evaluate directly the examples. > I have saved that in 'PharoInBox' in squeaksource. Can you add an entry in the issue tracker for that? Marcus -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Oct. 2, 2009

[Pharo-project] [update] #10465

by Marcus Denker

10465 ----- Issue 1203: ThreadSafeTranscript(Object)>>doesNotUnderstand: #print: Issue 773: Comment and category in Utilities class>>addUpdateServer: Issue 1259: ProcessorScheduler>>selfEvaluating -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Oct. 2, 2009

[Pharo-project] Examples for UITheme

by Cyrille Delaunay

Hi, I have added comments to the UITheme classe description and into the examples methods, to evaluate directly the examples. I have saved that in 'PharoInBox' in squeaksource.

Oct. 2, 2009

Re: [Pharo-project] StrikeFont Accujen in Pharo

by Jochen

StÃ©phane Ducasse schrieb: >>>>>> >> Thank you Henry! With your hint i've finally found a solution! >> >> In Squeak I could file out the font with: >> (StrikeFont familyName: 'Accujen' size: 9) writeAsStrike2named: >> 'Accujen9.sf2' >> >> In Pharo then I could file it in with: >> TextConstants at: 'Accujen' put: (TextStyle fontArray: (Array with: >> (StrikeFont new readFromStrike2: 'Accujen9.sf2'))). >> Preferences restoreDefaultFonts. >> StrikeFont limitTo16Bits. >> StrikeFont useUnderscoreIfOver1bpp >> >> Now I can use the Accujen like any other font in Pharo. :) >> > > could you package that and put it somewhere? > so that we can reuse it somebody needs it? > A AccujenPharo Package would be great! > > Stef I'm quite new to packages/monticello etc. - probably it should be two packages: one for Squeak (to file out) and one for Pharo (to file in). Or is it possible to include files (the fonts) into packages? I'm quite busy at the moment but will think about it the next days! Jochen

Oct. 2, 2009

Re: [Pharo-project] PositionableStream and uintXXX

by Andrey Larionov

Thanks. I found what i need send a binary to stream before processing. On Fri, Oct 2, 2009 at 16:02, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > tream defines binary as well, default implementation does nothing, > look at it's subclasses implementors to see which support it.

Oct. 2, 2009

Re: [Pharo-project] PositionableStream and uintXXX

by Henrik Johansen

(SocketStream on: socket) binary. Stream defines binary as well, default implementation does nothing, look at it's subclasses implementors to see which support it. Cheers, Henry On Oct 2, 2009, at 5:16 15AM, Andrey Larionov wrote: > I'm try to launch FastCGI for Seaside. And there is a question. > From socket stream reads some byte sequence which wraped by ReadStream > on which reading operations is continued. In some place called unit24 > message, which sends bitShift: message. But from stream returned not > an Integer but Character, which dosnt have an bitShift: method. What > i'm missed? is there should be special calls to made stream binary? > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 2, 2009

[Pharo-project] What Collection is suitable for binary stream

by Andrey Larionov

I'm a novice for Smalltalk. Can any body suggest proper collection for binary stream. I try ByteArray - it dosn't allow Characters, try ByteString - it not allow non literals. Which collection (or maybe pattern) should be used to write binary and character data?

Oct. 2, 2009

Re: [Pharo-project] better error handling

by Igor Stasenko

2009/10/2 Alex Schenkman <alex(a)schenkman.info>: > Igor, > I'm trying to understand your suggestion. > Am I thinking correclty? > Thanks in advance! > On Thu, Oct 1, 2009 at 23:42, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> How about a visitor pattern? >> >> [ a block of code where you do something that can singal different >> exceptions Â ] >> Â Â on: Error do: [:ex | >> ex visitWith: self >> ] >> > I had to replace self with a class handling the errors: > [ZeroDivide new signal: 'zero'] > Â Â Â on: Error do: > Â [:error | error visitWith: (MyErrorHandler new)]. > > Error>>visitWith: anErrorHandler > Â Â Â ^ anErrorHandler handleError: self > > MyErrorHandler>>handleError: anError > Â Â Â ^anError signal > > > Error subclass: #AlexError > AlexError>>visitWith: anErrorHandler > Â Â Â ^ anErrorHandler handleAlexError: self > AlexError>>handleAlexError: anAlexError > Â Â Â ^'Handling an AlexError now.' > > yes, something like that > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Oct. 2, 2009

Re: [Pharo-project] better error handling

by Alex Schenkman

Igor, I'm trying to understand your suggestion. Am I thinking correclty? Thanks in advance! On Thu, Oct 1, 2009 at 23:42, Igor Stasenko <siguctua(a)gmail.com> wrote: > > How about a visitor pattern? > > [ a block of code where you do something that can singal different > exceptions ] > on: Error do: [:ex | > ex visitWith: self > ] > > I had to replace self with a class handling the errors: [ZeroDivide new signal: 'zero'] on: Error do: [:error | error visitWith: (MyErrorHandler new)]. Error>>visitWith: anErrorHandler ^ anErrorHandler handleError: self MyErrorHandler>>handleError: anError ^anError signal Error subclass: #AlexError AlexError>>visitWith: anErrorHandler ^ anErrorHandler handleAlexError: self AlexError>>handleAlexError: anAlexError ^'Handling an AlexError now.'

Oct. 2, 2009