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

Re: [Pharo-dev] Should Job use SystemAnnouncer?

by Camillo Bruni

I think this is a good idea, you can see that there is already an #announcer inst var that currently is unused. I think the original idea behind using the system announcer was to make other tools possible that will interact with the progress. Though nobody did it so far ;) => if it is a performance penalty remove it! Plus if there is a private announcer for each job the only announcement that really needs to go public is JobStart, from then on potential 3rd party tools can register to the internal announcer. On 2013-09-01, at 20:43, Stephan Eggermont <stephan(a)stack.nl> wrote: > While profiling some progressbar code, I noticed Job uses > the SystemAnnouncer. It seems odd that an Announcer used > for noticing code changes is reused for something unrelated > to code changes. Could we have a separate announcer for this? > > > Stephan >

Sept. 1, 2013

Should Job use SystemAnnouncer?

by Stephan Eggermont

While profiling some progressbar code, I noticed Job uses the SystemAnnouncer. It seems odd that an Announcer used for noticing code changes is reused for something unrelated to code changes. Could we have a separate announcer for this? Stephan

Sept. 1, 2013

Re: [Pharo-dev] DSM in Roassal

by Alexandre Bergel

Hi Volkert, Yes, we started an effort on that. Consider: | view builder | view := ROView new. builder := RODependencyMatrixBuilder new. builder model: (Array with: true with: false). builder dependencyBoolean: #xor:. builder gapSize: 0. builder on: view. view open Another example: | view builder objects | objects := ROShape withAllSubclasses. view := ROView new. view @ RODraggable. builder := RODependencyMatrixBuilder new. builder model: objects. " builder noVerticalShape." builder dependency: #superclass. builder gapSize: 0. builder on: view. view open If you are working on something similar, it would be great to join forces... how to load Juraj's code: Gofer new smalltalkhubUser: 'JurajKubelka' project: 'RoassalProposals'; package: 'RoassalGraphBuilders'; load. (Smalltalk globals at: #RODependencyMatrixBuilderTest) browse. Look at the ROMatrixExample class Will you be at ESUG? Cheers, Alexandre On Sep 1, 2013, at 11:43 AM, Volkert Barr <volkert(a)nivoba.de> wrote: > Dear all, > > i am using Roassal for visualizing applications dependencies and metrics of applications / applications clusters > on enterprise architecture level. I would now do some experiments with DSM and found an older mailing list post that DSM > support in Roassal is currently in development. That is cool :-) > > How can i tests this feature? It is not part of the latest Roassal (dev) version. Please help ... :-) > > BW, > Volkert > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 1, 2013

DSM in Roassal

by Volkert Barr

Dear all, i am using Roassal for visualizing applications dependencies and metrics of applications / applications clusters on enterprise architecture level. I would now do some experiments with DSM and found an older mailing list post that DSM support in Roassal is currently in development. That is cool :-) How can i tests this feature? It is not part of the latest Roassal (dev) version. Please help ... :-) BW, Volkert

Sept. 1, 2013

Re: [Pharo-dev] "self foo: (var := â¦)" vs "var := â¦. self foo: var"

by Alexandre Bergel

Ok, thanks! Alexandre On Sep 1, 2013, at 10:01 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > this is a VM problem, > > Use the latest (unstable) vm from here: http://files.pharo.org/vm/pharo/ > Esteban updated the VM > > > > On 2013-09-01, at 15:02, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> Hi! >> >> I am facing a strange situation: >> >> The following expression raises an error: >> -=-=-=-=-=-=-=-=-= >> rawView add: (helpLabel := (ROElement on: 'Click here!') + ROLabel). >> -=-=-=-=-=-=-=-=-= >> >> Apparently, what is sent as argument to #add: is an integer. >> >> I have to update my code with : >> -=-=-=-=-=-=-=-=-= >> (helpLabel := (ROElement on: 'Click here!') + ROLabel). >> rawView add: helpLabel. >> -=-=-=-=-=-=-=-=-= >> >> To not have an error. >> >> This is really strange! By the way, this looks like the issue with Metacello? >> >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 1, 2013

Re: [Pharo-dev] "self foo: (var := â¦)" vs "var := â¦. self foo: var"

by Camillo Bruni

this is a VM problem, Use the latest (unstable) vm from here: http://files.pharo.org/vm/pharo/ Esteban updated the VM On 2013-09-01, at 15:02, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > I am facing a strange situation: > > The following expression raises an error: > -=-=-=-=-=-=-=-=-= > rawView add: (helpLabel := (ROElement on: 'Click here!') + ROLabel). > -=-=-=-=-=-=-=-=-= > > Apparently, what is sent as argument to #add: is an integer. > > I have to update my code with : > -=-=-=-=-=-=-=-=-= > (helpLabel := (ROElement on: 'Click here!') + ROLabel). > rawView add: helpLabel. > -=-=-=-=-=-=-=-=-= > > To not have an error. > > This is really strange! By the way, this looks like the issue with Metacello? > > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Sept. 1, 2013

"self foo: (var := â¦)" vs "var := â¦. self foo: var"

by Alexandre Bergel

Hi! I am facing a strange situation: The following expression raises an error: -=-=-=-=-=-=-=-=-= rawView add: (helpLabel := (ROElement on: 'Click here!') + ROLabel). -=-=-=-=-=-=-=-=-= Apparently, what is sent as argument to #add: is an integer. I have to update my code with : -=-=-=-=-=-=-=-=-= (helpLabel := (ROElement on: 'Click here!') + ROLabel). rawView add: helpLabel. -=-=-=-=-=-=-=-=-= To not have an error. This is really strange! By the way, this looks like the issue with Metacello? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 1, 2013

TalkFFI versions 1.3 and 1.4

by Guillermo Polito

Hi Ciprian, In the last weeks we were playing a bit with TalkFFI for dbxtalk. After a while we got a working version but we found some stuff we'd like to fix. In version 1.3 CLExternalLibraryWrapper class>>uniqueInstance is wrongly defined. This is already fixed in talkffi 1.4. However, version 1.4 includes some other changes that make the VM just crash, :). What do you think about making a 1.3.1 version with the minor fix for the unique instance so we can move on without overrides? Of course I'm happy to provide the code (given the credentials to commit :)). TIA, Guille

Sept. 1, 2013

Re: [Pharo-dev] No more dirty packages in Pharo

by StÃ©phane Ducasse

excellent! On Sep 1, 2013, at 9:41 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Ok, great. I loaded ConfigurationOfMagritte3 #development, and Grease loaded clean. Thank you! > > The only remaining problem was asMorph in Magritte-Morph, but I fixed it now, so Magritte loads clean in Pharo 2.0. > > Cheers, > Doru > > > > On Sun, Sep 1, 2013 at 7:29 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Great. > > What version? > > Doru > > > On Fri, Aug 30, 2013 at 12:59 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Hi, > > I've fixed Magritte and Grease configurations so that loading these projects do not dirty any pharo package anymore. > > Best > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without losing enthusiasm." > Winston Churchill > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Sept. 1, 2013

Re: [Pharo-dev] where is hosted Grease?

by Esteban Lorenzano

On Sep 1, 2013, at 9:11 AM, Johan Brichau <johan(a)inceptive.be> wrote: > > On 31 Aug 2013, at 17:45, Tobias Pape <Das.Linux(a)gmx.de> wrote: > >>> That is like saying everyone have to be in the Seaside team to upload just a fix in Grease? >> >> >> Then make a grease team. >> Grease was invented for Seaside by the seaside team, doesn't >> that make the Seaside team the official maintainer? >> Then yes, everyone who wants his fix in the official Grease >> repo has to be on that team or ask someone there to merge/integrate/upload. > > > Does it really matter if you need to be on the Seaside team for contributing to only a specific sub project? not really. you could be a contributor of a project (not a team), and not part of the team... you could be part of Grease project without having anything to do with the rest of Seaside. > For example, Damien recently contributed fixes to the configurations and therefore I added him to the Seaside team. > > Easy. done. > > Apart from that, it makes sense to move Grease to its own project. > I'm not an author of Grease, but I did the move of Seaside to Smalltalkhub and raised the issue about Grease not having its proper project on the Seaside-dev mailinglist while doing this back in July. > If I remember correctly, there was no opposition to moving it to its separate space if this helped development. The reason it did not happen yet is that I previously thought we needed to merge the two Grease versions from the two Seaside repositories to a single one. But now I realise that we should only move the most recent one (the one from Seaside31). > > ESUG is coming up. If we did not do it by then, talk to us. > > Cheers > Johan

Sept. 1, 2013