Le 29/09/2018 à 01:05, Guillermo Polito a écrit :
> I'm sorry if I offended somebody. I've deleted the repository (it was
> under pharo-repository, not under my name). With it the changes I made
> to make it work on Pharo7.
>
> I understand that Peter's tool is easy, i've used it before.
> But I
On Sat, Sep 29, 2018 at 1:05 AM Guillermo Polito
wrote:
> I'm sorry if I offended somebody. I've deleted the repository (it was
> under pharo-repository, not under my name). With it the changes I made to
> make it work on Pharo7.
>
> I understand that Peter's tool is easy, i've used it before.
>
I'm sorry if I offended somebody. I've deleted the repository (it was under
pharo-repository, not under my name). With it the changes I made to make it
work on Pharo7.
I understand that Peter's tool is easy, i've used it before.
But I have my constraints, as others has theirs.
Just note that lot
Ah yes - the newer Tonel format should help - I haven’t consciously noticed
when having slow loading if all of the dependencies were Tonel2.
I still wonder if we may have a code loading perf issue overall - not sure if
it’s ever been measured (might be a great summer project for someone).
Hi,
I don't remember to be annoyed by the loading time of GToolkit.
Regarding DrGeo it is installed from Tonel file format repository (which
is local too), and it is usually very fast. Oh! But P6.1 may not be up
to the task with Tonel? I don't remember clearly all the reason why I
skipped P6 (the
> Am 28.09.2018 um 10:14 schrieb Guillermo Polito :
>
>
>
>> On Fri, Sep 28, 2018 at 9:07 AM Torsten Bergmann wrote:
>> Hi Guille,
>>
>> Yes, thanks. But it looks like the history is gone now - as you seem to load
>> and then commited
>> with Iceberg only.
>
> Yes, that's what I did.
>
Hi,
I have found that moving the image and changes files onto a RAMdisk makes a
huge difference to the install time of large packages.
Give it a try.
Craig
-Original Message-
From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of Tim
Mackinnon
Sent: Friday, 28
Hi,
Please load the whole GT. Also, in the meantime we switched to Tonel which
should speedup the loading time significantly.
Cheers,
Doru
> On Sep 28, 2018, at 7:53 PM, Tim Mackinnon wrote:
>
> When I installed GTDocumenter into a clean P61 image it took a really long
> time (like 20+
When I installed GTDocumenter into a clean P61 image it took a really long time
(like 20+ mins), so it may be something you have to wait out.
It does beg the question why it takes so long? Actually all of our code loading
is quite slow compared to other languages that load a lot more code. Not
+1000
Please use the git-migration tool. Keeping the history is important. Takes only
a couple of minutes to do
> Am 28.09.2018 um 09:06 schrieb Torsten Bergmann :
>
> Hi Guille,
>
> Yes, thanks. But it looks like the history is gone now - as you seem to load
> and then commited
> with
On Fri, Sep 28, 2018 at 9:07 AM Torsten Bergmann wrote:
> Hi Guille,
>
> Yes, thanks. But it looks like the history is gone now - as you seem to
> load and then commited
> with Iceberg only.
>
Yes, that's what I did.
>
> By using Peters "STHub -> Git migration tool" the history of the changes
Hi Guille,
Yes, thanks. But it looks like the history is gone now - as you seem to load
and then commited
with Iceberg only.
By using Peters "STHub -> Git migration tool" the history of the changes is
preserved and moved into
the git history too. See
12 matches
Mail list logo
