Re: [Pharo-users] Minimizing an Application

ah ok , thanks for the clarification , Craig and Tim , this makes more sense to me now :) On Sat, Aug 26, 2017 at 3:44 AM Craig Latta wrote: > > Hi-- > > > > > ...10mbs which is the size pharo image can be reduced to is > > > > nothing for todays TBs hard drives and

Re: [Pharo-users] Minimizing an Application

Hi-- > > > ...10mbs which is the size pharo image can be reduced to is > > > nothing for todays TBs hard drives and GBs flash drives and > > > online storage. Unless you do an embedded app and 10 mbs are huge > > > for your limited storage. > > > > Or you want to minimize initial startup time,

Re: [Pharo-users] Minimizing an Application

It is always easier to start than to finish something. :) For the small core we are getting there as Guillermo work showed it to us. 70 is bootstrap from source. Do you believe it? It is real and tangible. People can do it on their own machine. And this is just the start. Now we have our roadmap

Re: [Pharo-users] Minimizing an Application

Mariano's PhD was on this - as mentioned it to me a few weeks ago. This was one of the reasons for building fuel - to enable this sort of thing on top - and he proved it worked. Dimitrus - the idea is to I have a small core that loads quick and then less used elements can be paged in when

Re: [Pharo-users] Minimizing an Application

I still dont know what opening has to do with transmitting, even when you do it remotely , a socket / websocket connection should be all you need. For me transmitting the entire image would be necessary only in the case you want to install it remotely and that remote location has no immediate

Re: [Pharo-users] Minimizing an Application

I understand that to mean effectively that you are "opening" the image across the net - so eventually you need to whole image transmitted, but you don't have to wait for the whole thing before you start running it. cheers -ben On Fri, Aug 25, 2017 at 2:00 AM, Dimitris Chloupis

Re: [Pharo-users] Minimizing an Application

2017-08-24 14:51 GMT-03:00 stephan : > On 22-08-17 12:46, horrido wrote: >> >> If you start with a minimal imaqe, it's not obvious to me how you'd add a >> missing class and pull in all of its dependencies (which can be >> voluminous). >> And for a large application, there could

Re: [Pharo-users] Minimizing an Application

Indeed that can be a barrier but why you would want to transmit an entire image instead of portion of it using something like fuel files or other binary formats ? It would dramatically reduce the size of data you transmit. On Thu, Aug 24, 2017 at 8:10 PM Craig Latta

Re: [Pharo-users] Minimizing an Application

On 22-08-17 12:46, horrido wrote: If you start with a minimal imaqe, it's not obvious to me how you'd add a missing class and pull in all of its dependencies (which can be voluminous). And for a large application, there could be many, many missing classes. This sounds rather arduous. That has

Re: [Pharo-users] Minimizing an Application

> ...10mbs which is the size pharo image can be reduced to is nothing > for todays TBs hard drives and GBs flash drives and online storage. > Unless you do an embedded app and 10 mbs are huge for your limited > storage. Or you want to minimize initial startup time, including the time it

Re: [Pharo-users] Minimizing an Application

Pharo desperately needs an image management tool. But in the end it will be up to the code hero that will decided the bite the bullet and do it. There are like a ton of things that can improve and a ton of potential ideas and projects, this is just one. It wont be easy though because code inside

Re: [Pharo-users] Minimizing an Application

We would like to have dll like deployment too. But I'm too dull to know how to do implement it. Stef On Tue, Aug 22, 2017 at 2:17 PM, Esteban A. Maringolo wrote: > VAST provided such image deployment tool, where you could save the > deployment instructions, as whether to

Re: [Pharo-users] Minimizing an Application

VAST provided such image deployment tool, where you could save the deployment instructions, as whether to include/exclude certain packages, classes, methods, etc. It was great, although it wasn't "easy" to work with. Dolphin Smalltalk has an Image Stripper, that does something like that, but by

Re: [Pharo-users] Minimizing an Application

Hi Richard, If you make sure that you have a seed and maps of dependencies for all the packages you use then you can build daily your project with a integration farm. I worked with Envy and I was used to load in one click a working or deployed image. And it worked. Then working on the granularity

Re: [Pharo-users] Minimizing an Application

If you start with a minimal imaqe, it's not obvious to me how you'd add a missing class and pull in all of its dependencies (which can be voluminous). And for a large application, there could be many, many missing classes. This sounds rather arduous. Tim Mackinnon wrote > There has been a lot of

Re: [Pharo-users] Minimizing an Application

VA Smalltalk doesn't strip an image; it builds a new image based on application dependencies. With VA's packaging functionality, you are more likely to get a packaging error that reports you are trying to use something that isn't reachable according to the defined dependencies. I admit that

Re: [Pharo-users] Minimizing an Application

There has been a lot of great work on this front on the Pharo side from the "team" and PharoLambda has made use of it (although it's a tiny project). My footprint is ~22mb including vm & image. And leaving out sources. The ./scripts directory has the example of how to do it, along side the