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

Re: [Pharo-project] First commit to Pharoinbox. Need advice.

by StÃ©phane Ducasse

+1 > Refactorings and more tests are certainly welcome! > > Here's a few comments: > While I like keeping common functionality in one place, I'm not sure creating a new helper object for each at:/at:put: access is a good idea. Nor keeping the helper cached to avoid this. Have you considered using a Trait instead? To me it seems like a good use-case for one. > > To the tests: > - setUp uses at:put:. testAt asserts the values set in setUp. Thus, is it not really just another at:put: test? Does it test something not covered by the other at:put: test(s)? > - testAtPutLargeInteger uses a static integer. This is not ideal, as the range of SmallInteger depends on platform (I realize though, that it is large enough for it not to fail on 64bit as well). > Using f.ex SmallInteger maxVal + staticInteger is more intention revealing. > Although, max/minVal actually returns a constant at the moment rather than a platform-specific value, and thus would fail on 64bit. I'd consider this a bug which it'd be nice if a test exposed :) > - testWriteXYEndianOn uses 256*256*256. etc. Probably down to preference, but I think they'd looks nicer using the bitShift: (or #<< if you prefer less parenthesis) operator. > > Cheers, > Henry >

Jan. 26, 2011

Re: [Pharo-project] First commit to Pharoinbox. Need advice.

by StÃ©phane Ducasse

On Jan 26, 2011, at 12:40 PM, HwaJong Oh wrote: > > Thank you for your detailed advice. > Although i could only comply bitShift: adivce. Using trait was unsuccessful. > super send is not possible with traits and applying PointArrayTrait on > ShortPointArray makes strange error. super send are possible with traits. Tell us what was your problem. Stef > > New version is out. (Balloon-hjo.73) > -- > View this message in context: http://forum.world.st/First-commit-to-Pharoinbox-Need-advice-tp3237535p3237… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 26, 2011

Re: [Pharo-project] Easy access on pharo-project.org

by StÃ©phane Ducasse

Good ideas! On Jan 26, 2011, at 11:14 AM, Torsten Bergmann wrote: > We have the shortcut to the collaborative book: > > http://book.pharo-project.org > > > Would it be possible: > > 1. to access the build server > https://pharo-ic.lille.inria.fr/hudson/ > > under a simple name like: > > http://hudson.pharo.org or > http://ci.pharo.org (ci = continuos integration) > > 2. to access the issue tracker > http://code.google.com/p/pharo/issues > under > > http://issues.pharo-project.org or > http://bugs.pharo-project.org > > 3. to access the wiki > http://code.google.com/p/pharo/w/list > under > http://wiki.pharo-project.org > > 4. And the book page > http://pharo-project.org/documentation/tutorials-books > has no reference to the collaborative book > http://book.pharo-project.org > > Thx > T. > -- > GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit > gratis Handy-Flat! http://portal.gmx.net/de/go/dsl >

Jan. 26, 2011

Re: [Pharo-project] Issue 3599 in pharo: Serial Port

by pharo＠googlecode.com

Comment #2 on issue 3599 by ryd...(a)gmail.com: Serial Port http://code.google.com/p/pharo/issues/detail?id=3599 Hasn't mr. Schwab been talking about this too? The scratch source code license is available as part of the download at http://info.scratch.mit.edu/Source_Code. Afaict it's not MIT compatible, since it contains both non-commercial and copyleft clauses for derived works.

Jan. 26, 2011

Re: [Pharo-project] [ENH] About NonInteractive UI manager

by Sven Van Caekenberghe

On 26 Jan 2011, at 16:12, Igor Stasenko wrote: > I found that it doesn't works with Cog VM on Macs. > > On Hudson build server, which runs on linux it works well out of the > box (but that using Sqeuak VM though). OK, Thanks. I found the Cog VM's acting strange sometimes, especially in the headless case, a hanging headless VM is hard to debug (NonInteractive UI manager will hopefully change that in the future). The latest unix VM (4.4.7 2356) worked better for me. Sven

Jan. 26, 2011

Re: [Pharo-project] Issue 3599 in pharo: Serial Port

by pharo＠googlecode.com

Comment #1 on issue 3599 by stephane...(a)gmail.com: Serial Port http://code.google.com/p/pharo/issues/detail?id=3599 see 1057

Jan. 26, 2011

Re: [Pharo-project] Issue 1057 in pharo: SerialPlugin doesn't handle arbitrary nodes names

by pharo＠googlecode.com

Updates: Labels: Milestone-1.3 Comment #7 on issue 1057 by stephane...(a)gmail.com: SerialPlugin doesn't handle arbitrary nodes names http://code.google.com/p/pharo/issues/detail?id=1057 ok We should have a look at that!

Jan. 26, 2011

Re: [Pharo-project] [ENH] About NonInteractive UI manager

by Igor Stasenko

On 26 January 2011 15:59, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 26 Jan 2011, at 15:27, Igor Stasenko wrote: > >> Hello pharoers, >> >> the last two days we worked hard with Marcus to incorporate this new >> stuff into image, and now we're done. >> All images past #13021 now have non interactive ui manager >> (NonInteractiveUIManager). >> We fixed almost all broken tests caused by introducing it (there are >> only few minor ones left). > > Very good. Thanks a lot for all the effort! I'll have to start tracking 1.3 now and we're not yet using 1.2 ;-) > >> Probably there could be more infrastructure around that in future >> (like redirecting Transcript output to some file/stdout while running >> headless), but first things first. > > Indeed, one step at a time, but if you add that as well, I think you have a complete solution! > > Things like advanced command line processing, scripting tools and some kind of REPL are too complex for core and should be part of optional packages. > > Sven > > PS: For which VM's is it necessary to say -headless twice ? > > I found that it doesn't works with Cog VM on Macs. On Hudson build server, which runs on linux it works well out of the box (but that using Sqeuak VM though). > > -- Best regards, Igor Stasenko AKA sig.

Jan. 26, 2011

Re: [Pharo-project] [ENH] About NonInteractive UI manager

by StÃ©phane Ducasse

>> > > Indeed, one step at a time, but if you add that as well, I think you have a complete solution! > > Things like advanced command line processing, scripting tools and some kind of REPL are too complex for core and should be part of optional packages. we will have that soon :) We want to rewrite the codeLoader from scratch for Coral.

Jan. 26, 2011

[Pharo-project] Issue 3599 in pharo: Serial Port

by pharo＠googlecode.com

Status: Accepted Owner: stephane...(a)gmail.com Labels: Milestone-1.3 New issue 3599 by stephane...(a)gmail.com: Serial Port http://code.google.com/p/pharo/issues/detail?id=3599 Hello We are developing software to interact with small robots for educational purposes. To do this we need to use the serial port. SerialPort class that includes Pharo does not work on mac or linux, because itÂ´s not able to open ports by name. It would be interesting that future versions include a SerialPort that would work in these circumstances. we are using since a time aÂ´go the plugin that comes with Scratch, with this we just copy the plugins in the folder of the VM, the Plugin that comes with the VM Scrath, and add to the image of the image classes of Scratch , ScratchPlugin and SerialPort2.Up to date this has worked on all VM including the latest Cog. It works on Linux, Mac or Windows.We wory that future versions will lose support. One important question is what is the license of scratch Then in addition I know that there is a fix made by serge for SerialPort

Jan. 26, 2011