November 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] About the Playground cache

by Ben Coman

Tudor Girba wrote: > > How about creating just one cache file, and only add used/evaluated > expressions > to the cache? > > > Why? What don't you want remembered? > > Cheers, > Doru > > ZnEasy get: 'https://www.google.com.au/webhp?search=sex+worker+jobs' ;) ??

Nov. 21, 2014

Re: [Pharo-dev] [Pharo4] down to 3 failing tests!

by Ben Coman

Marcus Denker wrote: > We are down to 3 failing tests! > > AJx64AssemblerTests>>#testStringOps64Mnemonics > ObsoleteTest>>#testFixObsoleteSharedPools > ReleaseTest>>#testObsoleteClasses > > https://pharo.fogbugz.com/f/search/?sSearchFor=outline%3A14445 > > Nice to hear. This will be good to achieve.

Nov. 21, 2014

Re: [Pharo-dev] About the Playground cache

by Tudor Girba

Hi, On Thu, Nov 20, 2014 at 11:56 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > 2014-11-20 22:14 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > >> Hi Nicolai, >> >> On Thu, Nov 20, 2014 at 10:04 PM, Nicolai Hess <nicolaihess(a)web.de> >> wrote: >> >>> >>> I thought the Playground cache holds all evaluated/used expressions. >>> >> >> > Hi Doru > > >> It used to only remember the expressions after you pressed Go. But, then >> we noticed that this is not enough as sometimes you just do it. So, rather >> than duplicating the logic for all possible actions, we asked ourselves: >> Why would I ever want to forget anything? After all, I am not deleting my >> mails anymore, and the package-cache already accumulated some 14k mcz files. >> >> Hence, the playground never forgets. >> > > Sure it does, you just have to delete all the current text, after that it > is gone you can not get it back. > > Maybe my practice is different, I don't open many different playgrounds > for every code I type in. > I am used to work with one or two workspaces and use only one of them as a > "playground" for the code. > I see. > >> >>> But it just caches the current text and if you remove the current text, >>> the cache >>> file is deleted. >>> >> >> Indeed. You get a file per Playground. This is why the title of the >> playground can be relevant. >> > >> >>> And it does not use just one file, but one for every opened playground >>> with text. >>> And if you close the playground, without deleting the current text, you >>> ' ll end >>> up with many (many many) cache files. (and it takes some time opening the >>> first playground after image start up). >>> >> >> Interesting. I have used this quite a lot and did not stumble across the >> opening delay problem. How many files do you have? >> > > 0, just deleted :) > But, does it still take long for you? > >> >>> Pressing the little "..." icon shows an unscrollable large list with all >>> the cache entries. >>> (even duplicate entries). >>> >> >> This will be replaced with a fancy search. >> >> How about creating just one cache file, and only add used/evaluated >>> expressions >>> to the cache? >>> >> >> Why? What don't you want remembered? >> > > all the same text from different cache files. > Ok. So, you mean if I have exactly the same text, we should not cache it. That makes sense. Would that be enough for you? If so, could you open an issue for this? > btw, the cache isn't truncated if you don't delete the whole text. That > means, if you select some > text and replace it with a shorter one, the play-cache files replaces only > the beginning of the file. > Therefore, some of the text isn't even valid code anymore. > Oops. This is a bug. Can you open an issue? Cheers, Doru > > >> >> Cheers, >> Doru >> >> >>> >>> >>> nicolai >>> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 20, 2014

Re: [Pharo-dev] About the Playground cache

by Nicolai Hess

2014-11-20 22:14 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi Nicolai, > > On Thu, Nov 20, 2014 at 10:04 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> >> I thought the Playground cache holds all evaluated/used expressions. >> > > Hi Doru > It used to only remember the expressions after you pressed Go. But, then > we noticed that this is not enough as sometimes you just do it. So, rather > than duplicating the logic for all possible actions, we asked ourselves: > Why would I ever want to forget anything? After all, I am not deleting my > mails anymore, and the package-cache already accumulated some 14k mcz files. > > Hence, the playground never forgets. > Sure it does, you just have to delete all the current text, after that it is gone you can not get it back. Maybe my practice is different, I don't open many different playgrounds for every code I type in. I am used to work with one or two workspaces and use only one of them as a "playground" for the code. > > >> But it just caches the current text and if you remove the current text, >> the cache >> file is deleted. >> > > Indeed. You get a file per Playground. This is why the title of the > playground can be relevant. > > >> And it does not use just one file, but one for every opened playground >> with text. >> And if you close the playground, without deleting the current text, you ' >> ll end >> up with many (many many) cache files. (and it takes some time opening the >> first playground after image start up). >> > > Interesting. I have used this quite a lot and did not stumble across the > opening delay problem. How many files do you have? > 0, just deleted :) > > >> Pressing the little "..." icon shows an unscrollable large list with all >> the cache entries. >> (even duplicate entries). >> > > This will be replaced with a fancy search. > > How about creating just one cache file, and only add used/evaluated >> expressions >> to the cache? >> > > Why? What don't you want remembered? > all the same text from different cache files. btw, the cache isn't truncated if you don't delete the whole text. That means, if you select some text and replace it with a shorter one, the play-cache files replaces only the beginning of the file. Therefore, some of the text isn't even valid code anymore. > > Cheers, > Doru > > >> >> >> nicolai >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Nov. 20, 2014

Re: [Pharo-dev] Link between PetitParser and Roassal and Glamour

by Tudor Girba

No problem :) Cheers, Doru On Thu, Nov 20, 2014 at 10:10 PM, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > I see. thanks :-) > On 20 Nov 2014, at 16:15, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > It's not strange. You only get this dependency if you load the gui of > petit parser. If you do not need the gui, you can load the core group. > > > > Doru > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > > >> On 20 Nov 2014, at 15:57, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > >> > >> Load PetitParser (dev version) => Roassal and Glamour loaded. > >> > >> Isnât it strange? I believe there should be less dependency. > >> > >> Noury > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 20, 2014

Re: [Pharo-dev] About the Playground cache

by Tudor Girba

Hi Nicolai, On Thu, Nov 20, 2014 at 10:04 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > I thought the Playground cache holds all evaluated/used expressions. > It used to only remember the expressions after you pressed Go. But, then we noticed that this is not enough as sometimes you just do it. So, rather than duplicating the logic for all possible actions, we asked ourselves: Why would I ever want to forget anything? After all, I am not deleting my mails anymore, and the package-cache already accumulated some 14k mcz files. Hence, the playground never forgets. > But it just caches the current text and if you remove the current text, > the cache > file is deleted. > Indeed. You get a file per Playground. This is why the title of the playground can be relevant. > And it does not use just one file, but one for every opened playground > with text. > And if you close the playground, without deleting the current text, you ' > ll end > up with many (many many) cache files. (and it takes some time opening the > first playground after image start up). > Interesting. I have used this quite a lot and did not stumble across the opening delay problem. How many files do you have? > Pressing the little "..." icon shows an unscrollable large list with all > the cache entries. > (even duplicate entries). > This will be replaced with a fancy search. How about creating just one cache file, and only add used/evaluated > expressions > to the cache? > Why? What don't you want remembered? Cheers, Doru > > > nicolai > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 20, 2014

Re: [Pharo-dev] Link between PetitParser and Roassal and Glamour

by Noury Bouraqadi

I see. thanks :-) On 20 Nov 2014, at 16:15, Tudor Girba <tudor(a)tudorgirba.com> wrote: > It's not strange. You only get this dependency if you load the gui of petit parser. If you do not need the gui, you can load the core group. > > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > >> On 20 Nov 2014, at 15:57, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: >> >> Load PetitParser (dev version) => Roassal and Glamour loaded. >> >> Isnât it strange? I believe there should be less dependency. >> >> Noury >

Nov. 20, 2014

About the Playground cache

by Nicolai Hess

I thought the Playground cache holds all evaluated/used expressions. But it just caches the current text and if you remove the current text, the cache file is deleted. And it does not use just one file, but one for every opened playground with text. And if you close the playground, without deleting the current text, you ' ll end up with many (many many) cache files. (and it takes some time opening the first playground after image start up). Pressing the little "..." icon shows an unscrollable large list with all the cache entries. (even duplicate entries). How about creating just one cache file, and only add used/evaluated expressions to the cache? nicolai

Nov. 20, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40378 Home: https://github.com/pharo-project/pharo-core

Nov. 20, 2014

[pharo-project/pharo-core] be3b36: 40378

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: be3b363a977670fdbe7db8858e22295e160283f8 https://github.com/pharo-project/pharo-core/commit/be3b363a977670fdbe7db885… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-20 (Thu, 20 Nov 2014) Changed paths: M Nautilus.package/ClassDefinitionAcceptor.class/instance/protocol/accept_notifying_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script378.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40378.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot.package/ObjectLayout.class/instance/extending/extendSmallInteger.st A Slot.package/SmallIntegerLayout.class/class/instance creation/extending_scope_host_.st Log Message: ----------- 40378 14508 add class ivars to SmallInteger: subclass responsibility #extending:scope:host: https://pharo.fogbugz.com/f/cases/14508 14507 DNU when accepting a class side definition for class instance vars https://pharo.fogbugz.com/f/cases/14507 http://files.pharo.org/image/40/40378.zip

Nov. 20, 2014