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

Damn, the last row of the last plugins fills all the window... -- Pavel 2013/10/4 Pavel Krivanek : > Thanks, this seems to work: > > defaultSpec > > | layout | > layout := SpecLayout composed. > self pluginClasses do: [ :c | > layout add: {#model. #class. #pluginOf:. c. #defaultSpec} ].

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

Thanks, this seems to work: defaultSpec | layout | layout := SpecLayout composed. self pluginClasses do: [ :c | layout add: {#model. #class. #pluginOf:. c. #defaultSpec} ]. ^ layout. plugin code on the instance side looks like this: defaultSpec ^ SpecLayout composed

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

Impressive is the right word, indeed :) Doru On Fri, Oct 4, 2013 at 12:08 PM, Sven Van Caekenberghe wrote: > > On 04 Oct 2013, at 10:53, Marcus Denker wrote: > > > 30446 > > - > > > > 11719 integrate all the changes from the repository of the new debugger > > https://pharo.fogbugz.c

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

Since you are doing some really edge use of Spec, it's not covered by Spec easily. But if on you model you have a method returning your pluginClasses, you could do maybe: | layout | layout := SpecLayout composed. self pluginClasses do: [ :c | layout add: {#model. pluginOf:. c} ] I am

Re: [Pharo-dev] What is WeakActionSequence?

This is a good question I was always wondering. I think it is related to event triggered in DependentFields of Object. It triggers several events. Weak because somehow there are weak event handled without weak references, probably due to the lack of ephemerons. (in some case the activation of the

Re: [Pharo-dev] additional Milestone label for applications

On 2013-10-04, at 19:44, b...@openinworld.com wrote: > Camillo Bruni wrote: >> If you want to track an external project on fogbugz, we should also create a >> proper fogbugz project, so it is clearly separated. > There is a separate Project='Launcher', but I guess its hard to filter out > when

Re: [Pharo-dev] [ann] system attraction view

Hi, On Fri, Oct 4, 2013 at 2:42 PM, Goubier Thierry wrote: > > > Le 04/10/2013 14:14, Tudor Girba a écrit : > >> Hi, >> >> >> On Fri, Oct 4, 2013 at 1:41 PM, Goubier Thierry > > wrote: >> >> Hi Tudor, >> >> I found your visualisation very interesting, and

Re: [Pharo-dev] What is WeakActionSequence?

On 04 Oct 2013, at 19:27, Camillo Bruni wrote: > What is that class? No comments, two single methods on Object that refer to > it? If you remove it, the world as we know it will end ! Seriously, I've seen this before, I also asked the same question, but no one seems to know. Sven

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

This was the original code for the spec that embeds plugins. As you can see, it had to use ugly addMorph:. I do not think that I need to do something special. Has the current Spec a better way how to do that? defaultSpec | spec | spec := OrderedCollection with: #ContainerModel. spec a

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

In other words... I have a model that has some plugins. I need to generate a spec that embeds specs generated for each plugin. Models for this embedded specs must be the plugins, not the original model. -- Pavel 2013/10/4 Pavel Krivanek : > well, and the version with "SpecLayout composed" when I

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

well, and the version with "SpecLayout composed" when I do not need direct fractions? ^ SpecLayout composed newRow:[: r | r add: #finderButtonModel] height: 25 How to send #finderButtonModel to different object than SpecInterpreter model?

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

^{ #ContainerModel. #vShrinkWrap. #add:. {{self. #finderButtonModel}. #layout:. #(FrameLayout rightFraction: 0.125)}. #add:. {{self. #browserButtonModel}. #layout:. #(FrameLayout leftFraction: 0.125 rightFractio

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

Ben, how now should look code like this: defaultSpec ^{ #ComposableSpec. #vResizing:. #shrinkWrap. #add:. {{self. #finderButtonModel}. #layout:. #(FrameLayout rightFraction: 0.125)}. #add:. {{self. #browserButtonModel}. #layout:

Re: [Pharo-dev] additional Milestone label for applications

Camillo Bruni wrote: If you want to track an external project on fogbugz, we should also create a proper fogbugz project, so it is clearly separated. There is a separate Project='Launcher', but I guess its hard to filter out when many Projects are subparts of the main image. On a projec

Re: [Pharo-dev] additional Milestone label for applications

b...@openinworld.com wrote: I've been advised that for application related issues tracked on Fogbugz (e.g. for PharoLauncher) to avoid tagging the Milestone as 'Pharo3.0' - which is reserved for image related issues. Fair enough, but the only available alternative 'Later' just doesn't seem a g

[Pharo-dev] What is WeakActionSequence?

What is that class? No comments, two single methods on Object that refer to it? signature.asc Description: Message signed with OpenPGP using GPGMail

Re: [Pharo-dev] additional Milestone label for applications

If you want to track an external project on fogbugz, we should also create a proper fogbugz project, so it is clearly separated. On a project-basis you can define custom milestones. So in that sense, milestones do not serve for distinguishing external projects. Additionally you can define a simp

[Pharo-dev] additional Milestone label for applications

I've been advised that for application related issues tracked on Fogbugz (e.g. for PharoLauncher) to avoid tagging the Milestone as 'Pharo3.0' - which is reserved for image related issues.  Fair enough, but the only available alternative 'Later' just doesn't seem a good fit.  Can adding anothe

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

Hi Ben, I already had a workaround to subscribe to a morph's event: treeModel announcer on: WidgetBuilt do: [ :builtAnnouncement | builtAnnouncement widget when: #aboutToToggleExpandedState send: #aboutToToggleExpandedState: to: self ] So I migrated it to: treeModel whenBuiltDo: [ :builtAnno

[Pharo-dev] [update 3.0] #30452

30452 - 11707 Tree Inspector: code pane needs to bind self https://pharo.fogbugz.com/f/cases/11707 11778 Can not <- or -> in TextModel https://pharo.fogbugz.com/f/cases/11778 11780 clean up unused FilePath and #asSqueakPathName https://pharo.fogbugz.co

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

Excellent!! On Fri, Oct 4, 2013 at 3:21 PM, Andrei Chis wrote: > Now it would be nice to see what other actions do we need in the debugger > for creating methods > https://pharo.fogbugz.com/f/cases/5338/Create-button-in-debugger-for-subclassResponsibility-shouldBeImplement

[Pharo-dev] [update 3.0] #30451

30451 - 11457 #asSqueakPathName is a bad name https://pharo.fogbugz.com/f/cases/11457 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.928.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Settings-Polymorph-MarcusDenker.57.diff http://small

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

Now it would be nice to see what other actions do we need in the debugger for creating methods https://pharo.fogbugz.com/f/cases/5338/Create-button-in-debugger-for-subclassResponsibility-shouldBeImplemented-etc On Fri, Oct 4, 2013 at 2:57 PM, Marcus Denker wrote: > 30449 > - > > 11777 Fix Sp

[Pharo-dev] [update 3.0] #30450

30450 - 11759 Protocol names should be Symbols https://pharo.fogbugz.com/f/cases/11759 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/ClassOrganizer-Core-MarcusDenker.10.diff signature.asc Description: Message signed with OpenPGP using GPGMail

[Pharo-dev] [regression reporter]regression occurred

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=win/570/ 1 regressions found. Zinc.Tests.ZnServerTests.testEntityTooLarge

Re: [Pharo-dev] PharoCommandLineHandler

On 2013-10-04, at 14:54, Pavel Krivanek wrote: > It is not in the separate (or other) package so it still makes > problems for Kernel jobs (I have to remove this class before > shrinking). > This information from the documentation does not seem to be valid: > "It first checks if another handler

[Pharo-dev] [update 3.0] #30449

30449 - 11777 Fix SpecTests https://pharo.fogbugz.com/f/cases/11777 11776 Fix Create action on #subclassResponsibility https://pharo.fogbugz.com/f/cases/11776 The debugger now displays the create button when an exception of type #subclassResponsibility is shown. How

Re: [Pharo-dev] PharoCommandLineHandler

It is not in the separate (or other) package so it still makes problems for Kernel jobs (I have to remove this class before shrinking). This information from the documentation does not seem to be valid: "It first checks if another handler is available. If so it will activate the found handler." --

Re: [Pharo-dev] PharoCommandLineHandler

We introduced this class because of the Kernel jobs (see the class comment). So yes, it is essential for the Pharo Image, not for the Kernel (as you can see by its superclass). On 2013-10-04, at 14:46, Camillo Bruni wrote: > which pharo version? > > On 2013-10-04, at 14:42, Pavel Krivanek wr

Re: [Pharo-dev] PharoCommandLineHandler

which pharo version? On 2013-10-04, at 14:42, Pavel Krivanek wrote: > PharoCommandLineHandler is strange. What is real purpose of this > class? Do we need it? It adds UsersManager dependency but I do not > think that it really stops the processing of arguments. > > -- Pavel > signature.asc

Re: [Pharo-dev] RPackage-SystemIntegration problem

It helped, thanks. -- Pavel 2013/10/4 Marcus Denker : > > On Oct 4, 2013, at 11:46 AM, Pavel Krivanek wrote: > >> Hi, >> >> When I look at the package RPackage-SystemIntegration (v. 173) and I >> do browse it in Monticello GUI, it doesn't contain the extension of >> the removed class ClassOrgani

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

Thank you all! :D On 4 October 2013 09:37, Andrei Chis wrote: > Thanks for integrating it :) > > > On Fri, Oct 4, 2013 at 10:53 AM, Marcus Denker wrote: > >> 30446 >> - >> >> 11719 integrate all the changes from the repository of the new debugger >> https://pharo.fogbugz.com/f/cases

[Pharo-dev] PharoCommandLineHandler

PharoCommandLineHandler is strange. What is real purpose of this class? Do we need it? It adds UsersManager dependency but I do not think that it really stops the processing of arguments. -- Pavel

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

For Spec users: The change is mostly backward compatible :) 2 things really changed: - direct access to a model's widget is not returning what it used to return. This is done on purpose since it's very often a bad idea to directly access the widget. - some behaviour on tr

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

Thanks for integrating it :) On Fri, Oct 4, 2013 at 10:53 AM, Marcus Denker wrote: > 30446 > - > > 11719 integrate all the changes from the repository of the new debugger > https://pharo.fogbugz.com/f/cases/11719 > > This commit contains the following main changes: > - debugging acti

Re: [Pharo-dev] [ann] system attraction view

Le 04/10/2013 14:14, Tudor Girba a écrit : Hi, On Fri, Oct 4, 2013 at 1:41 PM, Goubier Thierry mailto:thierry.goub...@cea.fr>> wrote: Hi Tudor, I found your visualisation very interesting, and wondered about one thing linked to your blog post and if I got it right. The visu

[Pharo-dev] [update 3.0] #30448

30448 - 11740 Remove Morphic dependency from Spec https://pharo.fogbugz.com/f/cases/11740 A Huge change from Ben... Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1292.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tabs-MarcusDenker.33.

[Pharo-dev] [regression reporter]regression occurred

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=mac/569/ 3 regressions found. KernelTests.Classes.ClassHierarchyTest.testSubclasses Spec.Tests.SpecInterpreterTest.testBuildWidgetForWithSpec Spec.Tests.SpecInterpreterTest.testInterpretASpecModelMorphAssociation

[Pharo-dev] [regression reporter]regression occurred

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=win/569/ 3 regressions found. KernelTests.Classes.ClassHierarchyTest.testSubclasses Spec.Tests.SpecInterpreterTest.testBuildWidgetForWithSpec Spec.Tests.SpecInterpreterTest.testInterpretASpecModelMorphAssociation

[Pharo-dev] [regression reporter]regression occurred

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=linux-stable-worker/569/ 3 regressions found. KernelTests.Classes.ClassHierarchyTest.testSubclasses Spec.Tests.SpecInterpreterTest.testBuildWidgetForWithSpec Spec.Tests.SpecInterpreterTest.testInterpretASpecModelMorphAs

Re: [Pharo-dev] [ANN] Mustache templates

Very nice! Doru On Fri, Oct 4, 2013 at 1:47 PM, Sven Van Caekenberghe wrote: > > On 04 Oct 2013, at 12:58, Norbert Hartl wrote: > > > > > Am 04.10.2013 um 12:32 schrieb Alexandre Bergel >: > > > >> What is a mustache template? > >> > > > http://norbert.hartl.name/blog/2013/10/03/mustache-tem

Re: [Pharo-dev] [ann] system attraction view

Hi, On Fri, Oct 4, 2013 at 1:41 PM, Goubier Thierry wrote: > Hi Tudor, > > I found your visualisation very interesting, and wondered about one thing > linked to your blog post and if I got it right. > > The visualisation you're showing is able to show, at the single class > level, if a class is

Re: [Pharo-dev] References to Obsolete classes

I agree, If you want to reference an obsolete class after removing the class A, then the source code of the method should also change, and say "AnObsoleteA" instead of "A" if the source code says "A" then i do not like to have a reference to "AnObsoleteA" 2013/10/4 Sabine Knöfel > Hi, > > I

Re: [Pharo-dev] [ANN] Mustache templates

On 04 Oct 2013, at 12:58, Norbert Hartl wrote: > > Am 04.10.2013 um 12:32 schrieb Alexandre Bergel : > >> What is a mustache template? >> > http://norbert.hartl.name/blog/2013/10/03/mustache-templates-for-smalltalk/ Nice! > Norbert > >> On 4 Oct 2013, at 03:56, Torsten Bergmann wrote: >>

Re: [Pharo-dev] [ann] system attraction view

Hi Tudor, I found your visualisation very interesting, and wondered about one thing linked to your blog post and if I got it right. The visualisation you're showing is able to show, at the single class level, if a class is more or less regular (i.e. tidy == well designed?) but you show that

Re: [Pharo-dev] Link to books on website

On Oct 4, 2013, at 9:25 AM, Torsten Bergmann wrote: > Looks like our homepage has a link to Pharo by example, but not to > the new Deep into Pharo book or the other free ST book collection from Stef > > http://www.pharo-project.org/home this is all linked here: http://www.pharo-proj

[Pharo-dev] [update 3.0] #30447

30447 - 11773 SpecDebugger(Object)>>doesNotUnderstand: #expandStack https://pharo.fogbugz.com/f/cases/11773 11774 sync RPackage-SystemIntegration https://pharo.fogbugz.com/f/cases/11774 11775 trivial clean PolyMorph https://pharo.fogbugz.com/f/cases/11

Re: [Pharo-dev] [ANN] Mustache templates

Am 04.10.2013 um 12:32 schrieb Alexandre Bergel : > What is a mustache template? > http://norbert.hartl.name/blog/2013/10/03/mustache-templates-for-smalltalk/ Norbert > On 4 Oct 2013, at 03:56, Torsten Bergmann wrote: > >>> I like to announce my smalltalk port of mustache templates. >> >> C

Re: [Pharo-dev] Pharo (cog) Vm on Windows with 2GB virtual mem

thats great indeed. I would be interested to hear your experience with it when you start processing that data , maybe hint* *hint* a blog post ? :D It benefits pharo in general to have practical examples that show that pharo can be a very efficient environment and language. oscar wrote > Than

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

On Oct 4, 2013, at 12:35 PM, Pavel Krivanek wrote: > One new package DebuggerActions, right? And DebuggerFilters Marcus signature.asc Description: Message signed with OpenPGP using GPGMail

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

One new package DebuggerActions, right? -- Pavel 2013/10/4 Marcus Denker : > 30446 > - > > 11719 integrate all the changes from the repository of the new debugger > https://pharo.fogbugz.com/f/cases/11719 > > This commit contains the following main changes: > - debugging actions are f

Re: [Pharo-dev] RPackage-SystemIntegration problem

On Oct 4, 2013, at 11:46 AM, Pavel Krivanek wrote: > Hi, > > When I look at the package RPackage-SystemIntegration (v. 173) and I > do browse it in Monticello GUI, it doesn't contain the extension of > the removed class ClassOrganizer. But when I do the same and I browse > the this package in t

Re: [Pharo-dev] [ANN] Mustache templates

What is a mustache template? Cheers, Alexandre On 4 Oct 2013, at 03:56, Torsten Bergmann wrote: >> I like to announce my smalltalk port of mustache templates. > > Cool! > >> To load it do > > Consider making a copy into MetaRepoForPharo20 or MetaReporForPharo30 > if it is working in these

Re: [Pharo-dev] References to Obsolete classes

Hi, I run into the same problem last week and endend up in reloading my code in a new image. I prefer your suggestion. Sabine Von meinem iPad gesendet Am 04.10.2013 um 12:04 schrieb Noury Bouraqadi : > Hi, > > Consider the following scenario: > 1- create class A > 2- create class B with a m

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

On 04 Oct 2013, at 10:53, Marcus Denker wrote: > 30446 > - > > 11719 integrate all the changes from the repository of the new debugger > https://pharo.fogbugz.com/f/cases/11719 > > This commit contains the following main changes: > - debugging actions are first class entities; they a

[Pharo-dev] References to Obsolete classes

Hi, Consider the following scenario: 1- create class A 2- create class B with a method m that references class A 3- delete class A . As a result B>>#m holds a reference to ObsoleteA 4- create a new class A. B>>#m continues to hold a reference to ObsoleteA. This is even more disturbing, since th

[Pharo-dev] RPackage-SystemIntegration problem

Hi, When I look at the package RPackage-SystemIntegration (v. 173) and I do browse it in Monticello GUI, it doesn't contain the extension of the removed class ClassOrganizer. But when I do the same and I browse the this package in the same version from the Pharo repository, it does contain extensi

Re: [Pharo-dev] Pharo (cog) Vm on Windows with 2GB virtual mem

Hi, As far as I can tell, you should set the limit in MBytes. So, for 2G, you should have: AddressSpaceLimit=2048 I am using 1GB for some Moose analyses. I benchmarked and got no sign of slowdown. Cheers, Doru On Fri, Oct 4, 2013 at 6:10 AM, Oscar EA Callaú wrote: > Thanks a lot, I added

[Pharo-dev] [regression reporter]regression occurred

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=win/567/ 2 regressions found. ToolsTest.Debugger.DebuggerTest.testBasic Zinc.Tests.ZnServerTests.testEntityTooLarge

[Pharo-dev] [regression reporter]regression occurred

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=mac/567/ 1 regressions found. ToolsTest.Debugger.DebuggerTest.testBasic

[Pharo-dev] [regression reporter]regression occurred

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=linux-stable-worker/567/ 1 regressions found. ToolsTest.Debugger.DebuggerTest.testBasic

[Pharo-dev] [update 3.0] #30446

30446 - 11719 integrate all the changes from the repository of the new debugger https://pharo.fogbugz.com/f/cases/11719 This commit contains the following main changes: - debugging actions are first class entities; they are defined in separate classes. All actions from the toolbar ar

Re: [Pharo-dev] Pharo (cog) Vm on Windows with 2GB virtual mem

That's a great quote for marketing Pharo. Thanks Oscar. Oscar EA Callaú wrote: FYI, I don’t have speed problems with such memory. Of course, If I’ll process some big data, I’ll wait a while to get the answer, but the same happens in any other lang/platt. Certainty, I can do fast experiments in

Re: [Pharo-dev] [ANN] Mustache templates

Am 04.10.2013 um 08:56 schrieb Torsten Bergmann : >> I like to announce my smalltalk port of mustache templates. > > Cool! > >> To load it do > > Consider making a copy into MetaRepoForPharo20 or MetaReporForPharo30 > if it is working in these versions. > > That way it is easily accessible vi

Re: [Pharo-dev] "as yet unclassified" protocol remains when empty

Thanks Thierry. Searching didn't turn up anything, so I logged it https://pharo.fogbugz.com/f/cases/11772/as-yet-unclassified-protocol-remains-when-empty Goubier Thierry wrote: Hi Ben, I think it has already been noticed as a bug, so it will be corrected. Not sure there is already an issue a

[Pharo-dev] Link to books on website

Looks like our homepage has a link to Pharo by example, but not to the new Deep into Pharo book or the other free ST book collection from Stef http://www.pharo-project.org/home Looks like the Collaborative book moved to Gemtalksystem: http://pharo.gemtalksystems.com/ Is it still maintained/