Re: [Pharo-users] ShouldNotImplement: #add: should not have been implemented in Array

[Offray Vladimir Luna Cárdenas]

Somehow it solved itself automagically. :-)

Cheers,

Offray

On 15/09/15 08:39, Offray Vladimir Luna Cárdenas wrote:

Hi,

I was coding today and after creating a method with only the name and 
a comment and trying to save it I started to get this message: 
"ShouldNotImplement: #add: should not have been implemented in Array". 
I don't see anything related to my code that can be generating this. 
The environment is still working, but the message is annoying. Any 
pointers on how to solve it?


Cheers,

Offray

Re: [Pharo-users] load directive

[Dale Henrichs]

On 9/15/15 12:32 AM, Usman Bhatti wrote:
On Fri, Sep 11, 2015 at 11:06 PM, Dale Henrichs 
> wrote:


Usman,

Off topic --- I don't read all of the pharo posts on both pharo
lists, but if you put Metacello in the subject, I have an email
filter that alerts me and I read those (more often:) ...


Ok :)


What you are getting with record is what would be loaded in the
image, so my guess is that in Pharo4.0 there are equivalent or
later versions of all the packages that would be loaded ...


In the versions prior to Pharo4, the directive showed me all the 
packages regardless.
I would guess that happened because the packages weren't already loaded 
in the image prior to Pharo4.0 ...


During a Metacello load there are two passes made a `fetch` and `load` 
pass ... the `fetch` pass produces a loadDirective and the `load` pass 
executes the loadDirective ... the `record` command (without 
`ignoreImage: true`) simply runs the `fetch` pass and returns the 
loadDirective (it also doesn't bother fetching the packages) I do it 
this way so that the same code is used whether you are doing a `fetch` 
or a `record` and reduces the changes for you to get different results 
from both commands ...


Dale

Re: [Pharo-users] Ecstatic ETSite>>generateHtml file copy philosphy

[Damien Cassou]

Ben Coman  writes:

> It would be nice if Pillar was more flexible in this regard. For
> background, I am looking into Ecstatic to generate a static web site
> from Pillar files hosted on GitHub Pages.  This is constrained to
> serve html files out of the base directory of the branch tagged
> "gh-pages".  So I want to generate html files into the root folder,
> from pillar files in a subdirectory "_sitesrc".
>
> I have got as far as getting interested in this line...
> PrExportPhase>>writeAll:using:
> ... outputFile := (file relativeTo: self configuration
> baseDirectory) withExtension: aWriter fileExtension.
>
> [1] https://help.github.com/articles/user-organization-and-project-pages/

you might want to look at this:

https://github.com/cdlm/pharo-katas/

and

http://people.untyped.org/pharo-katas/

which is generated from Pillar. This is the work of Damien Pollet, in
CC.


-- 
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

Re: [Pharo-users] Long text entry field

[Stephan Eggermont]

Hi Offray,

On 15-09-15 16:08, Offray Vladimir Luna Cárdenas wrote:

I will publish my variation of your work. Is pretty specific for the
needs of our local hackerspace, but will be really nice to share code.


Good. It is very helpful to have lots of examples of how to do things 
with Morphic (and then how to do them with Bloc)


Stephan

Re: [Pharo-users] Ecstatic ETSite>>generateHtml file copy philosphy

[Damien Cassou]

Ben Coman  writes:

> * Generating part of the document with a Smalltalk script. Wow! Bingo!
> Just what I've been dreaming of.   Now do you think maybe this might
> be used to open a UI Tool (e.g. SystemBrowser) and generate a screen
> snapshot to png file on disk, that can be included as a Figure ???
> Perhaps even able to process tapes from EventRecorder?
> http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2015-January/104701.html


open a new thread about that. I heard some users might have done
something similar already.


> * In "5.2. Configuration parameters" I see
> support - I am a collection of support files [...] will get
>copied inside the outputDirectory folder.
> Does this support copying a whole folder to be a folder in
> outputDirectory.  For example the "theme" folder in Ecstatic ?


should work straightforwardly if the "support" variable includes "theme/*"

> Some minor feedback on PillarChap doc...


please submit pull requests on
https://github.com/SquareBracketAssociates/EnterprisePharo/


> Now I'm a bit late to the party following 1.0.0 release,


ok, so I won't tell you about Pillar 2 :-)
(https://www.mail-archive.com/pharo-users@lists.pharo.org/msg14415.html)



> but I have one criticism and one enhancement suggestion...
>
> * The syntax @@subscript@@ is very close to @@annotation.  I wonder if
> something like ,,subscript,, might have been a better choice. I don't
> see many double commas anywhere (except data), and if some text needs
> to display such data, requiring a space between commas is probably not
> too onerous.


agree. Please open an issue on https://github.com/pillar-markup/pillar



> * In "3.9.1. Script with a label or caption", since the link syntax is
> used, possibly using the anchor syntax would feel more consistent.
> That is...
> [[[@script1|caption=...
> rather than...
> [[[label=script1|caption=...
>

not sure about that. We need to make the syntax a bit uniform but I
don't see that much improvement here.


> Great work with Pillar guys.


you can thank Cyril who did 99% of it.

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

Re: [Pharo-users] Ecstatic ETSite>>generateHtml file copy philosphy

[Ferlicot D. Cyril]

Le 15/09/2015 16:22, Ben Coman a écrit :
> 
> Thanks. Thats a good read. Its been a while since I was using Pillar.
> I can't remember exact features then but there seems to have been
> massive progress with lots of new nice features...
> 
> * Sub/super-scripts
> 
> * Unique text alignment per table cell - markdown seems only to align
> whole columns
> 
> * Link syntax for internal, neighbouring-file, external-url seems
> balanced and logical
> 
> * Script line numbers, MmmMmmm
> 
> * Templating
> 
> * Generating part of the document with a Smalltalk script. Wow! Bingo!
> Just what I've been dreaming of.   Now do you think maybe this might
> be used to open a UI Tool (e.g. SystemBrowser) and generate a screen
> snapshot to png file on disk, that can be included as a Figure ???

This is on the todo list of Pillar :)

https://github.com/pillar-markup/pillar/issues/17

But as you can see on the list of issues… There is still a lot of works
to do!

> Perhaps even able to process tapes from EventRecorder?
> http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2015-January/104701.html
> 
> 
> One query...
> 
> * In "5.2. Configuration parameters" I see
> support - I am a collection of support files [...] will get
>copied inside the outputDirectory folder.
> Does this support copying a whole folder to be a folder in
> outputDirectory.  For example the "theme" folder in Ecstatic ?
> 

Yes!
For example a common use for a book can be:

"support" : [ "support", "**/Figures" ]

This will include the folder `support` with the templates, css etc.
For the LaTeX export we create some symlinks to the outputDirectory
named `root`, this allow to use "\include{root/support}{myTeXFile.tex}".

This will also include all the folders named `Figures`.
For example if you have `baseDirectory/chap1/Figures` and
`baseDirectory/Annexes/A/c/Figures` you will get
`outputDirectory/chap1/Figures` and `outputDirectory/Annexes/A/c/Figures`.

You can also use "Chap#/Figures" to take only the Figures folder inside
`Chap1`, `Chap2`, `Chap3`…

> 
> Some minor feedback on PillarChap doc...
> 
> * In part "3.8 Pictures", consider leaving the colon off the end of this 
> line...
>  To include a picture, use the syntax 
> +caption>file://filename|parameters+:
>since it confused me for a moment whether it was part of the syntax.
> 
> * Minor grammatical correction...
>  A slide end at the beginning of an other slide or at the end of
> the document.
>  A slide ends at the beginning of another slide or at the end of
> the document.
> 
> 
> Now I'm a bit late to the party following 1.0.0 release, but I have
> one criticism and one enhancement suggestion...
> 
> * The syntax @@subscript@@ is very close to @@annotation.  I wonder if
> something like ,,subscript,, might have been a better choice. I don't
> see many double commas anywhere (except data), and if some text needs
> to display such data, requiring a space between commas is probably not
> too onerous.
> 
> * In "3.9.1. Script with a label or caption", since the link syntax is
> used, possibly using the anchor syntax would feel more consistent.
> That is...
> [[[@script1|caption=...
> rather than...
> [[[label=script1|caption=...
> 

I will keep that feedback and see what I can do latter :)
Thank you very much! Feedback is awesome!

> 
> Great work with Pillar guys.
> 
> So if I want to add the following to Ecstatic's pillar.conf
> {...
>"baseDirectory" : "_srcsite",
> "outputDirectory" : ".",
> ...} it won't get automatically passed through to Pillar?  I'll need
> to work out how to get them to Pillar myself?
> 

I didn't had the time to take a look at ecstatic but I know a lot of
features as the outputDirectory are hardcoded inside Ecstatic because
it's new in Pillar and we don't have the time to update ecstatic.

> Am I correct to assume Ecstatic is using Pillar 1.0.0? since
> Monticello shows the latest Configuration is loaded in the image.
> 

I don't know if it is exactly the 1.0.0 but if it's not it's a pretty
close version because we fixed the version with Guillermo at the end of
my internship and the 1.0.0 went out in my last day of internship.

> cheers -ben
> 
> 

-- 
Cheers
Cyril



signature.asc
Description: OpenPGP digital signature

Re: [Pharo-users] Ecstatic ETSite>>generateHtml file copy philosphy

[Ben Coman]

On Tue, Sep 15, 2015 at 2:18 AM, Ferlicot D. Cyril
 wrote:
> Le 14/09/2015 19:24, Ben Coman a écrit :
>>
>> Thanks Peter.
>>
>> It would be nice if Pillar was more flexible in this regard. For
> Hi :)
>
> With the version 1.0.0 of Pillar you have the possibility to use
> "outputDirectory" and the "support" parameters.
> The first will will generate the files into a new folder and the second
> will copy a list of files if the outputDirectory ~= baseDirectory.
>
> You can take a look at the documentation of EnterprisePharo (don't
> forget to take the last version for Pillar 1.0.0 or later:
> https://ci.inria.fr/pharo-contribution/view/Books/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html).

Thanks. Thats a good read. Its been a while since I was using Pillar.
I can't remember exact features then but there seems to have been
massive progress with lots of new nice features...

* Sub/super-scripts

* Unique text alignment per table cell - markdown seems only to align
whole columns

* Link syntax for internal, neighbouring-file, external-url seems
balanced and logical

* Script line numbers, MmmMmmm

* Templating

* Generating part of the document with a Smalltalk script. Wow! Bingo!
Just what I've been dreaming of.   Now do you think maybe this might
be used to open a UI Tool (e.g. SystemBrowser) and generate a screen
snapshot to png file on disk, that can be included as a Figure ???
Perhaps even able to process tapes from EventRecorder?
http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2015-January/104701.html


One query...

* In "5.2. Configuration parameters" I see
support - I am a collection of support files [...] will get
   copied inside the outputDirectory folder.
Does this support copying a whole folder to be a folder in
outputDirectory.  For example the "theme" folder in Ecstatic ?


Some minor feedback on PillarChap doc...

* In part "3.8 Pictures", consider leaving the colon off the end of this line...
 To include a picture, use the syntax +caption>file://filename|parameters+:
   since it confused me for a moment whether it was part of the syntax.

* Minor grammatical correction...
 A slide end at the beginning of an other slide or at the end of
the document.
 A slide ends at the beginning of another slide or at the end of
the document.


Now I'm a bit late to the party following 1.0.0 release, but I have
one criticism and one enhancement suggestion...

* The syntax @@subscript@@ is very close to @@annotation.  I wonder if
something like ,,subscript,, might have been a better choice. I don't
see many double commas anywhere (except data), and if some text needs
to display such data, requiring a space between commas is probably not
too onerous.

* In "3.9.1. Script with a label or caption", since the link syntax is
used, possibly using the anchor syntax would feel more consistent.
That is...
[[[@script1|caption=...
rather than...
[[[label=script1|caption=...


Great work with Pillar guys.


>
> You can also check the configuration of Enterprise Pharo or PharoMooc to
> get a concrete example.
> (https://github.com/SquareBracketAssociates/EnterprisePharo/blob/master/pillar.conf
> --
> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/pillar.conf)
>
>
> Ecstatic doesn't use that for now because we don't have the time to
> update it but Pillar can do it.

So if I want to add the following to Ecstatic's pillar.conf
{...
   "baseDirectory" : "_srcsite",
"outputDirectory" : ".",
...} it won't get automatically passed through to Pillar?  I'll need
to work out how to get them to Pillar myself?

Am I correct to assume Ecstatic is using Pillar 1.0.0? since
Monticello shows the latest Configuration is loaded in the image.

cheers -ben

>
>> background, I am looking into Ecstatic to generate a static web site
>> from Pillar files hosted on GitHub Pages.  This is constrained to
>> serve html files out of the base directory of the branch tagged
>> "gh-pages".  So I want to generate html files into the root folder,
>> from pillar files in a subdirectory "_sitesrc".
>>
>> I have got as far as getting interested in this line...
>> PrExportPhase>>writeAll:using:
>> ... outputFile := (file relativeTo: self configuration
>> baseDirectory) withExtension: aWriter fileExtension.
>>
>> [1] https://help.github.com/articles/user-organization-and-project-pages/
>>
>> cheers -ben
>>
>
>
> --
> Cheers
> Cyril
>

Re: [Pharo-users] Long text entry field

[Offray Vladimir Luna Cárdenas]

Thanks Stephan,

I will publish my variation of your work. Is pretty specific for the 
needs of our local hackerspace, but will be really nice to share code.


Cheers,

Offray

On 15/09/15 08:37, Stephan Eggermont wrote:

On 15-09-15 14:55, Offray Vladimir Luna Cárdenas wrote:

Hi all,

Thanks to the Stephan's advices,  I'm making progress in my small
planning application and hopefully today I will have a working
prototype. Now I would like to add some properties to the PlanColumn
class, one of them is a long description of what the day is gonna be
about. I can fill it using TextEntreDialogWindow, as in Stephan's code
but I would like to have a more apt widget for long text. Unfortunately
I can't find it by myself. Any pointers to where is it? How can I create
a widget for a long text entry?


There are several rubric examples that might help you.
Please note that I am making some improvements to the PlanBoard code
that might be useful for your application.

Stephan

Re: [Pharo-users] Long text entry field

[Offray Vladimir Luna Cárdenas]

Thanks Nicolai. This is what I was looking for.

Cheers,

Offray

On 15/09/15 08:52, Nicolai Hess wrote:



2015-09-15 14:55 GMT+02:00 Offray Vladimir Luna Cárdenas 
mailto:off...@riseup.net>>:


Hi all,

Thanks to the Stephan's advices,  I'm making progress in my small
planning application and hopefully today I will have a working
prototype. Now I would like to add some properties to the
PlanColumn class, one of them is a long description of what the
day is gonna be about. I can fill it using TextEntreDialogWindow,
as in Stephan's code but I would like to have a more apt widget
for long text. Unfortunately I can't find it by myself. Any
pointers to where is it? How can I create a widget for a long text
entry?


Just like TextEntryDialogWindow, but use TextEditorDialogWindow, for 
example:


Smalltalk ui theme
textEditorIn: ActiveWorld
text: 'Enter some text'
title: 'Editor'
entryText: String loremIpsum
entryHeight:300



Cheers,

Offray

Re: [Pharo-users] Long text entry field

[Nicolai Hess]

2015-09-15 14:55 GMT+02:00 Offray Vladimir Luna Cárdenas 
:

> Hi all,
>
> Thanks to the Stephan's advices,  I'm making progress in my small planning
> application and hopefully today I will have a working prototype. Now I
> would like to add some properties to the PlanColumn class, one of them is a
> long description of what the day is gonna be about. I can fill it using
> TextEntreDialogWindow, as in Stephan's code but I would like to have a more
> apt widget for long text. Unfortunately I can't find it by myself. Any
> pointers to where is it? How can I create a widget for a long text entry?
>

Just like TextEntryDialogWindow, but use TextEditorDialogWindow, for
example:

Smalltalk ui theme
textEditorIn: ActiveWorld
text: 'Enter some text'
title: 'Editor'
entryText: String loremIpsum
entryHeight:300




>
> Cheers,
>
> Offray
>
>

[Pharo-users] ShouldNotImplement: #add: should not have been implemented in Array

[Offray Vladimir Luna Cárdenas]

Hi,

I was coding today and after creating a method with only the name and a 
comment and trying to save it I started to get this message: 
"ShouldNotImplement: #add: should not have been implemented in Array". I 
don't see anything related to my code that can be generating this. The 
environment is still working, but the message is annoying. Any pointers 
on how to solve it?


Cheers,

Offray

Re: [Pharo-users] Long text entry field

[Stephan Eggermont]

On 15-09-15 14:55, Offray Vladimir Luna Cárdenas wrote:

Hi all,

Thanks to the Stephan's advices,  I'm making progress in my small
planning application and hopefully today I will have a working
prototype. Now I would like to add some properties to the PlanColumn
class, one of them is a long description of what the day is gonna be
about. I can fill it using TextEntreDialogWindow, as in Stephan's code
but I would like to have a more apt widget for long text. Unfortunately
I can't find it by myself. Any pointers to where is it? How can I create
a widget for a long text entry?


There are several rubric examples that might help you.
Please note that I am making some improvements to the PlanBoard code
that might be useful for your application.

Stephan

[Pharo-users] Long text entry field

[Offray Vladimir Luna Cárdenas]

Hi all,

Thanks to the Stephan's advices,  I'm making progress in my small 
planning application and hopefully today I will have a working 
prototype. Now I would like to add some properties to the PlanColumn 
class, one of them is a long description of what the day is gonna be 
about. I can fill it using TextEntreDialogWindow, as in Stephan's code 
but I would like to have a more apt widget for long text. Unfortunately 
I can't find it by myself. Any pointers to where is it? How can I create 
a widget for a long text entry?


Cheers,

Offray

Re: [Pharo-users] load directive

[Tudor Girba]

Also, in the latest GT-InspectorExtensions-Core, you now have the ability
of inspecting the directive, and you can even filter the tree.

If you inspect a load directive you get this (in this case the result is
also filtered by the GT string):

[image: Inline image 2]

It took about 7 minutes to do this. Moldable tools can turn problems on
their head if we use them actively :).

Cheers,
Doru



On Tue, Sep 15, 2015 at 9:32 AM, Usman Bhatti 
wrote:

> On Fri, Sep 11, 2015 at 11:06 PM, Dale Henrichs <
> dale.henri...@gemtalksystems.com> wrote:
>
>> Usman,
>>
>> Off topic --- I don't read all of the pharo posts on both pharo lists,
>> but if you put Metacello in the subject, I have an email filter that alerts
>> me and I read those (more often:) ...
>>
>
> Ok :)
>
>
>>
>> What you are getting with record is what would be loaded in the image, so
>> my guess is that in Pharo4.0 there are equivalent or later versions of all
>> the packages that would be loaded ...
>>
>
> In the versions prior to Pharo4, the directive showed me all the packages
> regardless.
>
>
>>
>> If you are interested in seeing all of the packages that would be loaded
>> (without regard to packages already loaded in image) you can do the
>> following:
>>
>>   ((ConfigurationOfGlamour project version: #stable)
>> ignoreImage: true)
>> record loadDirective
>>
>
> Ok. Thank you for this information.
>
> regards.
>
>
>>
>>
>> Dale
>>
>>
>> On 09/11/2015 01:44 AM, Usman Bhatti wrote:
>>
>> Tx for looking.
>>
>> I did:
>> (ConfigurationOfGlamour project version: #stable) record loadDirective
>> in Moose 5.0 (pharo3) and Moose5.1(pharo4).
>>
>> Here is the difference in the output. And the first (with Pharo3) is much
>> more helpful because with a single command one can understand ALL the
>> packages loaded. Whereas, in Pharo4, we don't get the complete tree and
>> hence one has to see the list of the individual configurations to
>> understand.
>>
>> Pharo3
>> linear load :
>> linear load : 2.1 [ConfigurationOfGlamour]
>> load : ConfigurationOfGrease
>> atomic load : 2.1 [ConfigurationOfGlamour]
>> load : Glamour-Announcements-tg.5
>> load : Glamour-Helpers-TudorGirba.25
>> long list continues--
>> linear load : 2.162 [ConfigurationOfMondrian]
>> load : ConfigurationOfHealthReportProducer
>> linear load : 2.162 [ConfigurationOfMondrian]
>> load : ConfigurationOfShapeST80
>> atomic load : 2.162 [ConfigurationOfMondrian]
>> linear load : 1.7 [ConfigurationOfHealthReportProducer]
>> load : ConfigurationOfXMLSupport
>> atomic load : 1.7 [ConfigurationOfHealthReportProducer]
>> explicit load : XMLSupport
>> load : ConfigurationOfXMLSupport-monty.75
>> load : HealthReportProducer-Ivan_Rojas.13
>> load : Nile-Base-DamienCassou.81
>> load : Mondrian-ComplexShape-AlexandreBergel.33
>> long list continues--
>>
>> Pharo4
>> linear load :
>> linear load : 3.3.0 [ConfigurationOfGlamour]
>> load : ConfigurationOfMagritte3
>> atomic load : 3.3.0 [ConfigurationOfGlamour]
>> linear load : 1.14 [ConfigurationOfRoassal2]
>> linear load : 11 [ConfigurationOfNeoJSON]
>> load : Neo-JSON-Tests-SvenVanCaekenberghe.29
>> linear load : 3.5.0 [ConfigurationOfMagritte3]
>> load : Magritte-Pharo3-Model
>> load : CollectionExtensions-TudorGirba.41
>> load : Glamour-Roassal2-Presentations-TudorGirba.38
>>
>>
>>
>> regards.
>>
>> On Thu, Sep 10, 2015 at 8:53 PM, stepharo  wrote:
>>
>>> (ConfigurationOfStore project version: #stable) record loadDirective
>>>
>>> linear load :
>>> linear load : 0.10 [ConfigurationOfStore]
>>> linear load : 0.2 [ConfigurationOfGarage]
>>> load : ConfigurationOfTalkFFI
>>> linear load : 0.2 [ConfigurationOfGarage]
>>> load : Store-StephaneDucasse.13
>>>
>>>
>>
>>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

[Pharo-users] RubMethodEditingExample subclasses Model?

[Stephan Eggermont]

Why are RubMethodEditingExample and RubPluggableTextMorphExample
subclasses of Model?

Stephan

Re: [Pharo-users] load directive

[Usman Bhatti]

On Fri, Sep 11, 2015 at 11:06 PM, Dale Henrichs <
dale.henri...@gemtalksystems.com> wrote:

> Usman,
>
> Off topic --- I don't read all of the pharo posts on both pharo lists, but
> if you put Metacello in the subject, I have an email filter that alerts me
> and I read those (more often:) ...
>

Ok :)


>
> What you are getting with record is what would be loaded in the image, so
> my guess is that in Pharo4.0 there are equivalent or later versions of all
> the packages that would be loaded ...
>

In the versions prior to Pharo4, the directive showed me all the packages
regardless.


>
> If you are interested in seeing all of the packages that would be loaded
> (without regard to packages already loaded in image) you can do the
> following:
>
>   ((ConfigurationOfGlamour project version: #stable)
> ignoreImage: true)
> record loadDirective
>

Ok. Thank you for this information.

regards.


>
>
> Dale
>
>
> On 09/11/2015 01:44 AM, Usman Bhatti wrote:
>
> Tx for looking.
>
> I did:
> (ConfigurationOfGlamour project version: #stable) record loadDirective
> in Moose 5.0 (pharo3) and Moose5.1(pharo4).
>
> Here is the difference in the output. And the first (with Pharo3) is much
> more helpful because with a single command one can understand ALL the
> packages loaded. Whereas, in Pharo4, we don't get the complete tree and
> hence one has to see the list of the individual configurations to
> understand.
>
> Pharo3
> linear load :
> linear load : 2.1 [ConfigurationOfGlamour]
> load : ConfigurationOfGrease
> atomic load : 2.1 [ConfigurationOfGlamour]
> load : Glamour-Announcements-tg.5
> load : Glamour-Helpers-TudorGirba.25
> long list continues--
> linear load : 2.162 [ConfigurationOfMondrian]
> load : ConfigurationOfHealthReportProducer
> linear load : 2.162 [ConfigurationOfMondrian]
> load : ConfigurationOfShapeST80
> atomic load : 2.162 [ConfigurationOfMondrian]
> linear load : 1.7 [ConfigurationOfHealthReportProducer]
> load : ConfigurationOfXMLSupport
> atomic load : 1.7 [ConfigurationOfHealthReportProducer]
> explicit load : XMLSupport
> load : ConfigurationOfXMLSupport-monty.75
> load : HealthReportProducer-Ivan_Rojas.13
> load : Nile-Base-DamienCassou.81
> load : Mondrian-ComplexShape-AlexandreBergel.33
> long list continues--
>
> Pharo4
> linear load :
> linear load : 3.3.0 [ConfigurationOfGlamour]
> load : ConfigurationOfMagritte3
> atomic load : 3.3.0 [ConfigurationOfGlamour]
> linear load : 1.14 [ConfigurationOfRoassal2]
> linear load : 11 [ConfigurationOfNeoJSON]
> load : Neo-JSON-Tests-SvenVanCaekenberghe.29
> linear load : 3.5.0 [ConfigurationOfMagritte3]
> load : Magritte-Pharo3-Model
> load : CollectionExtensions-TudorGirba.41
> load : Glamour-Roassal2-Presentations-TudorGirba.38
>
>
>
> regards.
>
> On Thu, Sep 10, 2015 at 8:53 PM, stepharo  wrote:
>
>> (ConfigurationOfStore project version: #stable) record loadDirective
>>
>> linear load :
>> linear load : 0.10 [ConfigurationOfStore]
>> linear load : 0.2 [ConfigurationOfGarage]
>> load : ConfigurationOfTalkFFI
>> linear load : 0.2 [ConfigurationOfGarage]
>> load : Store-StephaneDucasse.13
>>
>>
>
>