- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [COTDC] 84#2- MCMergeRecord
by laurent laffont Sept. 14, 2011

Sept. 14, 2011

Today: MCMergeRecord Laurent On Sat, Sep 10, 2011 at 9:32 AM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Today: FreeTypeCacheLinkedList > > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent >

1 0

[Pharo-project] PetitParser + Amber
by Frank Shearar Sept. 14, 2011

Sept. 14, 2011

Hi GÃ¶ran, Quick question: during your work on Amber, did you find any particularly slow parts of PetitParser? Or, rephrased: while a hand-written parser is pretty much guaranteed to run faster than PetitParser (or any general parser generator, I reckon), are there any parts of PetitParser that leap out as being ripe for optimisation? Thanks, frank

6 6

[Pharo-project] PetitParser + Amber
by Torsten Bergmann Sept. 14, 2011

Sept. 14, 2011

GÃ¶ran wrote: >Amber is pretty slow compared to raw js Let's see what Dart provides compared to js ... and if its Smalltalk/Amber like (see [1] and [2]) Bye T. [1] http://astares.blogspot.com/2011/09/one-month-until-dart-is-released.html [2] http://astares.blogspot.com/2011/09/more-rumors-on-dart-and-smalltalk.html -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

1 0

[Pharo-project] [update 1.4] #14140
by Marcus Denker Sept. 14, 2011

Sept. 14, 2011

14140 ----- Issue 4796: Fix ClassSearch http://code.google.com/p/pharo/issues/detail?id=4796 Issue 4794: New method in AbstractTool http://code.google.com/p/pharo/issues/detail?id=4794 Issue 4789: Improve the way morphs communicate with model http://code.google.com/p/pharo/issues/detail?id=4789 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [CI-Server] Hudson discontinued Oct 1st
by Marcus Denker Sept. 14, 2011

Sept. 14, 2011

Hello, We have right now two integration setups: Hudson. Old https://pharo-ic.lille.inria.fr/hudson/ Jenkins. New https://ci.lille.inria.fr/pharo/ Running two setups is very confusing for everyone. Therefore, the old one will be turned *OFF* Oct 10th. All important projects will be migrated before that to Jenkins. Marcus -- Marcus Denker -- http://marcusdenker.de

1 0

Re: [Pharo-project] Pharo One Click 1.3 LNK file
by Marcus Denker Sept. 14, 2011

Sept. 14, 2011

On Sep 14, 2011, at 8:28 AM, Sven Van Caekenberghe wrote: > > On 14 Sep 2011, at 08:19, Marcus Denker wrote: > >> The One-Click here: >> >> https://gforge.inria.fr/frs/download.php/28922/Pharo-1.3-OneClick.zip >> >> Does not use a LNK File, it just has the exe in the main directory. And current VMs. >> >> (Yes, and the one click on the Build server is out of date... maybe we should remove it for now to have less confusion) > > Yeah, I saw that I had two different versions on my machine, not sure what the most recent was I followed the one on the page, > > http://www.pharo-project.org/pharo-download/release-1-3 > > to > > https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.3/lastSucce… > > The one fresh of the build server should be the latest no ? That is using the LNK file though. > Latest from the image yes. VMs: no. Yes, this is all confusing and needs to be fixed... and the whole Hudson build server needs to be discontinued, ASAP. (It's very confusing to have two. We are really good at doing very confusing things... we need to improve that). Marcus -- Marcus Denker -- http://marcusdenker.de

2 1

Re: [Pharo-project] Pharo One Click 1.3 LNK file
by Marcus Denker Sept. 14, 2011

Sept. 14, 2011

On Sep 13, 2011, at 9:00 PM, Sven Van Caekenberghe wrote: > There is a problem with the current Pharo One Click 1.3 LNK (.lnk) file on Windows. > > It refers to non existing paths and thus does not work. > > More specifically the 'Target' and 'Starts In' fields are wrong. > > I know close to nothing about Windows, can somebody else help here ? > > Ideally these should refer relatively to the right directories, so that when the containing directory changes its name or is moved things don't break. Similar to what the Linux .sh script does. > > An additional problem is that these one click artifacts are built on Linux where the .lnk file probably cannot be edited. > The One-Click here: https://gforge.inria.fr/frs/download.php/28922/Pharo-1.3-OneClick.zip Does not use a LNK File, it just has the exe in the main directory. And current VMs. (Yes, and the one click on the Build server is out of date... maybe we should remove it for now to have less confusion) Marcus -- Marcus Denker -- http://marcusdenker.de

2 1

Re: [Pharo-project] Downloading configuration on Pharo1.3 and Pharo1.4 freezes my image
by Marcus Denker Sept. 14, 2011

Sept. 14, 2011

On Sep 14, 2011, at 4:29 AM, Guillermo Polito wrote: > Hi! > > Some students had their Pharo1.3 and Pharo1.4 images freezed when executing the following script: > > Gofer it > squeaksource: 'ObjectBrowser'; > package: 'ConfigurationOfObjectBrowser'; > load. > > (ConfigurationOfObjectBrowser project version: #bleedingEdge) load > > I've reproduced it with the last images from Hudson/Jenkins, and they allways freeze on the Cleaning up step... > On the other hand, it loads correctly on latest 1.2... > > Does anybody have an idea of what's happening? > I think this is this bug: http://code.google.com/p/pharo/issues/detail?id=4768 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Pharo One Click 1.3 LNK file
by Sven Van Caekenberghe Sept. 14, 2011

Sept. 14, 2011

There is a problem with the current Pharo One Click 1.3 LNK (.lnk) file on Windows. It refers to non existing paths and thus does not work. More specifically the 'Target' and 'Starts In' fields are wrong. I know close to nothing about Windows, can somebody else help here ? Ideally these should refer relatively to the right directories, so that when the containing directory changes its name or is moved things don't break. Similar to what the Linux .sh script does. An additional problem is that these one click artifacts are built on Linux where the .lnk file probably cannot be edited. Sven

2 2

[Pharo-project] MethodContext #tempScopedNames vs #tempAt
by Philippe Marschall Sept. 14, 2011

Sept. 14, 2011

Hi While trying to debug the debugger in Seaside (hi Mike) I stumbled on something funny. Seaside the following code to work: Semaphore forMutualExclusion critical: [ | sender | sender := thisContext sender. sender tempAt: sender tempScopedNames size ] But it doesn't, you get a SubscriptOutOfBounds. #tempScopedNames answers #('mutuallyExcludedBlock' 'blockValue' 'caught'). The method arguments (mutuallyExcludedBlock) can be found in self tempAt: 1 the temps can be found in self tempAt: 2 Which means that sender tempNamed: 'blockValue' will answer #(nil true) instead of the real value (nil). This is very confusing. This is with the latest Pharo 1.3 and Cog .r2489 Cheers Philippe

2 3