I use different tools to follow the mailing list. One of which is
forum.world.st.
If you take a look down this thread, you'll notice the problem:
http://forum.world.st/Tell-me-about-your-workflow-td4729308.html
Ouch!
Well, I guess then you have noticed what is my problem when I answer a mail
Thierry wrote:
>could you please include some quoted text in your answer? I am unable to know
>to whom you are answering, my mailer only
>classifying mails in a thread based on their date, and I need a minimum of
>quotes to be able to track the conversation.
I use different tools to follow the
De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Stephan
Eggermont [step...@stack.nl]
Date d'envoi : lundi 16 décembre 2013 20:26
À : pharo-dev@lists.pharo.org
Objet : Re: [Pharo-dev] Tell me about your workflow
I don't read posts that I cannot re
> *De :* Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de
> Stéphane Ducasse [stephane.duca...@inria.fr]
> *Date d'envoi :* vendredi 13 décembre 2013 13:47
>
> *À :* Pharo Development List
> *Objet :* Re: [Pharo-dev] Tell me about your workflow
>
I don't read posts that I cannot read.
Please remove non-relevant quoted text.
Stephan
:47
À : Pharo Development List
Objet : Re: [Pharo-dev] Tell me about your workflow
try with Moose.
Stef
On Dec 12, 2013, at 4:20 PM, Yuriy Tymchuk
mailto:yuriy.tymc...@me.com>> wrote:
Pharo10 on SmalltalkHub is humongous. You can definitely do a stress test with
it :)
Uko
On 12 Dec 201
Then I will :)
Thierry
De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Stéphane
Ducasse [stephane.duca...@inria.fr]
Date d'envoi : vendredi 13 décembre 2013 13:47
À : Pharo Development List
Objet : Re: [Pharo-dev] Tell me about your workflow
idea of creating one randomly ;)
>>
>> Thierry
>>
>> De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Yuriy
>> Tymchuk [yuriy.tymc...@me.com]
>> Date d'envoi : jeudi 12 décembre 2013 15:37
>> À : Pharo Development List
>> Obje
tian
Sastre [sebast...@flowingconcept.com]
Date d'envoi : vendredi 13 décembre 2013 14:57
À : Pharo Development List
Objet : Re: [Pharo-dev] Tell me about your workflow
I can try a forced load on a 3.0 ignoring requisites for testing purposes
but I'm using this:
https://github.com/dalehenrich/file
redi 13 décembre 2013 14:32
> À : Pharo Development List
> Objet : Re: [Pharo-dev] Tell me about your workflow
>
> A bit.
>
> This is from today's current version (and is not all, it's only the two
> biggest packages):
>
> (MCPackage named: 'flow') wor
ncept.com]
Date d'envoi : vendredi 13 décembre 2013 14:32
À : Pharo Development List
Objet : Re: [Pharo-dev] Tell me about your workflow
A bit.
This is from today's current version (and is not all, it's only the two biggest
packages):
(MCPackage named: 'flow') workingCopy p
the version file:
> 202796.
>
> Is that a lot lower than your count?
>
> Thierry
>
> De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Sebastian
> Sastre [sebast...@flowingconcept.com]
> Date d'envoi : vendredi 13 décembre 2013 13:34
>
d'envoi : vendredi 13 décembre 2013 13:34
À : Pharo Development List
Objet : Re: [Pharo-dev] Tell me about your workflow
how many coreMethods?
On Dec 13, 2013, at 7:00 AM, GOUBIER Thierry
mailto:thierry.goub...@cea.fr>> wrote:
Bad news. Roassal package directory has 355 entries (
doesn't seems long.
>
> I'll do some profiling.
>
> Thierry
> De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de GOUBIER
> Thierry
> Date d'envoi : jeudi 12 décembre 2013 17:07
> À : Pharo Development List
> Objet : [PROVENANCE INTERNET] Re
faster, mate :):):)
Thierry
De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de GOUBIER Thierry
Date d'envoi : vendredi 13 décembre 2013 10:00
À : Pharo Development List
Objet : [PROVENANCE INTERNET] Re: [Pharo-dev] Tell me about your workflow
e : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de GOUBIER Thierry
Date d'envoi : jeudi 12 décembre 2013 17:07
À : Pharo Development List
Objet : [PROVENANCE INTERNET] Re: [Pharo-dev] Tell me about your workflow
Thanks for the pointers.
I'll look at Seaside/Moose/Mondrian and
Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Yuriy Tymchuk
[yuriy.tymc...@me.com]
Date d'envoi : jeudi 12 décembre 2013 16:24
À : Pharo Development List
Objet : Re: [Pharo-dev] Tell me about your workflow
So if you want something big and with a lot of commits you can use Pharo* i
er complained
>>>
>>> let me know
>>>
>>>
>>>
>>>
>>>
>>> On Dec 12, 2013, at 3:53 AM, GOUBIER Thierry wrote:
>>>
>>>> If you would be ready to profile a package save on your repository, it
>
ierry
>>
>> De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Yuriy
>> Tymchuk [yuriy.tymc...@me.com]
>> Date d'envoi : jeudi 12 décembre 2013 15:37
>> À : Pharo Development List
>> Objet : Re: [Pharo-dev] Tell me about your workflow
>>
gt; Tymchuk [yuriy.tymc...@me.com]
> Date d'envoi : jeudi 12 décembre 2013 15:37
> À : Pharo Development List
> Objet : Re: [Pharo-dev] Tell me about your workflow
>
> Are you interested in a package or a project? I can provide you information
> based on size, etc…
>
&
creating one randomly ;)
Thierry
De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Yuriy Tymchuk
[yuriy.tymc...@me.com]
Date d'envoi : jeudi 12 décembre 2013 15:37
À : Pharo Development List
Objet : Re: [Pharo-dev] Tell me about your work
course. Is Roassal
> large enough?
>
> Thierry
>
> De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Sebastian
> Sastre [sebast...@flowingconcept.com]
> Date d'envoi : jeudi 12 décembre 2013 12:12
> À : Pharo Development List
> Objet : Re: [Pharo-dev] Tell
7;envoi : jeudi 12 décembre 2013 12:12
À : Pharo Development List
Objet : Re: [Pharo-dev] Tell me about your workflow
gee the big code package is airflowing which I have, quite conservatively,
running on #14438 images
I load filetree like this:
Gofer new
url: 'http://ss3.gems
11 décembre 2013 17:09
> À : Pharo Development List
> Objet : Re: [Pharo-dev] Tell me about your workflow
>
> ok, if saving is dumping all, then 3 is confirmed? After the first commit,
> I'd say so.
>
> about 2, I don't know. I'm available to make tests and meas
o-dev-boun...@lists.pharo.org] de la part de Sebastian
Sastre [sebast...@flowingconcept.com]
Date d'envoi : mercredi 11 décembre 2013 17:09
À : Pharo Development List
Objet : Re: [Pharo-dev] Tell me about your workflow
ok, if saving is dumping all, then 3 is confirmed? After the first commit, I
ok, if saving is dumping all, then 3 is confirmed? After the first commit, I'd
say so.
about 2, I don't know. I'm available to make tests and measure results
have a nice trip, keep us tuned about any progress
On Dec 11, 2013, at 2:09 PM, Goubier Thierry wrote:
> Yes, you're right in the
Yes, you're right in the general case.
But a solution to that general problem will take time to be implemented
(time I lack at the moment, sadly) and if the main gain is a few %
because it's writing the version file and the metadata for methods which
are the "slow" factors, then we'll have wor
Without entering in details, a cause for slow package write is dumping all
every time.
For that strategy, we already have the image save which is magically fast.
So, if we make something to scan the code and write only when it's different
from what's on disk, then we would be preventing tons of
Le 11/12/2013 16:27, Esteban Lorenzano a écrit :
ah, and IMHO the problem is not about reading... is about writing (if it
has to write the metadata each time...).
But, personnaly, I don't know if this is the reason for the lack of
performance...
I have three hypothesis for Sebastian proble
that would be sooo cool. Thanks Thierry!
Esteban
On Wed, Dec 11, 2013 at 4:39 PM, Goubier Thierry wrote:
> Thanks. I'll have a look.
>
> If this format solves the git merge conflicts, I'll be porting it. But
> I'll make sure first it doesn't have the performance problems Sebastian is
> telling
Thanks. I'll have a look.
If this format solves the git merge conflicts, I'll be porting it. But
I'll make sure first it doesn't have the performance problems Sebastian
is telling about.
Because if it is just removing writing the metadata in gitfiletree, it's
a 5 minutes job :).
Thierry
L
ah, and IMHO the problem is not about reading... is about writing (if it
has to write the metadata each time...).
Esteban
On Wed, Dec 11, 2013 at 4:24 PM, Esteban Lorenzano wrote:
> Thierry, I know there is a working version... let me search...
>
> (5 mins later)
>
>
> here:
>
> https://github.
Thierry, I know there is a working version... let me search...
(5 mins later)
here:
https://github.com/rjsargent/CypressReferenceImplementation
Dale says Richard made a metadata-less version.
We should take a look at that.
Esteban
On Wed, Dec 11, 2013 at 4:28 PM, Goubier Thierry wrote:
>
Esteban, Sebastian,
In the filetree code, you will find a format without metadata, but it's
not in use anymore.
If you use gitfiletree, it will write the metadata for compatibility
reasons with filetree, but it will never read it back.
I'm pushing code to make filetree robust to absence of
Le 11/12/2013 15:44, Sebastian Sastre a écrit :
Hi Thierry
On Dec 11, 2013, at 12:43 PM, Goubier Thierry wrote:
I have packages (in the order of hundreds of classes) and save delays
and package click delays are starting to demand patience in a way that
doesn't feel like the right path
Whi
I know there is a version of filetree without metadata (more compelling for
projects that will never use other formats).
Dale told me that there was a preview somewhere, but I didn't tested yet
(lack of time) and now I cannot find the mail...
Dale, can you re-send the link?
cheers,
Esteban
On We
I should breath before I type, but you probably already got that I meant
redundant writes (not reads)...
Anyway.. I was talking with Esteban and he mentions some kind of compatibility
metadata.
If I'm going to give a leap of faith to filetree repos to save code why should
I care about mcz comp
Hi Thierry
On Dec 11, 2013, at 12:43 PM, Goubier Thierry wrote:
>>
>> I have packages (in the order of hundreds of classes) and save delays
>> and package click delays are starting to demand patience in a way that
>> doesn't feel like the right path
>
> Which operations ? I didn't remember noti
Le 11/12/2013 15:18, Sebastian Sastre a écrit :
Are you using git with your Pharo based software?
Yes
If you do, are you using filetree?
gitfiletree (it uses the filetree code path for writing, and a git
archive path for reading)
I ask because I'm worried about scale.
I have packages
Are you using git with your Pharo based software?
If you do, are you using filetree?
I ask because I'm worried about scale.
I have packages (in the order of hundreds of classes) and save delays and
package click delays are starting to demand patience in a way that doesn't feel
like the right p
40 matches
Mail list logo
