- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.2] #12295
by Marcus Denker Jan. 10, 2011

Jan. 10, 2011

12295 ----- Issue 3521: StringMorphEditor doesnt work Issue 3514: Failing Test: NewTextMorphTests.testAcceptContents -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3514 in pharo: Failing Test: NewTextMorphTests.testAcceptContents
by pharo＠googlecode.com Jan. 10, 2011

Jan. 10, 2011

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2 New issue 3514 by marcus.denker: Failing Test: NewTextMorphTests.testAcceptContents http://code.google.com/p/pharo/issues/detail?id=3514 NewTextMorphTests.testAcceptContents fails

1 4

[Pharo-project] Issue 3521 in pharo: StringMorphEditor doesn't work
by pharo＠googlecode.com Jan. 10, 2011

Jan. 10, 2011

Status: Accepted Owner: aplantec Labels: Milestone-1.2 New issue 3521 by aplantec: StringMorphEditor doesn't work http://code.google.com/p/pharo/issues/detail?id=3521 Used to edit a StringMorph is the 'string morph are editable' is set to true. Do we need that ?

1 2

[Pharo-project] Pharo sprint @ lille Friday 21 of January
by StÃ©phane Ducasse Jan. 10, 2011

Jan. 10, 2011

Hi guys we will have a pharo sprint at Lille Friday 21 of January. If you want to join let us know that we organize for the food. The sprint will happen in our rooms at LIFL http://rmod.lille.inria.fr/web/pier/contactr/ Stef

3 4

[Pharo-project] Generating ticket (was Re: Generators for Pharo Xmax wish))
by Ralph Boland Jan. 10, 2011

Jan. 10, 2011

> The easiest way to get this code into pharo core is to create a mcz > package, put it on PharoInbox on squeaksource and create a ticket in > code.google.com/p/pharo referencing it and taggint it Fixed, this way > St?phane or Markus can harvest it to the core image. I am clear on how to do this (I am not a Pharo user). I went to: code.google.com/p/pharo and from there I went to squeaksource.com/PharoInbox/feed.rss and subscribed. But I don't see how to add any text to the site. I assume that "ticket" is a bug report but I don't know how to generate one for Pharo. Please send instructions on how to do the above. > If the mcz package is overkill, then a simple fileout of the package in > squeak attached to the ticket will do. > Maybe in the long term a project on squeaksource should be created (if > not exists) and new changes to to it and from there pulled to squeak and > pharo. I believe Andreas Raab originally created a project for generators on squeaksource but it doesn't appear to be there now. Perhaps it was removed once the generators package was incorporated into Squeak. Ralph Boland

3 2

Re: [Pharo-project] 4 days sprints in february
by Marcus Denker Jan. 10, 2011

Jan. 10, 2011

Hi, I will be travelling until the 23rd, so I can't join. On Jan 9, 2011, at 10:25 AM, StÃ©phane Ducasse wrote: > Hi guys > > we are brainstorming with alain plantec to organize a sprint at roscoff (close to brest - excellent sea food). > The set up would be: > - 21 - 24 of february - this is holiday time here. I will rent a house with the kids there. > - we can get access to a room for 450 Euros (break included). > - the hosting is 50 Euros per day breakfast included - lunches are about 15 euros. > > So are some of you interested by participating. We could ask some sponsoring to ESUG. > > http://maps.google.fr/maps?client=safari&rls=en&q=roscoff&oe=UTF-8&redir_es… > > http://www.google.fr/images?client=safari&rls=en&q=roscoff&oe=UTF-8&redir_e… > > Stef -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] How to display an image from an external PNG/JPG file in a Morph?
by Dimitry Golubovsky Jan. 10, 2011

Jan. 10, 2011

Hi, Maybe a silly question, but is there an example of displaying an image from an external file in a Morph? A sample package/class source, or a wiki page would be fine. Or just a step-by-step description of the process. I am guessing that I have to create a Form first (that is, from the picture file), but could not find which method to use. Thanks for any suggestions. -- Dimitry Golubovsky Anywhere on the Web

2 2

[Pharo-project] bootstrapping Order ...
by James Ladd Jan. 10, 2011

Jan. 10, 2011

Hi All, I'm wondering where I can find information or if anyone knows off hand what the order of bootstrapping would be if the image had to be created from scratch? As I see it, there are dependencies between Object -> Class and so forth. Rgs, James.

1 0

[Pharo-project] Using Open Sound Control with Pharo 1.1.1 one click
by Andy Burnett Jan. 10, 2011

Jan. 10, 2011

Hello I am trying to create some simple controls for an OSX Quartz Composer application. The app supports Open Sound Control - basically UDP multicast commands. I managed to load the OSC package from squeak source using Pharo 1.0. But I couldn't get UDP to work - the system report a Prim Failure. I updated to 1.1.1 and OSC now fails to load, due to a syntax error. Before I dig into this any further, I need to know whether UDP is actually working under Pharo - searching the list archive showed messages saying it was broken, but the bug tracker doesn't show it as a bug. Can anyone enlighten me? Cheers Andy

1 0

Re: [Pharo-project] [squeak-dev] Re: [Seaside-dev] Seaside and exception behaviour
by Julian Fitzell Jan. 9, 2011

Jan. 9, 2011

Hi Andreas, A neat approach, but I don't think it quite works (yet, anyway). Although it has the correct behaviour when the exception action is invoked, it doesn't behave correctly for #defaultAction. According to 5.5.2.1 in the spec, "The #defaultAction method is executed in the context of the signaling environment." So, taking an example of an existing #defaultAction method that signals an exception: [ Error signal ] on: UnhandledError do: [ :ex | 'ANSI says so' ] returns 'ANSI says so' without your change but brings up a debugger with it. Julian On Sat, Jan 8, 2011 at 7:34 PM, Andreas Raab <andreas.raab(a)gmx.de> wrote: > Thanks for the test case. I've posted a possible fix for Squeak to the inbox > (Kernel-ar.540) but I'd like people to review the change first since it's a > fairly critical part of the system. I'd appreciate if someone could look at > the fix and comment on whether that's the sensible thing to do. > > Cheers, > Â - Andreas > > On 1/8/2011 6:02 PM, Julian Fitzell wrote: >> >> On Wed, Jan 5, 2011 at 8:15 AM, Paolo Bonzini<bonzini(a)gnu.org> Â wrote: >>> >>> On 01/05/2011 04:58 PM, mkobetic(a)cincom.com wrote: >>>> >>>>>> Â Here's maybe a bit more concise example. If you run the thing below >>>>>> in a workspace, >>>>>> Â it returns 'Squeak' in Squeak and 'VW' in VW >>>>>> >>>>>> Â [ Â [ Â Â Â [ Â Â Â self error: 'trigger error' >>>>>> Â Â Â Â Â Â ] on: ZeroDivide do: [ :ex | 'Squeak' ] >>>>>> Â Â ] on: Error do: [ :ex | 3 / 0 ] >>>>>> Â ] on: ZeroDivide do: [ :ex | 'VW' ] >>>>> >>>>> Â It returns 'Squeak' on GNU Smalltalk. Â This is consistent with my >>>>> Â analysis of Alan's snippet. Â Unfortunately I don't have at hand my >>>>> copy >>>>> Â of the standard. >>>> >>>> FWIW, Smalltalk/X returns 'VW' >>> >>> That's the correct behavior. Â The standard says the search should proceed >>> from the last exception handler that was created up to the oldest. >> >> Agreed. Â The ANSI standard seems quite clear about that: >> >> 5.4.3.3: "If signaling of an exception results in evaluation of action >> the evaluation will occur in the context of the handler environment." >> >> 5.5.2.1: "If a matching handler is found, the exception action of the >> handler is evaluated in the exception environment that was current >> when the handler was created and the state of the current exception >> environment is preserved as the signaling environment." >> >>> (That said, Squeak/gst's behavior is quite easy to justify, as stack >>> unwinding hasn't happened yet. Â I'll wait for this thread to settle >>> before >>> changing it in gst). >> >> But stack unwinding shouldn't need to happen until one of the #on:do: >> calls is actually ready to return. Until then, its all just searching. >> >> I think Squeak/Pharo's problem is that it doesn't maintain a first >> class "exception environment" as described by the glossary in the ANSI >> standard: "An abstract entity that is a LIFO list of exception >> handlers. An exception environment may be logically searched starting >> from the most recently "pushed" exception handler." >> >> Squeak/Pharo simply (ab)uses the context chain, walking it looking for >> the next handler (see the implementation of #signal, which always >> starts searching from thisContext). This works fine most of the time >> but not when you need to temporarily restore a previous exception >> environment. #handleSignal: does go to the effort of setting a >> handlerContext on the signaled exception before calling the action >> block. This is necessary to implement #pass, #isNested, and so on but >> would also need to be put somewhere that #signal could get at it to >> use as a starting point for the search. >> >> This seems like a squeak/pharo bug to me. I don't much feel like >> fixing it in Grease given that Grease is supposed to assume correct >> ANSI implementation as a pre-requisite. Perhaps we can broker a deal >> where Squeak/Pharo will fix this and VW (finally) fixes its signaling >> behaviour so we can drop GRError, etc. entirely. >> >> In the meantime, though, how would we fix the Seaside code assuming we >> had ANSI-correct exception handling implementations? >> >> Julian >> >> > > >

1 0