30445
-
11767 Fix codeCriticeBrowser and some critic driven cleanups for code critics
https://pharo.fogbugz.com/f/cases/11767
11769 Some random refactorings
https://pharo.fogbugz.com/f/cases/11769
11768 Small Code Critic cleanup of UpdateStreamer
On Oct 4, 2013, at 8:04 AM, Marcus Denker marcus.den...@inria.fr wrote:
30445
-
11767 Fix codeCriticeBrowser and some critic driven cleanups for code critics
https://pharo.fogbugz.com/f/cases/11767
11769 Some random refactorings
30445
-
11767 Fix codeCriticeBrowser and some critic driven cleanups for code critics
https://pharo.fogbugz.com/f/cases/11767
11769 Some random refactorings
https://pharo.fogbugz.com/f/cases/11769
Diff information:
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 via Config browser.
Thx
T.
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
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
Am 04.10.2013 um 08:56 schrieb Torsten Bergmann asta...@gmx.de:
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
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
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
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
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=mac/567/
1 regressions found.
ToolsTest.Debugger.DebuggerTest.testBasic
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ú oalva...@dcc.uchile.clwrote:
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
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 the
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 bouraq...@gmail.com:
Hi,
Consider the following scenario:
1- create class A
2- create
On Oct 4, 2013, at 11:46 AM, Pavel Krivanek pavel.kriva...@gmail.com 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
One new package DebuggerActions, right?
-- Pavel
2013/10/4 Marcus Denker marcus.den...@inria.fr:
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:
-
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
On Oct 4, 2013, at 9:25 AM, Torsten Bergmann asta...@gmx.de 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:
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
Hi,
On Fri, Oct 4, 2013 at 1:41 PM, Goubier Thierry thierry.goub...@cea.frwrote:
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
Very nice!
Doru
On Fri, Oct 4, 2013 at 1:47 PM, Sven Van Caekenberghe s...@stfx.eu wrote:
On 04 Oct 2013, at 12:58, Norbert Hartl norb...@hartl.name wrote:
Am 04.10.2013 um 12:32 schrieb Alexandre Bergel alexandre.ber...@me.com
:
What is a mustache template?
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
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
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
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
Le 04/10/2013 14:14, Tudor Girba a écrit :
Hi,
On Fri, Oct 4, 2013 at 1:41 PM, Goubier Thierry thierry.goub...@cea.fr
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
Thanks for integrating it :)
On Fri, Oct 4, 2013 at 10:53 AM, Marcus Denker marcus.den...@inria.frwrote:
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:
-
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
which pharo version?
On 2013-10-04, at 14:42, Pavel Krivanek pavel.kriva...@gmail.com 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
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 camillobr...@gmail.com wrote:
which pharo version?
On 2013-10-04, at
On 2013-10-04, at 14:54, Pavel Krivanek pavel.kriva...@gmail.com 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
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=win/570/
1 regressions found.
Zinc.Tests.ZnServerTests.testEntityTooLarge
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 marcus.den...@inria.frwrote:
30449
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
Excellent!!
On Fri, Oct 4, 2013 at 3:21 PM, Andrei Chis chisvasileand...@gmail.com wrote:
Now it would be nice to see what other actions do we need in the debugger
for creating methods
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
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
another
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
What is that class? No comments, two single methods on Object that refer to it?
signature.asc
Description: Message signed with OpenPGP using GPGMail
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
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
Ben,
how now should look code like this:
defaultSpec
^{ #ComposableSpec.
#vResizing:. #shrinkWrap.
#add:. {{self. #finderButtonModel}.
#layout:. #(FrameLayout
rightFraction: 0.125)}.
#add:. {{self. #browserButtonModel}.
^{ #ContainerModel.
#vShrinkWrap.
#add:. {{self. #finderButtonModel}.
#layout:. #(FrameLayout
rightFraction: 0.125)}.
#add:. {{self. #browserButtonModel}.
#layout:. #(FrameLayout
leftFraction: 0.125
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?
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 pavel.kriva...@gmail.com:
well, and the version with
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
On 04 Oct 2013, at 19:27, Camillo Bruni camillobr...@gmail.com 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
Hi,
On Fri, Oct 4, 2013 at 2:42 PM, Goubier Thierry thierry.goub...@cea.frwrote:
Le 04/10/2013 14:14, Tudor Girba a écrit :
Hi,
On Fri, Oct 4, 2013 at 1:41 PM, Goubier Thierry thierry.goub...@cea.fr
mailto:thierry.goub...@cea.fr** wrote:
Hi Tudor,
I found your visualisation
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 many
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
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
Impressive is the right word, indeed :)
Doru
On Fri, Oct 4, 2013 at 12:08 PM, Sven Van Caekenberghe s...@stfx.eu wrote:
On 04 Oct 2013, at 10:53, Marcus Denker marcus.den...@inria.fr wrote:
30446
-
11719 integrate all the changes from the repository of the new debugger
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
Damn, the last row of the last plugins fills all the window...
-- Pavel
2013/10/4 Pavel Krivanek pavel.kriva...@gmail.com:
Thanks, this seems to work:
defaultSpec
| layout |
layout := SpecLayout composed.
self pluginClasses do: [ :c |
layout add: {#model. #class. #pluginOf:. c.
55 matches
Mail list logo
