Hi again, I played a bit with the online demo. Do you have implemented a basic file browser with DOM (not canvas) UI? But it is not compatible at the Morphic level, right? So it is not a DOM element based backend that existing Morphic applications could use..? Also, what happens when you have an exception in code in a DOM callback like xhr completed or a click event? Does it pop up a real Squeak debugger and allows coding in the debugger like real smalltalk? Cheers, Siemen Sent from my iPhone
On 20 Jul 2018, at 11.27, Siemen Baader <siemenbaader@gmail.com> wrote:
Ok, Thanks!
:) Siemen
Sent from my iPhone
On 20 Jul 2018, at 10.08, Craig Latta <craig@blackpagedigital.com> 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 craig@blackpagedigital.com +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)