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

Re: [Pharo-project] Issue 3660 in pharo: Revert incorrect Monticello branch naming support

by pharo＠googlecode.com

Comment #1 on issue 3660 by da...(a)teleport.com: Revert incorrect Monticello branch naming support http://code.google.com/p/pharo/issues/detail?id=3660 GoferVersionReference>>parseName: is one of the other areas affected by Issue 281. So backing out the Issue 281 "fix" should be coordinated with a change to Gofer.

Feb. 5, 2011

[Pharo-project] Primitive calls in one package

by Laval Jannik

Hi, What is your opinion about having all primitive calls in one package ? It would be easier to maintain and to find them. Another question: why all existing primitive in VM have not a method in the image ? Cheers, --- Jannik Laval

Feb. 5, 2011

[Pharo-project] Issue 3660 in pharo: Revert incorrect Monticello branch naming support

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3660 by jfitz...(a)gmail.com: Revert incorrect Monticello branch naming support http://code.google.com/p/pharo/issues/detail?id=3660 After recent discussion with Dale Henrichs (see http://lists.squeakfoundation.org/pipermail/seaside-dev/2011-February/00455… ) I realize that my fix in Issue 281 was not correct. Actually, I'm not even sure whether the bug report was valid to begin with. The correct MC branch naming convention should be: <hyphenated-package-name>.<dotted.branch.tag>-<initials>.<count>.mcz and it appears the tools are currently largely supporting this. The *incorrect* convention pushed in by Issue 281 was: <hyphenated-package-name>-<initials>.<dotted.branch.tag>.<count>.mcz I don't know if the incorrect convention has become widely adopted, but it would reduce future confusion if we can back out the Issue 281 "fix".

Feb. 5, 2011

Re: [Pharo-project] [ANN] JNIPort 2.0 for VisualWorks, Pharo and Squeak

by Joachim Geidel

Am 05.02.11 18:11 schrieb Tudor Girba: > What are the impediments of getting it to work with Cog on Pharo? JNIPort relies on Alien, and I have not yet found a Cog VM working with Alien and JNIPort. I tried Squeak 5.8b12 for Mac OS X which identifies itself as Cog, but it crashes when you just evaluate "LibCLibrary uniqueInstance". Apparently this VM version doesn't work with Alien. Eliot's latest Cog build for Mac OS X at http://www.mirandabanda.org/files/Cog/VM/VM.r2349/ is able to load libc. When I try to use JNIPort, it can't find the library libjvm.dylib when I create a symbolic link to it in the working directory. When I create a symbolic link in the subdirectory Cog.app/Contents/Resources, it is able to load the library, but the VM crashes with a bus error when I try to call the first function of the library. I currently have no idea what causes the error. As the same code runs without problems on a Squeak VM, I don't think that the problem is in the JNIPort code, but I may be wrong. So, no JNIPort on Cog for now. This may change soon, of course. Regards, Joachim Geidel

Feb. 5, 2011

Re: [Pharo-project] Smalltalk for engineers

by Geoffroy Couprie

That's what I was trying to express: when you already program with another language, you can easily understand a new language, but you have big assumptions that will slow you down. I just pointed out the most important parts that surprised me when I learned Smalltalk. On Sat, Feb 5, 2011 at 7:28 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > That comment requires elaboration or at least some examples of what one can/should do, but getting past that is a big hurdle in learning Smalltalk. Â Things old to us can be earth shattering: something as simple as creating a new package (or even just a new class or a new class method somewhere, etc.) vs. writing a whole new program in some other language. > > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of John McIntosh [johnmci(a)smalltalkconsulting.com] > Sent: Saturday, February 05, 2011 5:33 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Smalltalk for engineers > > Casual mention of iPhone port, always helpfull > > On 2/4/11, Geert Claes <geert.wl.claes(a)gmail.com> wrote: >> >> James Robertson spotted this post: >> >> http://unhandledexpression.com/2011/02/04/smalltalk-for-engineers/ >> >> I was especially interested in the statement "you donât understand what you >> can/should do ..." >> -- >> View this message in context: >> http://forum.world.st/Smalltalk-for-engineers-tp3261551p3261551.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> > > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> > Corporate Smalltalk Consulting Ltd. Â http://www.smalltalkconsulting.com > =========================================================================== > >

Feb. 5, 2011

Re: [Pharo-project] Smalltalk for engineers

by Schwab,Wilhelm K

That comment requires elaboration or at least some examples of what one can/should do, but getting past that is a big hurdle in learning Smalltalk. Things old to us can be earth shattering: something as simple as creating a new package (or even just a new class or a new class method somewhere, etc.) vs. writing a whole new program in some other language. ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of John McIntosh [johnmci(a)smalltalkconsulting.com] Sent: Saturday, February 05, 2011 5:33 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Smalltalk for engineers Casual mention of iPhone port, always helpfull On 2/4/11, Geert Claes <geert.wl.claes(a)gmail.com> wrote: > > James Robertson spotted this post: > > http://unhandledexpression.com/2011/02/04/smalltalk-for-engineers/ > > I was especially interested in the statement "you donât understand what you > can/should do ..." > -- > View this message in context: > http://forum.world.st/Smalltalk-for-engineers-tp3261551p3261551.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Feb. 5, 2011

Re: [Pharo-project] Smalltalk for engineers

by Dale Henrichs

Grey bearded _and_ long hair +10000:) Dale On Feb 5, 2011, at 5:02 AM, Geert Claes wrote: > > > Peter Hugosson-Miller wrote: >> >> Bearded +1 >> > > Bearded +1 :) > -- > View this message in context: http://forum.world.st/Smalltalk-for-engineers-tp3261551p3261768.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Feb. 5, 2011

Re: [Pharo-project] Where is OB Was: [what do we do for OmniBrowser?]

by Guillermo Polito

Ok, now Gofer it squeaksource: 'PharoOB'; package: 'ConfigurationOfOmniBrowser'; load (ConfigurationOfOmniBrowser project version: '1.2.4') load Downloads OB from PharoOB ;). Have a nice weekend! Guille On Fri, Feb 4, 2011 at 3:55 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Go for PharoOB and we will delete files from PharoTaskForces > > Stef > > On Feb 4, 2011, at 1:15 AM, Guillermo Polito wrote: > > > Today's ConfigurationOfOmniBrowser relies on lukas repo and > PharoTaskForces (in SS). > > > > When there is an 1.2 specific fix, I'm commiting it to PharoTaskForces. > > When there is a fix on Lukas repo, I merge it and commit it to > PharoTaskForces. > > > > BTW, If we push everything in PharoOB, we'll have everything there (OB > code and metacello configurations). PharoOB has global read and write > access (I recreated it a few hours ago since it got lost :P ), so everyone > may contribute :). > > > > > > Guille > > > > On Thu, Feb 3, 2011 at 8:57 PM, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > > Guillermo please tell us which code base you are using otherwise OB > > will continue to be one-man show. > > > > 2011/2/3 Guillermo Polito <guillermopolito(a)gmail.com>: > > > > > > I'm integrating already the fixes into PharoTaskForces. If I have some > tome > > > tomorrow I'll push OB from Lukas repo to PharoOB and merge. > > > > > > Guille :) > > > > > >> > > >> Stef > > >> > > > > > > >

Feb. 5, 2011

Re: [Pharo-project] Issue 3659 in pharo: Task bar appearance does not make sense

by pharo＠googlecode.com

Comment #1 on issue 3659 by tudor.gi...(a)gmail.com: Task bar appearance does not make sense http://code.google.com/p/pharo/issues/detail?id=3659 I agree, but I could not get it to work like I wanted for the Glamorous Theme. It would be great if someone could take a look at this.

Feb. 5, 2011

Re: [Pharo-project] [ANN] JNIPort 2.0 for VisualWorks, Pharo and Squeak

by Tudor Girba

Sounds great! What are the impediments of getting it to work with Cog on Pharo? Cheers, Doru On 5 Feb 2011, at 16:14, Joachim Geidel wrote: > JNIPort 2.0 for VisualWorks, Pharo and Squeak is now available! > > JNIPort is a Smalltalk library which allows Java code to be invoked from > Smalltalk. It acts as a bridge between the world of Smalltalk objects and a > Java Virtual Machine (JVM) where Java code is executing. For more > information see > > http://jniport.wikispaces.com > > JNIPort 2.0 for VisualWorks can be loaded from the Cincom Public Store > Repository and from the JNIPort wiki at > > http://jniport.wikispaces.com/Downloads > > JNIPort 2.0 for Pharo and Squeak is available from SqueakSource at > > http://www.squeaksource.com/JNIPort.html > > and from the JNIPort wiki. > > The changes from JNIPort 1.9 are: > > - JNIPort can now be used in Pharo and Squeak. > > - Packages have been renamed such that the can be shared between Store > and Monticello. > > - Platform specific code has been moved to separate packages to make the > core packages portable between VisualWorks, Pharo, and Squeak. > > - The much-critized _null postfix used for selectors of wrapper methods > which don't have arguments is gone. > > - A few bugs have been fixed. > > Installation instructions for VisualWorks are on the JNIPort wiki, > instructions for Pharo and Squeak are on the wiki of the JNIPort project > page of SqueakSource. I strongly encourage you to read the instructions > before installing and using JNIPort. > > JNIPort 2.0 has been tested with: > > - VisualWorks from 7.5 to 7.8 (trent dec10.3) on Mac OS X 10.6.6 and > Windows XP SP 3 > > - VisualWorks from 7.7 to 7.8 (trent dec10.3) on Ubuntu 10.04 (64bit) > with both the 32-bit and the 64-bit VisualWorks VMs > > - Squeak 4.2 on Mac OS X 10.6.6 and Windows XP SP 3 > > - Pharo 1.1.1 and 1.2 on Mac OS X 10.6.6 and Windows XP SP 3 > > Known issues: > > - In Pharo 1.1.1, you may encounter an error when JNIPort tries to register > a new Java object in an internal weak dictionary. This is a bug in Pharo's > implementation of this collection class. I can't do anything about it. If > you can't live with it, please upgrade to Pharo 1.2. > > - JNIPort for Pharo and Squeak currently cannot be used with the Cog VM. > > - Callbacks from foreign operating system threads cannot be used in Pharo > and Squeak. The Alien foreign function interface does not yet support > this feature. When you run the unit tests, three tests will fail because > of this restriction. These failures are expected and do not indicate bugs. > > Best regards, > Joachim Geidel -- www.tudorgirba.com "Don't give to get. Just give."

Feb. 5, 2011