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
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 loca
> 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
Very good!
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?
Thanks for the details so far!
Siemen
On
> The minimal example seems to load fast enough. Do you think there is a
> potential to slim it down even further for a production system that
> uses the DOM as its UI, ie remove morphic and others and use the image
> in headless mode?
Certainly. I've done some experiments with "animated wi
Hi Craig,
Great, thanks! The minimal example seems to load fast enough. Do you think
there is a potential to slim it down even further for a production system that
uses the DOM as its UI, ie remove morphic and others and use the image in
headless mode?
Thanks for the offer to work together on
Hi Erik--
> I read in some of the more recent issues that on some mobile devices
> (based on iOS) the page reloads after switching apps and/or locking
> the device. This will loose any data currently in the Caffeine app.
> Craig is working on a solution based on WebWorkers. This probably
> means
Hi Siemen--
> What is the status of Caffeine now - is it production-ready with
> Pharo, and how large is a minimal (not development) image with
> everything required to run a production system - i.e. what would be
> the load time of a Caffeine web app?
I'm using Caffeine in production wi
Thanks!
My idea was to use it in a similar manner to e.g. Angular, with a full app
being loaded into the browser which communicates with a backend API. But this
requires the load time to be acceptable.. another direction would be to embed
it in a phone gap app and use it to build DOM-based mobi
You can find the source at the GitHub-link below. Craig seems active on this
project seeing the number of recent commits. Focus is on creating a live
VR-environment. Cool stuff I think . It will run Pharo, but if that means
'production ready'... Small image sizes for production systems/applications
On 19 July 2018 at 14:59, Siemen Baader wrote:
> What is the status of Caffeine now - is it production-ready with Pharo, and
> how large is a minimal (not development) image with everything required to
> run a production system - i.e. what would be the load time of a Caffeine web
> app?
>
> Tha
What is the status of Caffeine now - is it production-ready with Pharo, and how
large is a minimal (not development) image with everything required to run a
production system - i.e. what would be the load time of a Caffeine web app?
Thanks,
Siemen
Sent from my iPhone
12 matches
Mail list logo
