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

Re: [Pharo-dev] MultiByteFileStream #converter - what does it do?

by stepharo

Could you think about a roadmap? Because we are doing often actions that require a lot of work but people do not notice it. Stef > Yes, one day we have to do this. > > There is also Xtreams which is a broader, more interesting way of rethinking the subject. > > But the main issue is: the stream API is way too broad, so any change will involve slimming down or changing the API and hence the users. That is a lot of work. > >> On 18 Dec 2014, at 23:51, stepharo <stepharo(a)free.fr> wrote: >> >> Sven >> >> could we not nuke >> >> MultiByteFileStream >> >> and use ZnCharacterStreams? >> >> >> Le 17/12/14 19:54, Sven Van Caekenberghe a Ã©crit : >>>> On 17 Dec 2014, at 19:42, sheridan(a)sheridan-mahoney.com wrote: >>>> >>>> Hi there, >>>> >>>> I am still working my way through MultiByteFileStream tests, and have come across the messages #converter and #converter: . I would like to be able to test these - could someone explain briefly how the converters are used in this class? >>> In order to convert from bytes to characters and vice versa, MultiByteFileStream uses a TextConverter subclass instance as a helper. The messages #nextFromStream: and #nextPut:onStream: are the main interface between the two. >>> >>> The silly thing is that both MultiByteFileStream and TextConverter convert from wrongly encoded strings to correctly encoded strings. ZnCharacter[Read|Write]Stream and ZnCharacterEncoder do the correct thing. >>> >>> Sven >>> >> > >

Dec. 23, 2014

Re: [Pharo-dev] running MS Surface Pro 3 on Windows 8 - test failure - JobTest>>#testCurrent

by stepharo

Hi sheridan are you talking about Pharo 40? Stef Le 22/12/14 23:42, sheridan(a)sheridan-mahoney.com a Ã©crit : > Hi, > There is an open bug (12435 - skip JobTest>>#testCurrent to test) > saying a test failure with JobTest>>#testCurrent had been fixed, but I > am seeing a re-occurrence of the problem on my Windows 8.1 Pro when I > run the full body of test cases available. However when I run the test > case on its own, the test passes. This seems like an anomaly but is it > bug-worthy? Here is the code: > > testCurrent > self assert: Job current isNil. > > [ :aJob | > self assert: Job current equals: aJob. > > [ :anotherJob | > self assert: Job current equals: anotherJob. > ] asJob run. > > self assert: Job current equals: aJob. > ] asJob run. > > self assert: Job current isNil. > > > Thanks, > Sheridan > >

Dec. 23, 2014

Christmas gift: Memory Monitor

by Torsten Bergmann

>Torsten motivated us to upgrade Memory monitor. Thanks! Would be nice if others could check and update their packages too. >Memory monitor is accessible from the configuration browser. Â Easy accessibility is key, otherwise packages will get lost in the repo universe and with Versionner it is easy to provide a config these days! Bye T.

Dec. 23, 2014

Re: [Pharo-dev] Christmas gift: Memory Monitor

by Sean P. DeNigris

abergel wrote > In Pharo 4.0, buttons are missing. Any idea whatâs wrong? The layout was weird. Fixed version at http://smalltalkhub.com/mc/SeanDeNigris/SeansOutbox/main/ works on 3.0 & 4.0 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Christmas-gift-Memory-Monitor-tp4796722p4796731.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Dec. 23, 2014

Christmas gift: Memory Monitor

by Alexandre Bergel

Hi! Torsten motivated us to upgrade Memory monitor. Here is the script: -=-=-=-=-=-=-=-=-=-=-=-= Gofer it smalltalkhubUser: 'abergel' project: 'MemoryMonitor'; configurationOf: 'MemoryMonitor'; loadStable. -=-=-=-=-=-=-=-=-=-=-=-= In Pharo 3.0, you get something like: In Pharo 4.0, buttons are missing. Any idea whatâs wrong? Memory monitor is accessible from the configuration browser. Kind regards, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 22, 2014

Re: [Pharo-dev] running MS Surface Pro 3 on Windows 8 - test failure - JobTest>>#testCurrent

by sheridan＠sheridan-mahoney.com

Hi, There is an open bug (12435 - skip JobTest>>#testCurrent to test) saying a test failure with JobTest>>#testCurrent had been fixed, but I am seeing a re-occurrence of the problem on my Windows 8.1 Pro when I run the full body of test cases available. However when I run the test case on its own, the test passes. This seems like an anomaly but is it bug-worthy? Here is the code: testCurrent self assert: Job current isNil. [ :aJob | self assert: Job current equals: aJob. [ :anotherJob | self assert: Job current equals: anotherJob. ] asJob run. self assert: Job current equals: aJob. ] asJob run. self assert: Job current isNil. Thanks, Sheridan

Dec. 22, 2014

Do not forget to register to Pharo days...

by stepharo

http://pharodays2015.pharo.org Stef

Dec. 22, 2014

Re: [Pharo-dev] Excel binding

by Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾

Sorry, was mostly out of online. Of course, your contribution is welcome. Repository is globally writeable espesially for this kind of situations :) 2014-12-10 13:08 GMT+03:00 Blondeau Vincent <vincent.blondeau(a)worldline.com> : > Nice! > > > > Can I extend your project to add the .xlsx reading? > > > > Regards, > > > > Vincent > > > > *De :* Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *De la part > de* ???? ????????? > *EnvoyÃ© :* mercredi 10 dÃ©cembre 2014 01:16 > *Ã :* Pharo Development List > *Objet :* Re: [Pharo-dev] Excel binding > > > > Yes, including this, but not limited to this. > > > > I.e. not only generation, but also reading. Generation is just somewhat > simpler - so I started from this point. > > > > I announced it some tim ago, it's http://ss3.gemstone.com/ss/Tabular.html > > > > 2014-12-09 20:49 GMT+03:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > > El Tue Dec 09 2014 at 2:22:32 PM, Ð®ÑÐ¸Ð¹ ÐÐ¸ÑÐ¾Ð½ÐµÐ½ÐºÐ¾ <assargaddon(a)gmail.com> > escribiÃ³: > > I'm working on XLSX / ODS support code just now. > Nothing done on *reading* the data yet, but it may be easily switched. > > > > But my plans do not includes support of (binary) XLS format. > > > > > > > > Are you working on OpenXML (.xlsx) file generation? > > > > Regards! > > > > ------------------------------ > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un > virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. As > its integrity cannot be secured on the Internet, the Worldline liability > cannot be triggered for the message content. Although the sender endeavours > to maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted. >

Dec. 22, 2014

Re: [Pharo-dev] [OT] Bee Smalltalk

by Max Leske

Maybe there is something in the presentation they gave at ESUG this year (check the ESUG youtube channel)? > On 22 Dec 2014, at 15:32, Torsten Bergmann <astares(a)gmx.de> wrote: > > Anyone know what happened to Bee Smalltalk? > > The release announced at http://beesmalltalk.blogspot.de > is not available on GitHub anymore. > > https://github.com/melkyades/bee is pointing to nowhere... > > >

Dec. 22, 2014

[OT] Bee Smalltalk

by Torsten Bergmann

Anyone know what happened to Bee Smalltalk? The release announced at http://beesmalltalk.blogspot.de is not available on GitHub anymore. https://github.com/melkyades/bee is pointing to nowhere...

Dec. 22, 2014