Re: [Pharo-dev] Creating the smallest server runtime footprint

As an aside, I’ve just noticed that I get the same error in a normal 6.1 image when you try to load a baselineof package in Iceberg using the install menu option. So I wonder if this might actually be a bug in the image that the minimal version is getting as well? Tim > On 1 Aug 2017, at

[Pharo-dev] Question about Bloc

Hi! We were wondering whether someone did some workload with Bloc. How many elements can Bloc render, at the same time? Is there a support for Quad-Tree ? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu

Re: [Pharo-dev] Creating the smallest server runtime footprint

Yes, you should be able to load an mcz in that image by doing: (MCDirectoryRepository new directory: 'where-your-mcz-is') loadVersionFromFileNamed: 'Metacello-GitBasedRepository-Author.1.mcz') load. Guille On Wed, Aug 2, 2017 at 7:57 AM, Pavel Krivanek wrote: > >

Re: [Pharo-dev] [IMPORTANT] Following changes in the bootstrapping process

Hi Pavel, On Tue, Aug 01, 2017 at 11:57:23AM +0200, Pavel Krivanek wrote: > Hello, > > we are checking a huge pull request #177 (https://github.com/pharo-project/ > pharo/pull/177) that will change some basics of the bootstrap process: > > ... > > So please, try to look at the PR and test the

Re: [Pharo-dev] [IMPORTANT] Following changes in the bootstrapping process

2017-08-02 9:28 GMT+02:00 Alistair Grant : > Hi Pavel, > > On Tue, Aug 01, 2017 at 11:57:23AM +0200, Pavel Krivanek wrote: > > Hello, > > > > we are checking a huge pull request #177 (https://github.com/pharo- > project/ > > pharo/pull/177) that will change some basics of

Re: [Pharo-dev] [IMPORTANT] Following changes in the bootstrapping process

On Wed, Aug 02, 2017 at 09:35:02AM +0200, Pavel Krivanek wrote: > > > 2017-08-02 9:28 GMT+02:00 Alistair Grant : > > Hi Pavel, > > On Tue, Aug 01, 2017 at 11:57:23AM +0200, Pavel Krivanek wrote: > > Hello, > > > > we are checking a huge pull

Re: [Pharo-dev] Calypso browser and categories?

On Tue, Aug 1, 2017 at 11:32 AM, Denis Kudriashov wrote: > And I released new version with all fixes > > Cool! I just tested and everything seems to work nicely. Thanks Denis for the fixes and new release. A pleasure to be using this browser. You know... it's easier for me

Re: [Pharo-dev] Lots of "UTF8InvalidText: Invalid utf8 input detected" from OMBU

On Tue, Aug 1, 2017 at 11:34 AM, Martin Dias wrote: > Hello: > So, is this patch working fine? > > Well...it's has been a couple of days already and I haven't seen the issue again, so I guess yes, the workaround works... > Cheers > Martin > > On Thu, Jul 27, 2017 at

Re: [Pharo-dev] Calypso browser and categories?

2017-08-02 13:55 GMT+02:00 Mariano Martinez Peck : > > > On Tue, Aug 1, 2017 at 11:32 AM, Denis Kudriashov > wrote: > >> And I released new version with all fixes >> >> > Cool! I just tested and everything seems to work nicely. Thanks Denis for > the

Re: [Pharo-dev] [IMPORTANT] Following changes in the bootstrapping process

Pavel Krivanek-3 wrote > - Deprecated FileStream & childs (Moved to Deprecated70) *Counts direct references to FileStream & subclasses in a 6.1 Moose image* Brave souls! I hope the migration guide will be up to snuff, or I imagine a large percentage will be staying on 7.0 for a looong while :)

Re: [Pharo-dev] Creating the smallest server runtime footprint

Ah, I think I’m starting to get closer to what I need… So if I want to load in that last piece to enable more general remote loading - how do I figure out how to do that? I’m trying to work out where the build steps for building up the image (can I see them in Jenkins? It wasn’t clear to me if

Re: [Pharo-dev] Epicea: Revert the removal of a class

tinchodias wrote > However, I can say the Epicea changes browser is prepared > to this scenario because it delays its UI refresh some milliseconds after > a > change announcement happened. Can verify this really helps, having loaded large batches in a 6.1 image (with no other browsers open, for

Re: [Pharo-dev] [IMPORTANT] Following changes in the bootstrapping process

Thanks guille and pablo for the explanation. One day we will have to work on a fuel solution for binary code loading. On Wed, Aug 2, 2017 at 7:02 AM, Guillermo Polito wrote: > Hi all, > > I think Pablo answered most of the questions. But there is another > important

Re: [Pharo-dev] [IMPORTANT] Following changes in the bootstrapping process

>> - Deprecated FileStream & childs (Moved to Deprecated70) > > *Counts direct references to FileStream & subclasses in a 6.1 Moose image* > Brave souls! It means that Moose will have to update. These classes are not gone just deprecated. > I hope the migration guide will be up to snuff, or I

Re: [Pharo-dev] [IMPORTANT] Following changes in the bootstrapping process

Stephane Ducasse-3 wrote >>> - Deprecated FileStream & childs (Moved to Deprecated70) >> >> *Counts direct references to FileStream & subclasses in a 6.1 Moose >> image* >> Brave souls! > > It means that Moose will have to update. These classes are not gone > just deprecated. Not just Moose,