Re: [Pharo-dev] Slide share

Le 26/06/2013 21:13, Stéphane Ducasse a écrit : > Can you tell me if you can see the 2013 pharo conference? I can see 7 conferences and among them the 2013 pharo conference. Hilaire -- Dr. Geo http://drgeo.eu

Re: [Pharo-dev] Versions Browser over gitfiletree://

> Or ... A first step towards Pharo without a changeset. without Monticello file back-end no? Stef > > Thierry

Re: [Pharo-dev] Boolean

On Jun 27, 2013, at 8:16 AM, Clément Bera wrote: > > In Pharo 3 we will support conditional optimized messages ( #ifTrue:, > #ifFalse:, #ifTrue:ifFalse: and #ifFalse:ifTrue: ) sent on non boolean > receiver. However, this feature will be slow, so one should not use it too > much (as #become:,

Re: [Pharo-dev] Boolean

2013/6/27 Levente Uzonyi > On Wed, 26 Jun 2013, Guillermo Polito wrote: > > >> On Wed, Jun 26, 2013 at 11:20 PM, Levente Uzonyi wrote: >> On Wed, 26 Jun 2013, Clément Bera wrote: >> >> Actually this code: >> True basicNew ifTrue: [ "some code" ] >> works

Re: [Pharo-dev] Boolean

On Wed, 26 Jun 2013, Guillermo Polito wrote: On Wed, Jun 26, 2013 at 11:20 PM, Levente Uzonyi wrote: On Wed, 26 Jun 2013, Clément Bera wrote: Actually this code:  True basicNew ifTrue: [ "some code" ] works fine on the latest Pharo 3 because of Opal :

Re: [Pharo-dev] Versions Browser over gitfiletree://

Cool! I plan to integrate your work soon and I expect to merge your work on the Pharo3.0 branch as well... Dale - Original Message - | From: "GOUBIER Thierry" | To: "Pharo Development List ‎[pharo-dev@lists.pharo.org]‎" | Sent: Wednesday, June 26, 2013 2:28:55 PM | Subject: [Pharo-dev

Re: [Pharo-dev] Metacello doubt

- Original Message - | From: "Guido Chari" | To: "Pharo Development List" | Sent: Wednesday, June 26, 2013 2:49:09 PM | Subject: Re: [Pharo-dev] Metacello doubt | I understood. Thanks for the answer Dale. The drawback in this case | is to specify a particular dependency to AsmJit in my

Re: [Pharo-dev] Better Interruption in 2.0

Using Henry's processToInterrupt "Look for best candidate to interrupt: - any scheduled non-finalization process of lower priority - the weak-finalization process, if scheduled - the UI process Never interrupt the idle process, since killing it

Re: [Pharo-dev] Boolean

On 26 Jun 2013, at 14:20, Torsten Bergmann wrote: > Boolean new-> error > Boolean basicNew -> is possible > > should we care? true, false and nil are special since they are unique constant instances, right ? To support that notion, it would seem to be sensible to restrict creating

Re: [Pharo-dev] Versions Browser over gitfiletree://

I like what I see! :) Esteban A. Maringolo 2013/6/26 GOUBIER Thierry : > Or ... A first step towards Pharo without a changeset. > > Thierry

Re: [Pharo-dev] Metacello doubt

Phil, Check out the System Help ... the API is documented under Metacello>>MetacelloToolBox ... under PrfStef>>Browse tutorials>>Inside Metacello Toolbox there are 5-6 lessons there are other Metacello tutorials there as well ... Dale - Original Message - | From: p...@highoctane.b

Re: [Pharo-dev] Metacello doubt

I understood. Thanks for the answer Dale. The drawback in this case is to specify a particular dependency to AsmJit in my configuration. Also, perhaps is the right way since i realized i have a particular dependency on it. But this discussion makes me thing a little and so i have a new question.

Re: [Pharo-dev] Boolean

On Wed, Jun 26, 2013 at 11:20 PM, Levente Uzonyi wrote: > On Wed, 26 Jun 2013, Clément Bera wrote: > > Actually this code: >> True basicNew ifTrue: [ "some code" ] >> works fine on the latest Pharo 3 because of Opal :) >> > > So the Opal compiler lacks important optimizations. :) > Not at all.

Re: [Pharo-dev] Boolean

On Wed, 26 Jun 2013, Clément Bera wrote: Actually this code:  True basicNew ifTrue: [ "some code" ] works fine on the latest Pharo 3 because of Opal :) So the Opal compiler lacks important optimizations. :) Levente But nice trick for the old compiler :) 2013/6/26 Nicolas Cellier

Re: [Pharo-dev] Boolean

I guess that once detected adding a Lint rule is better than restrictions everywhere.

Re: [Pharo-dev] Metacello doubt

While we are at it, is there any documentation for the MetacelloToolbox? Couldn't find... Saw Sean's thing but nothing else. Would be great! TIA Phil --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:p...@highoctane.be | Web: http://phili

Re: [Pharo-dev] Slide share

This one I can see http://www.slideshare.net/pharoproject/2013-pharo-conference --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:p...@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtu

Re: [Pharo-dev] Metacello doubt

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 chang

[Pharo-dev] Slide share

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

[Pharo-dev] NBGLFrameBuffer>>checkStatus

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_FRAMEB

Re: [Pharo-dev] Boolean

On Jun 26, 2013, at 5:38 PM, Torsten Bergmann 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 lik

Re: [Pharo-dev] Metacello doubt

On Wed, Jun 26, 2013 at 4:27 PM, Guido Chari 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

Re: [Pharo-dev] Boolean

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..

[Pharo-dev] Boolean

>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.

[Pharo-dev] Better Interruption in 2.0

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

Re: [Pharo-dev] Boolean

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 > Because you don't know the tricks... This one should be just fine > > True basicNew ifTrue: [ "some code" ] yoursel

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

^&%$#^ not yet... I catched an error. rollback and retry :) On Jun 26, 2013, at 4:23 PM, Esteban Lorenzano wrote: > 30224 > - > > 6757 Should enable the new class organizer > https://pharo.fogbugz.com/f/cases/6757/ > > Finally :) > Thanks Ben for the work and to all for the testin

[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

[Pharo-dev] [update 3.0] #30224

30224 - 6757 Should enable the new class organizer https://pharo.fogbugz.com/f/cases/6757/ Finally :) Thanks Ben for the work and to all for the testing. Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Traits-EstebanLorenzano.519.diff http://smalltalkhub.com/mc/Pharo

Re: [Pharo-dev] HandMorph startup is fun

> Welcome in my world :P like the new depeche mode :) We will slowly systematically clean. stef > > Ben > > On Jun 26, 2013, at 2:48 PM, Stéphane Ducasse > wrote: > >> startUp >> >> self clearCompositionWindowManager >> >> and guess what :) >> >> clearCompositionWindowManager is n

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

On Jun 26, 2013, at 9:08 AM, kilon wrote: > Sure Damien I will try to unistall the libraries and try again and report the > error. > > Stephan why the website does not have a donate button ? Or you could even > try kickstarter. I am not claiming I know how these things work but maybe > its wor

[Pharo-dev] Smalltalkhub maintenance tomorrow

Hi guys, I will perform an update of SmalltalkHub tomorrow at 2pm Paris time. There might be a very short downtime of a minute or so, but I'll do my best to avoid any downtime at all. Cheers, Nico

Re: [Pharo-dev] Boolean

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 > True basicNew ifTrue: [ "some code" ] > > hehe raises NonBooleanReceiver :) > > > 2013/6/26 Camillo Bruni > >> why not, let's "forbid" them with an error m

Re: [Pharo-dev] [ANN]: Pharo x.5

DeNigris Sean wrote: > Are you both impatient and conservative (and apparently confused) like me? > I want to use the stable release of Pharo with the best new features of > the alpha version. Also, do you ever think of cool enhancements to the IDE > that for whatever reason have not made it into

[Pharo-dev] looking at the code of PasteUpMorph

Hi I think that it would be good to have PasteUpMorph (a morph in which we can drop morph) subclass World (the world = a morph in which we can drop morph and that have a worldstate) This would remove a lot of ifNil: everywhere. Stef

[Pharo-dev] DebugShowDamage seems broken between 30143 and 223

Hi guys could you enable the preference Flash damaged morphic region? Because on 30143 is works but not on 223. Stef

Re: [Pharo-dev] Boolean

True basicNew ifTrue: [ "some code" ] hehe raises NonBooleanReceiver :) 2013/6/26 Camillo Bruni > 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 wrote: > > > Boolean ne

Re: [Pharo-dev] HandMorph startup is fun

Welcome in my world :P Ben On Jun 26, 2013, at 2:48 PM, Stéphane Ducasse wrote: > startUp > > self clearCompositionWindowManager > > and guess what :) > > clearCompositionWindowManager is not implemented…. > > Alain is just disturbing me with all kinds of bogus morphic code :) > > St

Re: [Pharo-dev] Boolean

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 wrote: > Boolean new-> error > Boolean basicNew -> is possible > > should we care? >

[Pharo-dev] HandMorph startup is fun

startUp self clearCompositionWindowManager and guess what :) clearCompositionWindowManager is not implemented…. Alain is just disturbing me with all kinds of bogus morphic code :) Stef

[Pharo-dev] Boolean

Boolean new-> error Boolean basicNew -> is possible should we care?

[Pharo-dev] [regression reporter]regression occurred

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=win/263/ 4 regressions found. CollectionsTests.Strings.StringTest.testWriteStreamConvertsToWideString KernelTests.Numbers.NumberTest.testUnCategorizedMethods CollectionsTests.Strings.StringTest.testAt CollectionsTests

[Pharo-dev] [regression reporter]regression occurred

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=mac/263/ 4 regressions found. CollectionsTests.Strings.StringTest.testWriteStreamConvertsToWideString KernelTests.Numbers.NumberTest.testUnCategorizedMethods CollectionsTests.Strings.StringTest.testAt CollectionsTests

[Pharo-dev] [regression reporter]regression occurred

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=linux-stable-worker/263/ 4 regressions found. CollectionsTests.Strings.StringTest.testWriteStreamConvertsToWideString KernelTests.Numbers.NumberTest.testUnCategorizedMethods CollectionsTests.Strings.StringTest.testAt

[Pharo-dev] [update 3.0] #30223

30223 - 10950 Smart Suggestions should use Opal for parsing https://pharo.fogbugz.com/f/cases/10950 11025 Integrate the new version of the debugger https://pharo.fogbugz.com/f/cases/11025 11001 reduce shadowed args https://pharo.fogbugz.com/f/cases/110

Re: [Pharo-dev] Help wanted! Test new class organizer.

On 26 juin 2013, at 13:34, Esteban Lorenzano wrote: > > On Jun 26, 2013, at 1:22 PM, Camille Teruel wrote: > >> >> On 26 juin 2013, at 12:54, Esteban Lorenzano wrote: >> >>> Hi >>> >>> I finished the integration of the new class organizer, and I need people >>> who can test it before inte

Re: [Pharo-dev] Nautilus category filter

It should still be available since it's implemented on PluggaleListMorph Ben On Jun 26, 2013, at 12:54 PM, Torsten Bergmann wrote: > Back in the days the Nautilus Browser had a "filter" text field > directly above the category pane. One just had to click and > enter the name and the list got f

Re: [Pharo-dev] Help wanted! Test new class organizer.

On Jun 26, 2013, at 1:22 PM, Camille Teruel wrote: > > On 26 juin 2013, at 12:54, Esteban Lorenzano wrote: > >> Hi >> >> I finished the integration of the new class organizer, and I need people who >> can test it before integration. >> Please, merge the SLICE 6757 > > Tested and approved

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

On 26 juin 2013, at 13:30, Marcus Denker wrote: > > On Jun 26, 2013, at 1:26 PM, Camille Teruel wrote: > >> >> On 26 juin 2013, at 13:18, Marcus Denker wrote: >> >>> 11012 Object>>isComplex is related to complex number >>> https://pharo.fogbugz.com/f/cases/11012 >> >> This one is a dupl

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

On Jun 26, 2013, at 1:26 PM, Camille Teruel wrote: > > On 26 juin 2013, at 13:18, Marcus Denker wrote: > >> 11012 Object>>isComplex is related to complex number >> https://pharo.fogbugz.com/f/cases/11012 > > This one is a duplicate of issue 10971. > 10971 also remove Number>>#arg that is

[Pharo-dev] [regression reporter]regression occurred

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=win/262/ 2 regressions found. KernelTests.Numbers.NumberTest.testUnCategorizedMethods Tests.Release.ReleaseTest.testObsoleteClasses

[Pharo-dev] [regression reporter]regression occurred

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=mac/262/ 1 regressions found. KernelTests.Numbers.NumberTest.testUnCategorizedMethods

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

On 26 juin 2013, at 13:18, Marcus Denker wrote: > 11012 Object>>isComplex is related to complex number > https://pharo.fogbugz.com/f/cases/11012 This one is a duplicate of issue 10971. 10971 also remove Number>>#arg that is a nonsense in the absence of complex numbers.

Re: [Pharo-dev] Help wanted! Test new class organizer.

On 26 juin 2013, at 12:54, Esteban Lorenzano wrote: > Hi > > I finished the integration of the new class organizer, and I need people who > can test it before integration. > Please, merge the SLICE 6757 Tested and approved señor! Only one question why the AllProtocol is a subclass of Proto

[Pharo-dev] [update 3.0] #30222

30222 - 11017 Eye inspector and Object explorer not compatible https://pharo.fogbugz.com/f/cases/11017 11012 Object>>isComplex is related to complex number https://pharo.fogbugz.com/f/cases/11012 11016 Failing Inspector Tests https://pharo.fogbugz.com/

[Pharo-dev] Help wanted! Test new class organizer.

Hi I finished the integration of the new class organizer, and I need people who can test it before integration. Please, merge the SLICE 6757 https://pharo.fogbugz.com/f/cases/6757/ and after that execute this script: Smalltalk allClassesAndTraitsDo: [:c || org proOrg | org := c theNonMe

[Pharo-dev] Nautilus category filter

Back in the days the Nautilus Browser had a "filter" text field directly above the category pane. One just had to click and enter the name and the list got filtered. With more and more packages coming into an image this was very usefull in Nautilus since it allowed to filter the displayed. The T

Re: [Pharo-dev] [Pharo-project] Understanding NBOpenGL

My code gl shaderSource_shader: shader count: 1 string: shaderString length: 0. must not be correct. I try to translate this glShaderSource(shader, 1, &strFileData, NULL); using the tutorial in here -> http://www.arcsynthesis.org/gltut/Basics/Tut01%20Making%20Shaders.html

[Pharo-dev] removing griddedPoint: from Morph

Hi guys I would like to remove griddedPoint: ungriddedPoint | griddingContext | self flag: #arNote. "Used by event handling - should transform to pasteUp for gridding" (griddingContext := self pasteUpMorph) ifNil: [^ ungriddedPoint]. ^ griddingContext gridPoint:

Re: [Pharo-dev] SqueakSource3 with new server name

https://pharo.fogbugz.com/f/cases/11023/Backport-2-0-Change-gemstone-reference-to-gemtalksystems Thierry Le 26/06/2013 11:18, Torsten Bergmann a écrit : Dale wrote: "When the servers come back online you should start using the new domain names: ss3.gemstone.com -> ss3.gemtalksystems

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

Maybe this would be a good time to jettison cruft i.e. don't implement > things until someone requests them ;) > Some important ones are still missing. I'd add them and then see which of the remaining ones we need

Re: [Pharo-dev] [update 2.0] #20608

On Wed, Jun 26, 2013 at 8:53 AM, Martin Dias wrote: > yes, I want to use gutenberg, but still didn't check how follow instructions there https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english#readme -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the abilit

[Pharo-dev] MorphicEvent obsolete code :)

Looks like is not used :) MorphicEvent>>readFrom: aStream "Read a MorphicEvent from the given stream." | typeString | typeString := String streamContents: [:s | | c | [(c := aStream next) isLetter] whileTrue: [s nextPut: c]]. typeString = 'mous

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

On 26 Jun 2013, at 09:08, kilon wrote: > There must be enough people around that are not companies > and still willing to contribute financially to pharo , afterall who says > "no" to more money , right ? :D That is what the Pharo Association is for: http://association.pharo.org Sven

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

by the way , in case anyone wonders, I know that it did not remove the full library because it asked me to remove 10 mbs while when it installed it asked me to add 200+ MBs , quite a difference ;) -- View this message in context: http://forum.world.st/Pharo-dev-Pharo-does-not-work-on-ubuntu-13

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

Oh ok. I'm out of ideas now, apart from removing them one by one :P Thierry Le 26/06/2013 09:58, kilon a écrit : yes Thierry I have already done that I just forgot to add it here. Any other suggestions ? -- View this message in context: http://forum.world.st/Pharo-dev-Pharo-does-not-work-on

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

yes Thierry I have already done that I just forgot to add it here. Any other suggestions ? -- View this message in context: http://forum.world.st/Pharo-dev-Pharo-does-not-work-on-ubuntu-13-04-tp4695056p4695205.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

You probably need to do a : sudo apt-get autoremove after that, so that you get rid of all the dependencies of ia32-libs that you haven't installed yourself. Thierry Le 26/06/2013 09:35, kilon a écrit : I try to unistall the libraries with sudo apt-get remove --purge ia32-libs But unista

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

первоначальную задачу сдали (подписали) копия у Марины получили относительно нее запросы на изменения - выделение из АРМа фаршесоставителя АРМ-а для мешалки - разработка АРМа для составителя специй на основании спланированных замесов (заявки подписаны) -Original Message- From: Pharo-de

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

I try to unistall the libraries with sudo apt-get remove --purge ia32-libs But unistall only a single library and of course I cannot reproduce the error cause pharo continues to function properly. I am by no mean an Ubuntu expert but I have seen this another time, trying to remove a library this

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

On Jun 26, 2013, at 9:09 AM, kilon wrote: > Sure Damien I will try to unistall the libraries and try again and report the > error. > > Stephan why the website does not have a donate button ? because there is none. Because there only will be one if someone adds one. It is on the TODO, but th

Re: [Pharo-dev] Pharo does not work on ubuntu 13.04

Sure Damien I will try to unistall the libraries and try again and report the error. Stephan why the website does not have a donate button ? Or you could even try kickstarter. I am not claiming I know how these things work but maybe its worth a try. There must be enough people around that are not