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

Re: [Pharo-project] Comment Syntax

by Nicolas Cellier

2011/11/1 Sean P. DeNigris <sean(a)clipperadams.com>: > > Schwab,Wilhelm K wrote: >> >> ...It would be nice if it were portable to other Smalltalks, but it would >> be useful. >> ... >> XP advocates would tell us that we don't need the code and to just delete >> it. >> > > The second point is valid, but only applies to a subset of comments. For > example, in my case the thing that needs to be commented is Applescript code > that provides context for the method. It is part of the documentation, and > must contain double quotes to be valid Applescript. > > -- > View this message in context: http://forum.world.st/Comment-Syntax-tp3961451p3962192.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > An alternative would be like in some scripting language : everything after this mark is a comment. We can even doIt easily with Smalltalk-80 parser, I remember that the end of tokens was marked with a DoIt character encoded as value 30 or something like that ;) If you did introduce such character in code, then interpretation did stop at the DoIt mark. I always thought this was a bug - but now I understand a possible usage :) Of course, this only works when Browsing a single method. If you file out sources, then you still have to delimit the method source with doubled bangs ! or something... So take this as a joke more than a proposition. Nicolas

Nov. 1, 2011

Re: [Pharo-project] Goods Test Runner Pharo 1.3 Issues

by StÃ©phane Ducasse

let us know because core collection should be really robust. Stef On Nov 1, 2011, at 9:52 AM, mail list wrote: > I will check. Thank you. > > The problem is definitely something related to 'reachability'. eg I can save the top level objects but the second level objects (eg instance varaibles of the top level) I can not get to save. > > S. > On Nov 1, 2011, at 2:59 PM, Lukas Renggli wrote: > >> Not sure if this is related, but the collection hierarchy got refactored in Pharo at some point to include HashedCollection (AFAIR) as superclass. Maybe this broke something with the persistence of Sets and Dictionaries? >> >> Lukas >> >> On Tuesday, 1 November 2011, mail list <mail.list(a)ficonab.com> wrote: >> > I am trying to deploy a Pharo 1.3 image using Goods and running into some basic issues where my objects are not persisted by reachability. >> > eg I put dictionary x at root under a key 'test' >> > eg db root at: 'test' put x. >> > db commit. >> > Then at x i updated instance variable and add something to its dictionary and committ >> > eg x intancevariable y at: 'key' put 'zzzz' >> > db commit >> > >> > looking at the root x does not get updated with y. >> > >> > I have the majority of the test cases pasing except for testIdentitySet and testFlushAllRemovesAllUnreferenced. >> > >> > In testIdentitySet the following failure >> > | set x y y2 | >> > set := KKIdentitySet database: dbOne. >> > x := 1@1. >> > y := 2@2. >> > set add: x. >> > set add: y. >> > self assert: (set includes: x). >> > self assert: (set includes: y). >> > self deny: (set includes: 1@1). -->fails >> > >> > set = (2@2,1@1) >> > so it seems to think that x and 1@1 are the same. Which to me seems correct but I may be misunderstanding the testcase. >> > >> > Any thoughts or pointers to update my mistakes in using Goods db would be helpful. >> > >> > S. >> > On Oct 31, 2011, at 5:49 PM, Marcus Denker wrote: >> > >> >> 13320 >> >> ----- >> >> >> >> Issue 4945: Weird Settings filtering >> >> http://code.google.com/p/pharo/issues/detail?id=4945 >> >> >> >> -- >> >> Marcus Denker -- http://marcusdenker.de >> >> >> >> >> > >> > >> > >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >

Nov. 1, 2011

Re: [Pharo-project] Is FS loadable in 1.3?

by StÃ©phane Ducasse

Yes I guess that with damien we cleaned it. Still missing rename. Stef On Nov 1, 2011, at 2:19 AM, Sean P. DeNigris wrote: > > Tudor Girba-2 wrote: >> >> Please note that the official up-to-date ConfigurationOfFilesystem can be >> found in the squeaksource.com/fs repository. >> > > All 311 tests pass for #latestVersion in 1.3-rc. Sweet. > > -- > View this message in context: http://forum.world.st/Is-FS-loadable-in-1-3-tp3961499p3962226.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Nov. 1, 2011

Re: [Pharo-project] FS-Help

by StÃ©phane Ducasse

would be nice. Stef On Nov 1, 2011, at 2:15 AM, Sean P. DeNigris wrote: > Include with 1.4? (currently it's not) > > -- > View this message in context: http://forum.world.st/FS-Help-tp3962221p3962221.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Nov. 1, 2011

Re: [Pharo-project] Athens news :)

by Igor Stasenko

On 31 October 2011 22:54, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Igor let wild people have a look. > > Provide a script so that people can load and a bunch of examples. > Ok. i will > Stef > > On Oct 31, 2011, at 5:21 PM, Igor Stasenko wrote: > >> The text rendering is most complex part. And it going very slow, >> slower than i thought. >> Apart from text, there's a lot things to think about. >> But what i want to do right now is to implement enough functionality >> to fully render morphic desktop in pharo. >> And then we can discuss what else we need as well as what we dont need :) >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > > -- Best regards, Igor Stasenko.

Nov. 1, 2011

Re: [Pharo-project] Goods Test Runner Pharo 1.3 Issues

by mail list

I will check. Thank you. The problem is definitely something related to 'reachability'. eg I can save the top level objects but the second level objects (eg instance varaibles of the top level) I can not get to save. S. On Nov 1, 2011, at 2:59 PM, Lukas Renggli wrote: > Not sure if this is related, but the collection hierarchy got refactored in Pharo at some point to include HashedCollection (AFAIR) as superclass. Maybe this broke something with the persistence of Sets and Dictionaries? > > Lukas > > On Tuesday, 1 November 2011, mail list <mail.list(a)ficonab.com> wrote: > > I am trying to deploy a Pharo 1.3 image using Goods and running into some basic issues where my objects are not persisted by reachability. > > eg I put dictionary x at root under a key 'test' > > eg db root at: 'test' put x. > > db commit. > > Then at x i updated instance variable and add something to its dictionary and committ > > eg x intancevariable y at: 'key' put 'zzzz' > > db commit > > > > looking at the root x does not get updated with y. > > > > I have the majority of the test cases pasing except for testIdentitySet and testFlushAllRemovesAllUnreferenced. > > > > In testIdentitySet the following failure > > | set x y y2 | > > set := KKIdentitySet database: dbOne. > > x := 1@1. > > y := 2@2. > > set add: x. > > set add: y. > > self assert: (set includes: x). > > self assert: (set includes: y). > > self deny: (set includes: 1@1). -->fails > > > > set = (2@2,1@1) > > so it seems to think that x and 1@1 are the same. Which to me seems correct but I may be misunderstanding the testcase. > > > > Any thoughts or pointers to update my mistakes in using Goods db would be helpful. > > > > S. > > On Oct 31, 2011, at 5:49 PM, Marcus Denker wrote: > > > >> 13320 > >> ----- > >> > >> Issue 4945: Weird Settings filtering > >> http://code.google.com/p/pharo/issues/detail?id=4945 > >> > >> -- > >> Marcus Denker -- http://marcusdenker.de > >> > >> > > > > > > > > -- > Lukas Renggli > www.lukas-renggli.ch

Nov. 1, 2011

Re: [Pharo-project] Goods Test Runner Pharo 1.3 Issues

by Lukas Renggli

Not sure if this is related, but the collection hierarchy got refactored in Pharo at some point to include HashedCollection (AFAIR) as superclass. Maybe this broke something with the persistence of Sets and Dictionaries? Lukas On Tuesday, 1 November 2011, mail list <mail.list(a)ficonab.com> wrote: > I am trying to deploy a Pharo 1.3 image using Goods and running into some basic issues where my objects are not persisted by reachability. > eg I put dictionary x at root under a key 'test' > eg db root at: 'test' put x. > db commit. > Then at x i updated instance variable and add something to its dictionary and committ > eg x intancevariable y at: 'key' put 'zzzz' > db commit > > looking at the root x does not get updated with y. > > I have the majority of the test cases pasing except for testIdentitySet and testFlushAllRemovesAllUnreferenced. > > In testIdentitySet the following failure > | set x y y2 | > set := KKIdentitySet database: dbOne. > x := 1@1. > y := 2@2. > set add: x. > set add: y. > self assert: (set includes: x). > self assert: (set includes: y). > self deny: (set includes: 1@1). -->fails > > set = (2@2,1@1) > so it seems to think that x and 1@1 are the same. Which to me seems correct but I may be misunderstanding the testcase. > > Any thoughts or pointers to update my mistakes in using Goods db would be helpful. > > S. > On Oct 31, 2011, at 5:49 PM, Marcus Denker wrote: > >> 13320 >> ----- >> >> Issue 4945: Weird Settings filtering >> http://code.google.com/p/pharo/issues/detail?id=4945 >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> > > > -- Lukas Renggli www.lukas-renggli.ch

Nov. 1, 2011

Re: [Pharo-project] Brainstorming on the roadmap for first Pharo Consortium Engineer :)

by Benjamin

On Oct 31, 2011, at 9:56 PM, Mariano Martinez Peck wrote: > - Once again... I would LOVE to have a really working-out-of-the-box multithreaded FFI with callbacks. > This is a MUST if Pharo wants to be business friendly. > > - Unify the VMs. Have only ONE place where a single pharo user can go and pickup a VM. Have ANOTHER place for those bleeding edge or experiment VMs. > This means merging gforge, jenkins, pharo website, pharo one click, etc. > In addition, we need a way to IDENTIFY a VM. So that when someone reports a bug, we can exactly know which VM to reproduce it. > > - Integrate Nautilus with RB. Nobody (ok, most of us) cannot work without RB integration. Ok, integrations could live without that, but they INTEGRATE. If you are DEVELOPING you cannot develop without RB. If nobody will make OB to work in 1.4, then someone needs to integrate Nautilus with RB, otherwise people will stick with 1.3 and never change. I am on it, but it's long, i have to understand fully how it works, and since I never really used it (I am still a newbie ^^) it's not so easy. Moreover I have to go through OB code which is still obscure to me. But it progresses step by step :) Ben > - Make development really tools work in Pharo 1.4: OCompletion, Shout > > - Continue pushing Coral, Zinc, Ocean, DBXTalk, Fuel, Nautilus, etc. > > - Maintain issue tracker: let's give Marcus a rest. This means tagging issues, close them, validate, etc etc etc. > > Cheers > > On Mon, Oct 31, 2011 at 8:25 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > I can't take credit for thinking of the bridge, I was simply acknowledging it and the breadth of its audience as part of my shameless attempt to direct effort toward another feature that would get a lot of use :) > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Sean P. DeNigris [sean(a)clipperadams.com] > Sent: Monday, October 31, 2011 3:22 PM > To: pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Brainstorming on the roadmap for first Pharo Consortium Engineer :) > > Schwab,Wilhelm K wrote: > > > > The object-c bridge is probably a big deal to the Mac users among us, > > right? > > Yes! Thank you for the reminder, I'd temporarily given up and forgotten > about this. A stable, well-documented ObjC bridge would be /huge/. My > inability to effectively use it was one of the key drivers in my delving > into debugging the VM. Like FFI, I think documentation will be extremely > important here. > > Sean > > -- > View this message in context: http://forum.world.st/Brainstorming-on-the-roadmap-for-first-Pharo-Consorti… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > > -- > Mariano > http://marianopeck.wordpress.com >

Nov. 1, 2011

[Pharo-project] Goods Test Runner Pharo 1.3 Issues

by mail list

I am trying to deploy a Pharo 1.3 image using Goods and running into some basic issues where my objects are not persisted by reachability. eg I put dictionary x at root under a key 'test' eg db root at: 'test' put x. db commit. Then at x i updated instance variable and add something to its dictionary and committ eg x intancevariable y at: 'key' put 'zzzz' db commit looking at the root x does not get updated with y. I have the majority of the test cases pasing except for testIdentitySet and testFlushAllRemovesAllUnreferenced. In testIdentitySet the following failure | set x y y2 | set := KKIdentitySet database: dbOne. x := 1@1. y := 2@2. set add: x. set add: y. self assert: (set includes: x). self assert: (set includes: y). self deny: (set includes: 1@1). -->fails set = (2@2,1@1) so it seems to think that x and 1@1 are the same. Which to me seems correct but I may be misunderstanding the testcase. Any thoughts or pointers to update my mistakes in using Goods db would be helpful. S. On Oct 31, 2011, at 5:49 PM, Marcus Denker wrote: > 13320 > ----- > > Issue 4945: Weird Settings filtering > http://code.google.com/p/pharo/issues/detail?id=4945 > > -- > Marcus Denker -- http://marcusdenker.de > >

Nov. 1, 2011

Re: [Pharo-project] Brainstorming on the roadmap for first Pharo Consortium Engineer :)

by Schwab,Wilhelm K

Excellent news! ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] Sent: Monday, October 31, 2011 4:58 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Brainstorming on the roadmap for first Pharo Consortium Engineer :) When igor release athens, we will really ask him to get a 100% fully working FFI will be the most important task Stef On Oct 31, 2011, at 8:04 PM, Schwab,Wilhelm K wrote: > The object-c bridge is probably a big deal to the Mac users among us, right? My understand is that there are quite a few of you?? I've thought about it myself, but that's another story. > > For external interfacing, I would very much like to see callbacks widely supported; I'm thinking of solvers/minimizers etc., where one needs to tell the library how to evaluate a function. FFI has been pretty good to me, and Andreas described something that might be turned into a reusable callback mechanism for it. Alien and NativeBoost are also options. It would be nice if we had one external interface system that does it all. > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Noury Bouraqadi [bouraqadi(a)gmail.com] > Sent: Monday, October 31, 2011 11:17 AM > To: Pharo-project(a)lists.gforge.inria.fr > Cc: A friendly place where any question about pharo is welcome > Subject: Re: [Pharo-project] Brainstorming on the roadmap for first Pharo Consortium Engineer :) > > What about adding to this todo list: > > -Fixing/finishing the Objective-C bridge :-) > During ESUG 2010 Esteban told me that there was a pb with the Mac VM that causes the crash. > I believe this wasn't fixed and this is the biggest issue with the MARS project. > > Noury > On 31 oct. 2011, at 11:54, StÃ©phane Ducasse wrote: > >> Hi guys >> >> we have a roadmap for Esteban and we would like to share it with you. We have extra items that we would like to see fixed and we are welcoming your >> feedback/suggestions. Note this is typically the way we want to work with the consortium in the future: >> Build an initial roadmap and refine it based on the input of the community. >> >> - A website for the consortium registration (esteban is expert on that). >> - This is important for INRIA and for the visibility of the consortium. We should get new members :) >> - Integration with SmalltalkHub >> >> - Working on fixing bugs! >> - Debugger fixes >> - Continuous bug fixing. >> >> - Improving release process: faster, more people involved, simpler. >> - Working on metacello repositories for each distributions (everything is there but missing last bits) >> - Metacello tools >> - Automatic release validations >> - Automatic validation of fixes >> >> Now the free items with probably igor involvement >> - Multiwindowing support >> - Fully working multithreaded FFI with ***Documentation*** >> - Filesystem fix and integration >> - Integration of OPAL >> - RPackage integration >> >> Igor related >> - Ephemerons >> - Object format >> - VM branding >> - Use of new canvas >> - Event cleaning >> >> So we are waiting for your suggestions. >> >> >> Stef >> >> >> >> > > Noury > -- > http://twitter.com/#!/NouryBouraqadi > > > > > > >

Nov. 1, 2011