[Pharo-users] Morphic is super slow

Dimitris Chloupis kilon.alios at gmail.com
Sat Jan 16 09:45:18 EST 2016


Ben is super simple with github, you just load it from package browser in a
clean image (it will always get the latest version) or if you want to get
the latest version on top of existing ChronosManager version , because
Package Browser has a problem that does not get the latest version when you
have one older version already loaded

you do

Metacello new baseline: 'ChronosManager'; repository:
'github://kilon/ChronosManager'; get; load



On Sat, Jan 16, 2016 at 4:25 PM Ben Coman <btc at openinworld.com> wrote:

> 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
> >>
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/attachments/20160116/2658c542/attachment.html>


More information about the Pharo-users mailing list