[Pharo-users] Morphic is super slow

Ben Coman btc at openinworld.com
Sat Jan 16 09:23:37 EST 2016


Okay. So I haven't with git from Pharo before.  What definite actions
do I need to take to update?

I see the github://kilon/ChronosManager:master repository only contains:
* one BaselineOfChronosManager.package revision 4, which is the current loaded
* one ChronosManager.package revision 62, which is the current loaded

How do I get those to show a later version that I can load?

Also, if I click on <History> for ChronosManager.package revision 62,
then from ChronosManager-kilonAlios.61 context menu I select <View
changes> it gives an error: "Error: Could not find version
'ChronosManager-kilonAlios.61'. Maybe you need to add a repository?"
  Being familiar with git command line that is somewhat expected, but
could those more familiar with its usage in Pharo comment on this?

cheers -ben

On Sat, Jan 16, 2016 at 9:41 PM, Dimitris Chloupis
<kilon.alios at gmail.com> wrote:
> there is no need to update the catalog, my project is in github and catalog
> always loads the latest github version .
>
> One of the advantages of using github ;)
>
> and any change I do my code is immediately commited and pushed into github.
>
> On Sat, Jan 16, 2016 at 3:37 PM Ben Coman <btc at openinworld.com> wrote:
>>
>> On Sat, Jan 16, 2016 at 8:43 PM, Dimitris Chloupis
>> <kilon.alios at gmail.com> wrote:
>> > Hello Ben with your help and some more digging around I managed to solve
>> > my
>> > issues and I am now also able to update the taskbar button moprh without
>> > any
>> > major hit to my cpu. Pharo is now at 6-7% of one core which is not bad
>> > at
>> > all.
>> >
>> > So what you mention does not seem to affect my performance. However
>> > there is
>> > still the problem of ChronoManager taking over a second to open its gui
>> > .
>>
>> That profile report didn't format very well. Probably better to put it
>> in a text file to attach.
>> let me know when you've updated the catalog and I'll take another look.
>>
>> cheers -ben
>>
>




More information about the Pharo-users mailing list