- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3589 in pharo: ClassComment in OB

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #3 on issue 3589 by marcus.d...(a)gmail.com: ClassComment in OB http://code.google.com/p/pharo/issues/detail?id=3589 (No comment was entered for this change.)

Jan. 30, 2011

Re: [Pharo-project] Issue 3471 in pharo: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #9 on issue 3471 by marcus.d...(a)gmail.com: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride http://code.google.com/p/pharo/issues/detail?id=3471 (No comment was entered for this change.)

Jan. 30, 2011

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

by David T. Lewis

On Fri, Jan 28, 2011 at 09:33:50AM +0700, Serge Stinckwich wrote: > On Fri, Jan 28, 2011 at 9:12 AM, David T. Lewis <lewis(a)mail.msen.com> wrote: > > On Wed, Jan 26, 2011 at 03:09:14PM +0000, pharo(a)googlecode.com wrote: > >> 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. > > > > FYI, the primitives for named serial ports are now in the standard VM > > (maybe not yet in Cog, but it is a small change). If someone would like > > to test on a Linux platform, try using any recent build of the standard > > VM or use the latest 4.4.7.2357 unix VM from http://squeakvm.org/unix/. > > > > The image changes to SerialPort are simple. You can either copy changes > > from Squeak or get the orginal change sets from the Mantis report at > > http://bugs.squeak.org/view.php?id=7266. > > > > The named serial port work was contributed by Severin Lemaignan > > <severin.lemaignan(a)laas.fr> and I helped with some of the integration. > > Anything that I did is MIT licensed. > > Hi David, > > there is a issue in the Pharo bug tracker since several months for the > integration of this changes into Pharo here: > http://code.google.com/p/pharo/issues/detail?id=1057 > > Could we integrate these changes in 1.2 as there is no licence problems at all. > David and S?verin could you sign the licence agreement, just to be > sure everything is ok. Just to be clear, the status of named serial port support is: - VM support for named serial ports is present in the standard VM. - VM support for named serial ports is not yet included in Cog. - Pharo developers should IMO include S?verin's SerialPort changes, but I am not involved in this and there are no changes to SerialPort with my author initials either in Squeak or in the change sets on Mantis 7266. HTH, Dave > > The quality of the code is not really good, there is a lot of isString > everywhere in order to test if the port is a number or a string > regarding the OS platform used: > > SerialPort>>close > "Close the serial port. Do nothing if the port is not open." > port > ifNotNil: [port isString ifTrue:[self primClosePortByName: port] > ifFalse:[self primClosePort:port]]. > port := nil > > I think we need to polish it in order maybe to use only strings. Why > not used string like 'COM1' for a windows platform and '/dev/ttyS*' > for Linux ? Any comments about that ? > > Regards, > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/

Jan. 30, 2011

Re: [Pharo-project] Issue 3470 in pharo: [Failing Tests] OBKeyBindingsTest

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #7 on issue 3470 by marcus.d...(a)gmail.com: [Failing Tests] OBKeyBindingsTest http://code.google.com/p/pharo/issues/detail?id=3470 (No comment was entered for this change.)

Jan. 30, 2011

Re: [Pharo-project] TODO 1.2

by StÃ©phane Ducasse

Marcus Can I suggest that we really remove the non show stopper? and I'm sorry but we cannot maintain packages we do not know. Lukas could you integrate the fix I did for OB? Stef > Hi, > > So for a release, we need to fix the following bugs: > > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage > > Now as these are all problems of packages, not of the Core, I can not just commit > to core. > > So we need to actually fix the package in the place where the package is loaded > from. (potentially by discussion this with the maintainer) > > This is something anyone can do. We do not need to wait for Mariano to ne back > from holiday (which will be in 3 weeks), nor will I do this. I am a bit sick of 1.2... > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

Jan. 30, 2011

Re: [Pharo-project] Issue 3469 in pharo: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #6 on issue 3469 by marcus.d...(a)gmail.com: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy http://code.google.com/p/pharo/issues/detail?id=3469 (No comment was entered for this change.)

Jan. 30, 2011

Re: [Pharo-project] Issue 3470 in pharo: [Failing Tests] OBKeyBindingsTest

by pharo＠googlecode.com

Comment #6 on issue 3470 by marcus.d...(a)gmail.com: [Failing Tests] OBKeyBindingsTest http://code.google.com/p/pharo/issues/detail?id=3470 Issue 3619 proposed a fix (I merged it into this report)

Jan. 30, 2011

Re: [Pharo-project] Issue 3470 in pharo: [Failing Tests] OBKeyBindingsTest

by pharo＠googlecode.com

Comment #5 on issue 3470 by marcus.d...(a)gmail.com: [Failing Tests] OBKeyBindingsTest http://code.google.com/p/pharo/issues/detail?id=3470 Issue 3619 has been merged into this issue.

Jan. 30, 2011

[Pharo-project] TODO 1.2

by Marcus Denker

Hi, So for a release, we need to fix the following bugs: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage Now as these are all problems of packages, not of the Core, I can not just commit to core. So we need to actually fix the package in the place where the package is loaded from. (potentially by discussion this with the maintainer) This is something anyone can do. We do not need to wait for Mariano to ne back from holiday (which will be in 3 weeks), nor will I do this. I am a bit sick of 1.2... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 30, 2011

Re: [Pharo-project] Issue 3619 in pharo: Hudson Pharo 1.2dev OBBrowser keybinding

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 3470 Comment #1 on issue 3619 by marcus.d...(a)gmail.com: Hudson Pharo 1.2dev OBBrowser keybinding http://code.google.com/p/pharo/issues/detail?id=3619 (No comment was entered for this change.)

Jan. 30, 2011