Re: [Pharo-users] Status of Caffeine
> What about the UI lag and the occasional spinner that blocks the UI, > is this related to the debugging protocol (I see that the IDEs are > loaded in iframes) that will go away when run from local, or is this > something that can be optimized away? That's just the speed of Morphic. The VM is set up to display the spinner whenever anything takes more than a certain amount of time (one alternative is to just turn it off :). While Morphic in SqueakJS has gotten a lot faster since the first release, just because JavaScript engines have gotten faster, I was still motivated to explore alternatives. That's why I experimented with animated HTML wireframes, morphic.js from Snap, and using a separate HMTL5 canvas for each morph. All three of these approaches are much faster than traditional Morphic. However, the traditional Morphic UI has the appeal that it's pixel-portable between the Web and native apps. thanks again, -C -- Craig Latta Black Page Digital Amsterdam :: San Francisco cr...@blackpagedigital.com +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)
Re: [Pharo-users] Status of Caffeine
Ok, Thanks! :) Siemen Sent from my iPhone > On 20 Jul 2018, at 10.08, Craig Latta wrote: > > >> What about the UI lag and the occasional spinner that blocks the UI, >> is this related to the debugging protocol (I see that the IDEs are >> loaded in iframes) that will go away when run from local, or is this >> something that can be optimized away? > > That's just the speed of Morphic. The VM is set up to display the > spinner whenever anything takes more than a certain amount of time (one > alternative is to just turn it off :). While Morphic in SqueakJS has > gotten a lot faster since the first release, just because JavaScript > engines have gotten faster, I was still motivated to explore > alternatives. That's why I experimented with animated HTML wireframes, > morphic.js from Snap, and using a separate HMTL5 canvas for each morph. > > All three of these approaches are much faster than traditional > Morphic. However, the traditional Morphic UI has the appeal that it's > pixel-portable between the Web and native apps. > > > thanks again, > > -C > > -- > Craig Latta > Black Page Digital > Amsterdam :: San Francisco > cr...@blackpagedigital.com > +31 6 2757 7177 (SMS ok) > + 1 415 287 3547 (no SMS) >
Re: [Pharo-users] Changing a BaselineOf... to include one more package
> On 16 Jul 2018, at 07:27 , Guillermo Polito wrote:
>
> - I've cloned SmaCC
> - I've checked out the flgr branch
> - I've loaded the baseline and added
>
>> spec package: 'SmaCC-Reification' with: [ spec requires:
>> #('SmaCC-Smalltalk-Parser' 'SmaCC-Runtime' 'SmaCC-Java') ]
> - then, I've done right click on the iceberg project and selected Metacello
> -> load baseline... => then inserted SmaCC-Reification and I got that package
> + dependencies loaded...
Well, I thought that was what I did before. I tried this again, and — lo and
behold — it worked! Thank you.
>
>
> Moreover, my original problem is still there — it's looking in a nonexistent
> package cache, rather than on github, or in my ~/iceberg/apblack/SmaCC clone
> of github.
>
> I don't think this is quite like that... Metacello will try to lookup the
> package in several places. And it will check at last the package cache. So it
> fails because it was not able to found that package in any of your
> repositories, but the last it checked was the package cache.
What still is not working is trying to reference SmaCC-Reficiation from
baselineOfGrace.
In `baselineOfGrace` I’ve put:
spec package: 'Grace-Parser' with: [ spec requires: {'SmaCC' .
'SmaCC-Reification'. 'Grace-Scope'} ]
but I still get the walkback
> Could not resolve: BaselineOfSmaCC-Reification [BaselineOfSmaCC-Reification]
> in /Users/black/Development/Pharo/images/Pharo 7.0 SmallGrace
> 32/pharo-local/package-cache g...@github.com:apblack/SmaCC.git[fglr]
I took that message to mean that it was listing all the places that it had
looked: first the non-existant package cache, and then githib. Is that wrong?
Is it actually looking in my shared iceberg directory, but just not saying so?
Does this only work after I have pushed everything to github? I like to get it
working before I push.
Andrew
Re: [Pharo-users] Changing a BaselineOf... to include one more package
I’ve spent another couple of hours on this, and here is where I stand. I can get SmaCC-Reification to load if I use the "load ...” menu in the Montecello extension menu to Iceberg — but only if I select the fglr branch manually. (this is reasonable, because that group is not on the working branch) I can’t get SmaCC-Reification to load as a dependency for Grace-Parser. I’ve tried pushing everything back to github. I’ve tried temporarily moving my git repos into the image directory (i.e., I’ve turned off the Iceberg setting to use a shared iceberg directory.) I still get > Could not resolve: BaselineOfSmaCC-Reification [BaselineOfSmaCC-Reification] > in /Users/black/Development/Pharo/images/Pharo 7.0 SmallGrace > 33/pharo-local/package-cache g...@github.com:apblack/SmaCC.git[fglr] I get this message even after I have loaded SmaCC-Reification by hand. I don’t know what else to try! My repo is on github: apblack/GraceInPharo.I’m stranded until I can get this working. Andrew
