June 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Metacello doubt

by Dale K. Henrichs

Guido, If the maintainer of a configuration would like to support bleeding edge loads that propagate through the dependent projects then they should specify which baseline version to use for each dependent project. For Native Boost the entry for AsmJit in the #baseline13: method could be changed to: project: 'AsmJit' with: [ spec className: 'ConfigurationOfAsmJit'; "==>" versionString: #bleedingEdge; repository: 'http://www.smalltalkhub.com/mc/Pharo/AsmJit/main' ]; Then the bleedingEdge load would be propagated through to the dependents ... but then you'd want the AsmJit configuration modified as well:) Dale ----- Original Message ----- | From: "Guido Chari" <charig(a)gmail.com> | To: pharo-dev(a)lists.pharo.org | Sent: Wednesday, June 26, 2013 7:27:19 AM | Subject: [Pharo-dev] Metacello doubt | I have a question since i'm trying to create some jenkins job for the | first time. Sorry if this was already discussed... | I have a dependency with for example NativeBoost. And i want | NativeBoost in its bleedingEdge version. If I "loadBleedingEdge" | NativeBoost is on its last version on every package but not its own | dependencies as for example AsmJit. Is this the right behavior? How | can i express to have not only my dependency but also the | dependencies of my dependencies in its bleedingEdge version?

June 26, 2013

Slide share

by StÃ©phane Ducasse

Hi guys we created a slideshare acount for pharo I added 2009 smalltalks slides 2011 ESUG 2013 Pharo Conference a new lecture Intro Model Syntax http://www.slideshare.net/pharoproject/ Can you tell me if you can see the 2013 pharo conference? Do you know if there are limits on the number of presentations that we can upload, because I see (get public on this presentation => go pro). So I wonder if I want to invest in slideshare.

June 26, 2013

NBGLFrameBuffer>>checkStatus

by Alexandre Bergel

Hi! Apparently, it happens that we get an error "Frame buffer status: Unknown error". The error comes from the method checkStatus: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= NBGLFrameBuffer>>checkStatus | status | self bind. status := gl checkFramebufferStatusEXT: GL_FRAMEBUFFER. status = GL_FRAMEBUFFER_COMPLETE ifFalse: [ #( #GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT #GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT #GL_FRAMEBUFFER_INCOMPLETE_DRAW_BUFFER #GL_FRAMEBUFFER_INCOMPLETE_READ_BUFFER #GL_FRAMEBUFFER_UNSUPPORTED #GL_FRAMEBUFFER_INCOMPLETE_MULTISAMPLE #GL_FRAMEBUFFER_UNDEFINED ) do: [:sym | (self class bindingOf: sym) ifNotNil: [:b | status = b value ifTrue: [ ^ self error: 'Frame buffer is incomplete: ', b key ] ]. ]. ^ self error: 'Frame buffer status: Unknown error'. ]. ^ true "ok" -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Any idea what's going on? We took a Pharo 2.0, loaded Athens, NBOpenGL, SourceCity, and roassal3d. Running the test of roassal3d shows this. I suspect this error comes from some interaction between the tests. Closing an opengl window is enough to desallocate the opengl resources? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 26, 2013

Re: [Pharo-dev] Boolean

by StÃ©phane Ducasse

On Jun 26, 2013, at 5:38 PM, Torsten Bergmann <astares(a)gmx.de> wrote: >> works fine on the latest Pharo 3 because of Opal :) > > So it is not a > > true copy > > ;) > > Anyhow - again my question, should we care and assure > common behavior with covering tests? I'm not sure that it is worth. I would like tests for part of the system that can break or change. > Bye > T. >

June 26, 2013

Re: [Pharo-dev] Boolean

by ClÃ©ment Bera

I guess they are too many ... At some point what would be nice is to define some class and API as 'system' or 'meta' that you can only use if you are in root mode and your project would be in some kind of sandbox. But this is too much work to implement this in a way stable enough for a release.. 2013/6/26 Torsten Bergmann <astares(a)gmx.de> > >works fine on the latest Pharo 3 because of Opal :) > > So it is not a > > true copy > > ;) > > Anyhow - again my question, should we care and assure > common behavior with covering tests? > > Bye > T. > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

June 26, 2013

Boolean

by Torsten Bergmann

>works fine on the latest Pharo 3 because of Opal :) So it is not a true copy ;) Anyhow - again my question, should we care and assure common behavior with covering tests? Bye T.

June 26, 2013

Re: [Pharo-dev] Metacello doubt

by Damien Cassou

On Wed, Jun 26, 2013 at 4:27 PM, Guido Chari <charig(a)gmail.com> wrote: > I have a dependency with for example NativeBoost. And i want NativeBoost in > its bleedingEdge version. If I "loadBleedingEdge" NativeBoost is on its last > version on every package but not its own dependencies as for example AsmJit. > Is this the right behavior? How can i express to have not only my dependency > but also the dependencies of my dependencies in its bleedingEdge version? you can't I guess. Each package maintainer decides what is best for the dependencies. If you want to override this, I still guess you have to make your package depend on all the dependencies of all your dependencies (recursively). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

June 26, 2013

Better Interruption in 2.0

by Stephan Eggermont

10569 Backport 2.0 Better Interruption says Work Needed. What should I look into? I am now loosing hours parsing/building large FAMIX models. Stephan

June 26, 2013

Re: [Pharo-dev] Boolean

by ClÃ©ment Bera

Actually this code: True basicNew ifTrue: [ "some code" ] works fine on the latest Pharo 3 because of Opal :) But nice trick for the old compiler :) 2013/6/26 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > Because you don't know the tricks... This one should be just fine > > True basicNew ifTrue: [ "some code" ] yourself > > > 2013/6/26 ClÃ©ment Bera <bera.clement(a)gmail.com> > >> True basicNew ifTrue: [ "some code" ] >> >> hehe raises NonBooleanReceiver :) >> >> >> 2013/6/26 Camillo Bruni <camillobruni(a)gmail.com> >> >>> why not, let's "forbid" them with an error message! >>> >>> => maybe you can and error to #become: on nil / true / false as well? >>> >>> On 2013-06-26, at 14:20, Torsten Bergmann <astares(a)gmx.de> wrote: >>> >>> > Boolean new -> error >>> > Boolean basicNew -> is possible >>> > >>> > should we care? >>> > >>> >> >> > > > -- > ClÃ©ment BÃ©ra > Mate Virtual Machine Engineer > BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq* >

June 26, 2013

Re: [Pharo-dev] [update 3.0] #30224

by Esteban Lorenzano

June 26, 2013