- Pharo-dev - lists.pharo.org

Re: [Pharo-project] How to force Metacello to use the package cache?

by Frank Shearar

On 28 January 2013 19:02, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Frank Shearar-3 wrote >> I was under the impression that it >> only did if the various ConfigurationOf authors thought to use the >> package-cache... > > The package cache does not have to be explicitly included. In fact, I've > never seen a configuration done that way. Ah, I may be confusing "loading a package" with "bootstrapping". Most ConfigurationOfs I've seen have bootstrapping that's broken in the face of no internet connection. My latest submission of ConfigurationOfPetitParser to this list contains a partial fix for the offline case, in fact. (*ping* to the PetitParser gods) frank > Cheers, > Sean > > > > -- > View this message in context: http://forum.world.st/How-to-force-Metacello-to-use-the-package-cache-tp466… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 28, 2013

Re: [Pharo-project] How to force Metacello to use the package cache?

by Sean P. DeNigris

Frank Shearar-3 wrote > I was under the impression that it > only did if the various ConfigurationOf authors thought to use the > package-cache... The package cache does not have to be explicitly included. In fact, I've never seen a configuration done that way. Cheers, Sean -- View this message in context: http://forum.world.st/How-to-force-Metacello-to-use-the-package-cache-tp466… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 28, 2013

Re: [Pharo-project] TxTextMorph based on new text model

by Sean P. DeNigris

Denis Kudriashov wrote > I like what they do inside rules. It is > really simple and understandable code. Maybe I will try reuse something. Very good. I am not suggesting we copy the exact approach, just learn any lessons so we don't have to repeat the mistakes of the past. Sean -- View this message in context: http://forum.world.st/TxTextMorph-based-on-new-text-model-tp4663219p4665942… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 28, 2013

Re: [Pharo-project] How to force Metacello to use the package cache?

by StÃ©phane Ducasse

On Jan 28, 2013, at 3:38 PM, Frank Shearar wrote: > I'm trying out a trick with extending Installer to always try load > from package-cache. Perhaps Gofer can be similarly tweaked? It does it per default. This is even explained in the Gofer chapter :). > > (I did it by making Installer use an MCRepositoryGroup, which iterates > over its contained repositories... and tries the package-cache first.) > > frank > > On 28 January 2013 18:02, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> for me it systematically loads everyghing so I'm trying to nuke it in gofer >> kind of I put the enable code in the disable method :) and I will see. >> >> >> >> disablePackageCache >> "Disable the use of the package-cache repository." >> >> packageCacheRepository := MCCacheRepository default >> >> >> >> >> Stef >> >> On Jan 28, 2013, at 12:21 PM, Sven Van Caekenberghe wrote: >> >>> >>> On 28 Jan 2013, at 16:05, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>>> Hi guys >>>> >>>> I'm trying to work on Moose and I get 200 package to download during my experiments ~ 30 min at minimum >>>> Does anybody have an idea how to make sure metacello use the package cache? >>> >>> In my experience, Metacello/Monticello caching *is* used (provided you keep using the same package-cache directory). >>> If you open the Transcript while loading and/or inspect the Metacello loading result, you'll see when the cache is being used. >>> >>> IMHO, the downloading is not the worst part, it is more the loading/compiling - probably due to massive notifications and the reactions on that, it is hard to analyse and I am no expert at all. >>> >>>> I started to comment >>>> >>>> cacheGofer >>>> >>>> cacheGofer == nil >>>> ifTrue: [ >>>> "don't use a caching Gofer here, since we expect the contents to change during a fetch operation" >>>> cacheGofer := Gofer new. >>>>>>>> cacheGofer disablePackageCache. >>>> cacheGofer repository: self cacheRepository. ]. >>>> ^ cacheGofer >>>> >>>> But no success so far. >>>> >>>> Still looking around >>>> Stef >>>> >>>> >>> >>> >> >> >

Jan. 28, 2013

Re: [Pharo-project] How to force Metacello to use the package cache?

by Frank Shearar

I'm trying out a trick with extending Installer to always try load from package-cache. Perhaps Gofer can be similarly tweaked? (I did it by making Installer use an MCRepositoryGroup, which iterates over its contained repositories... and tries the package-cache first.) frank On 28 January 2013 18:02, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > for me it systematically loads everyghing so I'm trying to nuke it in gofer > kind of I put the enable code in the disable method :) and I will see. > > > > disablePackageCache > "Disable the use of the package-cache repository." > > packageCacheRepository := MCCacheRepository default > > > > > Stef > > On Jan 28, 2013, at 12:21 PM, Sven Van Caekenberghe wrote: > >> >> On 28 Jan 2013, at 16:05, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> Hi guys >>> >>> I'm trying to work on Moose and I get 200 package to download during my experiments ~ 30 min at minimum >>> Does anybody have an idea how to make sure metacello use the package cache? >> >> In my experience, Metacello/Monticello caching *is* used (provided you keep using the same package-cache directory). >> If you open the Transcript while loading and/or inspect the Metacello loading result, you'll see when the cache is being used. >> >> IMHO, the downloading is not the worst part, it is more the loading/compiling - probably due to massive notifications and the reactions on that, it is hard to analyse and I am no expert at all. >> >>> I started to comment >>> >>> cacheGofer >>> >>> cacheGofer == nil >>> ifTrue: [ >>> "don't use a caching Gofer here, since we expect the contents to change during a fetch operation" >>> cacheGofer := Gofer new. >>> >>>> cacheGofer disablePackageCache. >>> cacheGofer repository: self cacheRepository. ]. >>> ^ cacheGofer >>> >>> But no success so far. >>> >>> Still looking around >>> Stef >>> >>> >> >> > >

Jan. 28, 2013

Re: [Pharo-project] TxTextMorph based on new text model

by StÃ©phane Ducasse

This was experimental. Do not lose your time with it. Now you know that you should continue :) This was to prove that "kids" could define even texteditor with simple rules. Stef > Here is the paper: http://www.vpri.org/pdf/m2010002_lobjects.pdf > And you can download the image with the actual active essay from http://tinlizzie.org/lesserphic2/Text%20Field%20for%20LObject.zip > > I read paper and play with image. And I have not good impression about this work. > > First they present text with real objects for each letter. Each letter is actually big object with x, y, predecessor, successor and other attributes. How much memory such model required? > Do you think that presenting any letter with real object (not just character) is sufficient for modern computers? I think not. Of course such model significantly simplified all logic around text layout stuff. But I think it is too expensive. > > Another thing which I always not agree is introduction scripting languages inside smalltalk. In paper all layout logic (and editing too) programmed by "system of rules" in special scripting language (very similar to smalltalk). If you look deeply you will see that rules call other rules with same way methods call other methods in basic smalltalk code. So I don't see any value of rules idea expressed with special scripts. > In spite of my non positive opinion I like what they do inside rules. It is really simple and understandable code. Maybe I will try reuse something. > > Best regards, > Denis

Jan. 28, 2013

Re: [Pharo-project] How to force Metacello to use the package cache?

by StÃ©phane Ducasse

In fact I was wrong it indeed get the files from my packagecachesâ¦ but this is still so slow :). > for me it systematically loads everyghing so I'm trying to nuke it in gofer > kind of I put the enable code in the disable method :) and I will see. > > > > disablePackageCache > "Disable the use of the package-cache repository." > > packageCacheRepository := MCCacheRepository default This was a bad idea :) Since nothing loaded anymore. > > > > > Stef > > On Jan 28, 2013, at 12:21 PM, Sven Van Caekenberghe wrote: > >> >> On 28 Jan 2013, at 16:05, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> Hi guys >>> >>> I'm trying to work on Moose and I get 200 package to download during my experiments ~ 30 min at minimum >>> Does anybody have an idea how to make sure metacello use the package cache? >> >> In my experience, Metacello/Monticello caching *is* used (provided you keep using the same package-cache directory). >> If you open the Transcript while loading and/or inspect the Metacello loading result, you'll see when the cache is being used. >> >> IMHO, the downloading is not the worst part, it is more the loading/compiling - probably due to massive notifications and the reactions on that, it is hard to analyse and I am no expert at all. >> >>> I started to comment >>> >>> cacheGofer >>> >>> cacheGofer == nil >>> ifTrue: [ >>> "don't use a caching Gofer here, since we expect the contents to change during a fetch operation" >>> cacheGofer := Gofer new. >>> >>>> cacheGofer disablePackageCache. >>> cacheGofer repository: self cacheRepository. ]. >>> ^ cacheGofer >>> >>> But no success so far. >>> >>> Still looking around >>> Stef >>> >>> >> >> > >

Jan. 28, 2013

Re: [Pharo-project] TxTextMorph based on new text model

by Denis Kudriashov

Hello 2013/1/24 DeNigris Sean <sean(a)clipperadams.com> > > I don't. Do you have link? > > Here is the paper: http://www.vpri.org/pdf/m2010002_lobjects.pdf > And you can download the image with the actual active essay from > http://tinlizzie.org/lesserphic2/Text%20Field%20for%20LObject.zip > I read paper and play with image. And I have not good impression about this work. First they present text with real objects for each letter. Each letter is actually big object with x, y, predecessor, successor and other attributes. How much memory such model required? Do you think that presenting any letter with real object (not just character) is sufficient for modern computers? I think not. Of course such model significantly simplified all logic around text layout stuff. But I think it is too expensive. Another thing which I always not agree is introduction scripting languages inside smalltalk. In paper all layout logic (and editing too) programmed by "system of rules" in special scripting language (very similar to smalltalk). If you look deeply you will see that rules call other rules with same way methods call other methods in basic smalltalk code. So I don't see any value of rules idea expressed with special scripts. In spite of my non positive opinion I like what they do inside rules. It is really simple and understandable code. Maybe I will try reuse something. Best regards, Denis

Jan. 28, 2013

Re: [Pharo-project] How to force Metacello to use the package cache?

by StÃ©phane Ducasse

for me it systematically loads everyghing so I'm trying to nuke it in gofer kind of I put the enable code in the disable method :) and I will see. disablePackageCache "Disable the use of the package-cache repository." packageCacheRepository := MCCacheRepository default Stef On Jan 28, 2013, at 12:21 PM, Sven Van Caekenberghe wrote: > > On 28 Jan 2013, at 16:05, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi guys >> >> I'm trying to work on Moose and I get 200 package to download during my experiments ~ 30 min at minimum >> Does anybody have an idea how to make sure metacello use the package cache? > > In my experience, Metacello/Monticello caching *is* used (provided you keep using the same package-cache directory). > If you open the Transcript while loading and/or inspect the Metacello loading result, you'll see when the cache is being used. > > IMHO, the downloading is not the worst part, it is more the loading/compiling - probably due to massive notifications and the reactions on that, it is hard to analyse and I am no expert at all. > >> I started to comment >> >> cacheGofer >> >> cacheGofer == nil >> ifTrue: [ >> "don't use a caching Gofer here, since we expect the contents to change during a fetch operation" >> cacheGofer := Gofer new. >> >>>> cacheGofer disablePackageCache. >> cacheGofer repository: self cacheRepository. ]. >> ^ cacheGofer >> >> But no success so far. >> >> Still looking around >> Stef >> >> > >

Jan. 28, 2013

Re: [Pharo-project] Soup works in 2.0

by StÃ©phane Ducasse

Cool. May be we should migrate to SmalltalkHub. If you do it put me as a contributor :) stef On Jan 28, 2013, at 2:21 PM, Sean P. DeNigris wrote: > All tests pass. I updated the config and uploaded it to SqS and ss3... > > Cheers, > Sean > > > > -- > View this message in context: http://forum.world.st/Soup-works-in-2-0-tp4665907.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 28, 2013