April 2015 - Pharo-users - lists.pharo.org

exception handling problem when running tests in Nautilus

by Otto Behrens

Hi, Thanks everyone for the new Pharo and all the work done. I like Spotter! I gave Pharo 4 a try today and ran into a problem with running tests in a TestCase (test class -> run tests). I just get the debugger popping up with WARequestContextNotFound. In the setUp of our test case, we call WACurrentRequestContext value, but handle the error when we do not have a context, for example: [ WACurrentRequestContext value. true ] on: WARequestContextNotFound do: [ :e | false ] This handler: "[ :e | false ]" is never called. What influences this is the exception handling in: AbstractNautilusUI >> #runTestsOfClass:notifying: Firstly, I think that it may be slighly better to call "e pass" or "e outer" in stead of "e defaultAction", as this would give another outer handler a chance to do something. The defaultAction is called when there are no more outer handlers anyway. After trying this, it did not help my cause. And I think that this is because the WACurrentRequestContext is a Notification and not an Error. I then replaced Exception with Error in the handler in AbstractNautilusUI. This seem to work. What also works is to completely remove the exception handling in AbstractNautilusUI >> #runTestsOfClass:notifying: What is a bit strange is the inconsistency in this exception handling when running a suite or an individual test. Perhaps this kind of code could be better on the TestSuite and not in the Nautilus UI? Can anyone please help? Should I be doing something else? Cheers Otto

April 19, 2015

Looking for Magritte example: MAAddress, MAPerson...

by stepharo

Hi guys long time ago Magritte was shipped with examples such as MAAddress and MAPerson. Does anybody have an idea? Stef

April 19, 2015

Re: [Pharo-users] Polygons + Skybox in woden?

by Yuriy Tymchuk

> On 16 Apr 2015, at 22:51, stepharo <stepharo(a)free.fr> wrote: > > >> Uhh.. >> >> I Woden still developed? Because I thought that Object Profile was working on it. Otherwise maybe we should switch to the CodeCity engineâ¦ it seems to have more âsupportâ. > > what is the codeCity engine? > you want to reinvent all the effort ronie put in woden? No, our aim is not to create a 3D graphics framework. But we meed to draw 3d boxes and few more entities somehow. Iâve mentioned Codecity because itâs usually easy to get a response from Ricky and at the moment of written, I was really perplexed with the answer. Iâm not expecting code owners to do someone elseâs job. For example Ronieâs answer was really cool. But if someone would tell that Ronie ran away and no one knows how Woden works - itâs ok too, as different things happen. But imagine that you ask: âDoes QualityAssistant fix critics automatically?â and Michele answers: âNo idea, but you should check and let us knowâ Maybe I am expecting too much responsibility, in this case please forgive me. Uko > > Stef > >> >> Uko >> >>> On 16 Apr 2015, at 15:11, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >>> >>> No idea, but let us know! >>> >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>>> On Apr 16, 2015, at 4:41 AM, Lusa Nicolas <nicolas.lusa(a)usi.ch <mailto:nicolas.lusa@usi.ch>> wrote: >>>> >>>> Hello, >>>> >>>> I am Nicolas Lusa from university of Lugano and I am working on my master thesis with the supervision of Yuriy Tymchuk. >>>> Right now I am working with woden and I am trying to build polygons. >>>> Question1: Is it possible somehow to build polygons in woden? >>>> >>>> If not: >>>> I know woden is based on OpenGL and I also know that in OpenGL is possible to draw polygons with GL_POLYGON and a given array of points. >>>> Question2: How could I use GL_POLYGON through woden for my purpose? >>>> >>>> Moreover, I would like to put some sort of skybox in my scene. Apparently it's not possible yet, so my question is how could I do that? >>>> >>>> Thanks in advance. >>>> Cheers. >>>> Nicolas >>> >> >

April 18, 2015

Re: [Pharo-users] [Bulk] Re: Fwd: Fwd: Debris' Quuve - Technologies used

by stepharo

And BTW I would really like to see how we can do crude with magritte-described objects. Le 18/4/15 21:37, stepharo a Ã©crit : > > > Le 18/4/15 20:04, Yanni Chiu a Ã©crit : >> On Apr 18, 2015, at 2:18 AM, stepharo <stepharo(a)free.fr> wrote: >> >>> I found strange that not a single little improvements of Magritte >>> was necessary for the Qude project. >> Itâs not strange to me, because when working with Magritte 2, it >> seemed that almost everything I wanted to do had a hook method to >> override, or an obvious place to subclass or extend. So much so, that >> when I could not find the extension point, I thought it was my fault. >> What was missing was instance-based descriptions, which was added by >> the community in Magritte 3. > > :) > >> >> Given how well-factored Magritte 2 was, my deduction was that a lot >> of effort had already been done to extract out an open-source >> artefact, from whatever system drove itâs development. So, no >> surprise that few improvements to the core Magritte were needed. > > Ok so we have perfect software. Good to know. >>> Now if heavy users of open-source libraries do not enhance these >>> open-source libraries and keep their extensions >>> under close source then the open-source libraries will never make >>> progress and I will immensely sad. >> Given that Magritte is already well-factored for extensions, what >> tends to be written is exactly the custom code which you would not be >> releasing to open-source. > > but you see I did not use magritte since long time. It would be great > to have example of custom-code. > For example are relationships any useful. >> >> However, there might be a case for add-ons, such as Twitter Bootstrap >> support. As mentioned in another post, changing the Magritte >> API/interfaces at this point is tricky, because it would affect >> current users - thatâs the conundrum: success and wider adoption will >> constrain the evolution. > We have versions to help there. > >> The addition of instance-based descriptions was worth the (minor) >> pain of the transition, but what level of pain would be tolerable to >> add Bootstrap support, especially if youâre not using Bootstrap. > But we are talking about SeasideMagritte here? > I do not know because I do not have experience. > I was talking about magritte. > > > >

April 18, 2015

Re: [Pharo-users] [Bulk] Re: Fwd: Fwd: Debris' Quuve - Technologies used

by stepharo

Le 18/4/15 20:04, Yanni Chiu a Ã©crit : > On Apr 18, 2015, at 2:18 AM, stepharo <stepharo(a)free.fr> wrote: > >> I found strange that not a single little improvements of Magritte was necessary for the Qude project. > Itâs not strange to me, because when working with Magritte 2, it seemed that almost everything I wanted to do had a hook method to override, or an obvious place to subclass or extend. So much so, that when I could not find the extension point, I thought it was my fault. What was missing was instance-based descriptions, which was added by the community in Magritte 3. :) > > Given how well-factored Magritte 2 was, my deduction was that a lot of effort had already been done to extract out an open-source artefact, from whatever system drove itâs development. So, no surprise that few improvements to the core Magritte were needed. Ok so we have perfect software. Good to know. >> Now if heavy users of open-source libraries do not enhance these open-source libraries and keep their extensions >> under close source then the open-source libraries will never make progress and I will immensely sad. > Given that Magritte is already well-factored for extensions, what tends to be written is exactly the custom code which you would not be releasing to open-source. but you see I did not use magritte since long time. It would be great to have example of custom-code. For example are relationships any useful. > > However, there might be a case for add-ons, such as Twitter Bootstrap support. As mentioned in another post, changing the Magritte API/interfaces at this point is tricky, because it would affect current users - thatâs the conundrum: success and wider adoption will constrain the evolution. We have versions to help there. > The addition of instance-based descriptions was worth the (minor) pain of the transition, but what level of pain would be tolerable to add Bootstrap support, especially if youâre not using Bootstrap. But we are talking about SeasideMagritte here? I do not know because I do not have experience. I was talking about magritte.

April 18, 2015

Re: [Pharo-users] Pillar used directly from Pharo

by Cyril Ferlicot

Hi ! You can use it from Pharo but it's a little complicated if you want to add a configuration file (pillar.conf). I can't explain now because I'm at a ceremony but when I'll have time I'll add the list of the commandes ! Le samedi 18 avril 2015, Jan ValÃ¡Å¡ek <valasja7(a)fit.cvut.cz> a Ã©crit : > Hi there, > > I'd like to ask you, whether is here a way to use pillar internally, > directly from Pharo and how to use it properly. I have found some > tutorials how to use it from linux/windows command prompt, however, I'd > prefer to call it in my program in pharo. > > > > Something like this -> > ----------------------- > header := pillarHeaderObject new. //creating pillar objects directly > from my program > header text:'Title of my page'. > aPillarDocument add: header. //adding them to the whole document > object > > and finally > > aPillarDocument exportToLatex. //export the document > ---------------------- > > > > or I can just write the text in the pillar notation to "myTextObject" > and then call something like-> > ------- > pillarParseAndExportToLatex: myTextObject. > ------- > > Is here a way to do this? > > Thanks for your help :-) > John. > > -- Cheers Cyril Ferlicot

April 18, 2015

Re: [Pharo-users] [Bulk] Re: Fwd: Fwd: Debris' Quuve - Technologies used

by Yanni Chiu

On Apr 18, 2015, at 2:18 AM, stepharo <stepharo(a)free.fr> wrote: > I found strange that not a single little improvements of Magritte was necessary for the Qude project. Itâs not strange to me, because when working with Magritte 2, it seemed that almost everything I wanted to do had a hook method to override, or an obvious place to subclass or extend. So much so, that when I could not find the extension point, I thought it was my fault. What was missing was instance-based descriptions, which was added by the community in Magritte 3. Given how well-factored Magritte 2 was, my deduction was that a lot of effort had already been done to extract out an open-source artefact, from whatever system drove itâs development. So, no surprise that few improvements to the core Magritte were needed. > Now if heavy users of open-source libraries do not enhance these open-source libraries and keep their extensions > under close source then the open-source libraries will never make progress and I will immensely sad. Given that Magritte is already well-factored for extensions, what tends to be written is exactly the custom code which you would not be releasing to open-source. However, there might be a case for add-ons, such as Twitter Bootstrap support. As mentioned in another post, changing the Magritte API/interfaces at this point is tricky, because it would affect current users - thatâs the conundrum: success and wider adoption will constrain the evolution. The addition of instance-based descriptions was worth the (minor) pain of the transition, but what level of pain would be tolerable to add Bootstrap support, especially if youâre not using Bootstrap.

April 18, 2015

Pillar used directly from Pharo

by Jan ValÃ¡Å¡ek

Hi there, I'd like to ask you, whether is here a way to use pillar internally, directly from Pharo and how to use it properly. I have found some tutorials how to use it from linux/windows command prompt, however, I'd prefer to call it in my program in pharo. Something like this -> ----------------------- header := pillarHeaderObject new. //creating pillar objects directly from my program header text:'Title of my page'. aPillarDocument add: header. //adding them to the whole document object and finally aPillarDocument exportToLatex. //export the document ---------------------- or I can just write the text in the pillar notation to "myTextObject" and then call something like-> ------- pillarParseAndExportToLatex: myTextObject. ------- Is here a way to do this? Thanks for your help :-) John.

April 18, 2015

Re: [Pharo-users] [ANN] Pharo 4.0 is released!

by Gaurav Singh

Congrats to all the developers for the amazing work :)

April 18, 2015

Re: [Pharo-users] [ANN] Pharo 4.0 is released!

by Sean P. DeNigris

Offray wrote > Sean, if you're here, have you read Tracing the dynabook [1]? No, thanks for the link! I'll add that to my Dynabook library :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Pharo-4-0-is-released-tp4819877p4820402.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 18, 2015