- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic

by StÃ©phane Ducasse

Thanks nicolas for checking that. Stef > So the latest ConfigurationOfXtreams found either in http://www.squeaksource.org/Xtreams or http://www.squeaksource.org/MetacelloRepository more or less load in Pharo3.0... > More or less means that it still tries to load FFI which fails to compile... > And I don't know why it loads, and i don't know why it fails... > FFI is required only by Xtreams-Xtra which is not (or should not be) in the 'default' group for #'pharo3.x' > It's not very important, because most of the Xtreams packages are already loaded when the failure occurs. > > When i check with this, it does not tell me that it will load FFI (maybe because I have a version loaded?): > ConfigurationOfXtreams project latestVersion fetch loadDirective. > > But when I load with this, it tries to compile FFI again: > ConfigurationOfXtreams project latestVersion load. > > > 2013/11/13 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > In original VW works, there is no FileDirectory nor FileReference nor FileSystem nor... > So Xtreams-Terminals was thought as a dialect specific package... > Of course, these terminals are still 95% compatible between Squeak4.x and Pharo3.x, so we can make a better packaging. > > Before deciding what is a good package delimitation, and what's not, I wanted to experiment a bit without compatibility constraints. > So I created a .Pharo3 branch in Terminals and TerminalsTests. > There's a little more than FileDirectory references: I also used the FileHandle class provided by FileSystem package, rather than Xtreams-Support XTIOFileHandle. > > Anyway, the Squeak/Pharo version is way behind the visualworks version, so yes, there is definitely some work needed. > Up to now, I diffed the versions in VW and manually ported to Squeak. > The good thing is that I can try to learn and understand the changes. > It is also mandatory to cop with the small differences (some VW method might be absent in Squeak/Pharo and require a Xtreams-Support counterpart, the classes need a XT prefix, ...). > The bad things are that > - there are many versions to integrate, and the history is not linear; > - I have only ten fingers, two eyes, and a single brain, the whole comes with very limited multitasking capabilities. > There must be a better way, like trying to automate the port of shared implementations, and review only the dialect-specific parts. > Or just put more brains, finger and eyes in the loop... > > > 2013/11/12 Frank Shearar <frank.shearar(a)gmail.com> > Yep, they do. build.squeak.org uses this repo. See also > https://code.google.com/p/xtreams/issues/detail?id=2 > > About time for us to pick up this work? > > frank > > On 12 November 2013 21:29, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > And the tests pass, except the file tests which are based on creating a > > stream thru (FileDirectory default / ...) > > > > > > 2013/11/12 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > >> > >> Hi Sven, > >> The last Squeak/Pharo locations I am aware of are: > >> - http://www.squeaksource.org/Xtreams for the Xtreams package > >> - http://www.squeaksource.org/MetacelloRepository for > >> ConfigurationOfXtreams (but I just copied the last Config to above repo) > >> A very important repository for resources of all kind from the original > >> authors is https://code.google.com/p/xtreams/ > >> > >> Those versions above do not load in Pharo3.0 due to several problems > >> - FileDirectory deprecation (there is an extension method that should be > >> removed in Pharo branch) > >> - Xtras package of Xtreams depends on FFI, and FFI does not load cleanly > >> in Pharo (at least the one found from the ConfigurationOfXtreams) because > >> ShortRunArray is not found... > >> > >> I will try and publish a Pharo branch, but before I do so, is anyone aware > >> of more recent work, or repository? > >> > >> > >> > >> > >> 2013/11/12 Sven Van Caekenberghe <sven(a)stfx.eu> > >>> > >>> Nicolas, > >>> > >>> Is it currently possible to load some latest version of Xtream into Pharo > >>> 3.0 ? > >>> > >>> If yes, from which repository using which Configuration ? > >>> > >>> I know that at ESUG 2012, Sean and Martin worked a bit on getting all > >>> different versions better in sync. > >>> > >>> It would be cool if we could at least load it, separate from the > >>> transition strategy (I agree with your proposal BTW), because many people do > >>> not know or have not seen what we are actually talking about. > >>> > >>> The clean, start from scratch approach of Xtreams also includes a much > >>> tighter and semantically better defined API. IMHO, a consequence is that > >>> #get / #next and #put: / #nextPut: are not just plain aliases (a modern use > >>> of exception handling is one big difference). The compatibility layer might > >>> be more of a challenge. > >>> > >>> The biggest gain is of course if clients switch to the newer API ;-) > >>> > >>> Sven > >>> > >>> On 12 Nov 2013, at 14:31, Nicolas Cellier > >>> <nicolas.cellier.aka.nice(a)gmail.com> wrote: > >>> > >>> > It's just a matter of selecting a strategy. I've proposed two: > >>> > A) create a wrapper class for legacy Stream compatibility selectors > >>> > B) create extensions for Legacy Stream compatibility selectors > >>> > My preference goes to A) > >>> > > >>> > The legacy support MUST be minimal (next nextPut: nextPutAll: peek > >>> > upTo: ...), otherwise we will import all the cruft in Xtream and would go > >>> > back to our starting point... > >>> > Once the minimal support written (a few hours should be enough), we > >>> > should gradually switch each every legacy Stream usage -> Xtream. > >>> > > >>> > An area which require more work is those Streams that have mixed > >>> > conventions (one portion is interpreted as text, another as binary). > >>> > In theory that's easy, we just have two streams and they both wrap on a > >>> > low level binary stream, but that means we have to be very cautious with > >>> > buffers and caches. > >>> > > >>> > Another area of work is usage of ugly selectors like name (we try to > >>> > access the file name from the Stream API, arghh). Those usages are bad and > >>> > require a rewrite. > >>> > > >>> > > >>> > 2013/11/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >>> > > >>> >> > >>> >> or of course, you start looking at porting XStreams to pharo ;), which > >>> >> on the long run will > >>> >> solve many more problems. The current situation is not that > >>> >> satisfactory > >>> > > >>> > having experience with it and thinking about a plan for the beginning > >>> > of 40 would be great. > >>> > I know that nicolas ported XTream to pharo/squeak. Now understanding > >>> > how integrate it would be nice. > >>> > Stef > >>> > > >>> > > >>> > >>> > >> > > > > >

Nov. 13, 2013

Re: [Pharo-dev] smalltalkhub.com down

by Mariano Martinez Peck

Cannot we simply run monit in the server? It is insane to wait someone to restart it manually.... On Tue, Nov 12, 2013 at 10:42 PM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > http://www.downforeveryoneorjustme.com/smalltalkhub.com > -- Mariano http://marianopeck.wordpress.com

Nov. 13, 2013

Re: [Pharo-dev] Monticello SmalltalkHub no longer asks for credentials

by StÃ©phane Ducasse

me too oscar already published some of his packages :) Stef On Nov 12, 2013, at 10:53 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > StÃ©phane Ducasse wrote >> sean this is strange because this morning I used my credentials > > I take back what I said. I think this is a different issue, since it seems > to still request in an older 3.0 version, and the change I was talking about > I think was in 2.0 > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Monticello-SmalltalkHub-no-longer-asks-for-credential… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Nov. 13, 2013

Re: [Pharo-dev] Spec new release :)

by StÃ©phane Ducasse

Ben it would be good to do it pier format so that we get html and pdf and also to avoid to have documentation spread all over. Stef On Nov 12, 2013, at 11:42 PM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > Yes it is planned :) > > The idea is to have it ready for the release of Pharo 3.0 (at last). > There is a git repo I just opened[1] where the doc will be :) > > Every body is free to fork it and to pull-request me :) > > Ben > [1]https://github.com/BenjaminVanRyseghem/Spec_Documentation > > On 12 Nov 2013, at 23:09, kilon alios <kilon.alios(a)gmail.com> wrote: > >> Is there any new documentation planned ? >> >> >> On Tue, Nov 12, 2013 at 11:42 PM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >> Confirmed and fixed :P >> https://pharo.fogbugz.com/default.asp?12153 >> >> >> Ben >> >> On 12 Nov 2013, at 17:08, Martin Dias <tinchodias(a)gmail.com> wrote: >> >>> (Checked in Pharo 30567) >>> >>> On Tue, Nov 12, 2013 at 5:08 PM, Martin Dias <tinchodias(a)gmail.com> wrote: >>>> Thanks Ben. It's neat to have Spec models for tree columns. It was >>>> strange to instantiate MorphTreeColumnMorph directly from my Spec >>>> model. >>>> >>>> I found an issue in TreeModel: Only one level of children is shown. >>>> Reproduce with: >>>> >>>> TreeModel new >>>> roots: (1 to: 5); >>>> childrenBlock: [ :item | 1+item to: 5+item ]; >>>> openWithSpec >>>> >>>> Should I report? >>>> >>>> MartÃn >>>> >>>> On Tue, Nov 12, 2013 at 2:59 PM, Benjamin >>>> <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >>>>> Itâs this one: https://pharo.fogbugz.com/default.asp?12135 >>>>> >>>>> Ben >>>>> >>>>> On 12 Nov 2013, at 14:49, Martin Dias <tinchodias(a)gmail.com> wrote: >>>>> >>>>> I forgot to specify: in latest Pharo (30565) >>>>> >>>>> On Tue, Nov 12, 2013 at 2:48 PM, Martin Dias <tinchodias(a)gmail.com> wrote: >>>>> >>>>> I think there is some issue with TreeColumnModel. For example: >>>>> >>>>> TreeModel exampleWithCustomColumnsAndNodes >>>>> >>>>> Raises "ByteSymbol(Object)>>doesNotUnderstand: #adapt:" >>>>> >>>>> Should I report in fogbugz? >>>>> >>>>> thanks, >>>>> MartÃn >>>>> >>>>> On Tue, Nov 12, 2013 at 2:21 PM, StÃ©phane Ducasse >>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>> >>>>> Yes this is what I did for the change sorter. I do not like this DSL like >>>>> way of passing block over block over block >>>>> over blocks. >>>>> >>>>> I love blocks but methods are named blocks and I prefer them. >>>>> >>>>> Stef >>>>> >>>>> biut that method can be written: >>>>> >>>>> aMenu addGroup: (MenuGroupModel new >>>>> addItem: (MenuItemModel new >>>>> name: 'Browse Full'; >>>>> action: [ self browseSelectedObject ]; >>>>> shortcut: $b command mac | $b alt win | $b alt unix); >>>>> addItem: (MenuItem new >>>>> name: 'Browse Class'; >>>>> action: [ self browseSelectedObjectClass ])). >>>>> >>>>> and you do not have to declare variables for that (and is a lot better than >>>>> using a block, IMO). >>>>> >>>>> >>>>> >>>>> On Nov 12, 2013, at 9:36 AM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> >>>>> wrote: >>>>> >>>>> One can just use an object too. >>>>> >>>>> Itâs just that otherwise, it pollutes a bit the method with tons of inst >>>>> vars >>>>> (and then you forget to use them :P) >>>>> >>>>> Ben >>>>> >>>>> On 12 Nov 2013, at 13:05, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>> >>>>> >>>>> On Nov 12, 2013, at 4:22 AM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> >>>>> wrote: >>>>> >>>>> It is not necessary better, but it saves you from having hundreds of temp >>>>> vars :) >>>>> >>>>> Ben >>>>> >>>>> On 12 Nov 2013, at 01:49, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>>> wrote: >>>>> >>>>> >>>>> Example: >>>>> aMenu addGroup: [ :aGroup | >>>>> aGroup addItem: [ :anItem | >>>>> anItem name: 'Browse Full'; >>>>> action: [ self browseSelectedObject ]; >>>>> shortcut: $b command mac | $b alt win | $b alt unix ]. >>>>> aGroup addItem: [ :anItem | >>>>> anItem name: 'Browse Class'; >>>>> action: [ self browseSelectedObjectClass ] ] ]. >>>>> >>>>> >>>>> I do not see the value of passing block to add element to groups >>>>> why not the normal way i.e. passing an object. I do not get why executing >>>>> a block with an object is better? >>>>> >>>>> >>>>> he, I thought the same :) >>>>> >>>>> >>>>> Stef >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>> >> >> >

Nov. 13, 2013

smalltalkhub.com down

by Nicolas Cellier

http://www.downforeveryoneorjustme.com/smalltalkhub.com

Nov. 13, 2013

Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic

by Nicolas Cellier

So the latest ConfigurationOfXtreams found either in http://www.squeaksource.org/Xtreams or http://www.squeaksource.org/MetacelloRepository more or less load in Pharo3.0... More or less means that it still tries to load FFI which fails to compile... And I don't know why it loads, and i don't know why it fails... FFI is required only by Xtreams-Xtra which is not (or should not be) in the 'default' group for #'pharo3.x' It's not very important, because most of the Xtreams packages are already loaded when the failure occurs. When i check with this, it does not tell me that it will load FFI (maybe because I have a version loaded?): ConfigurationOfXtreams project latestVersion fetch loadDirective. But when I load with this, it tries to compile FFI again: ConfigurationOfXtreams project latestVersion load. 2013/11/13 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > In original VW works, there is no FileDirectory nor FileReference nor > FileSystem nor... > So Xtreams-Terminals was thought as a dialect specific package... > Of course, these terminals are still 95% compatible between Squeak4.x and > Pharo3.x, so we can make a better packaging. > > Before deciding what is a good package delimitation, and what's not, I > wanted to experiment a bit without compatibility constraints. > So I created a .Pharo3 branch in Terminals and TerminalsTests. > There's a little more than FileDirectory references: I also used the > FileHandle class provided by FileSystem package, rather than > Xtreams-Support XTIOFileHandle. > > Anyway, the Squeak/Pharo version is way behind the visualworks version, so > yes, there is definitely some work needed. > Up to now, I diffed the versions in VW and manually ported to Squeak. > The good thing is that I can try to learn and understand the changes. > It is also mandatory to cop with the small differences (some VW method > might be absent in Squeak/Pharo and require a Xtreams-Support counterpart, > the classes need a XT prefix, ...). > The bad things are that > - there are many versions to integrate, and the history is not linear; > - I have only ten fingers, two eyes, and a single brain, the whole comes > with very limited multitasking capabilities. > There must be a better way, like trying to automate the port of shared > implementations, and review only the dialect-specific parts. > Or just put more brains, finger and eyes in the loop... > > > 2013/11/12 Frank Shearar <frank.shearar(a)gmail.com> > >> Yep, they do. build.squeak.org uses this repo. See also >> https://code.google.com/p/xtreams/issues/detail?id=2 >> >> About time for us to pick up this work? >> >> frank >> >> On 12 November 2013 21:29, Nicolas Cellier >> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> > And the tests pass, except the file tests which are based on creating a >> > stream thru (FileDirectory default / ...) >> > >> > >> > 2013/11/12 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> >> >> >> >> Hi Sven, >> >> The last Squeak/Pharo locations I am aware of are: >> >> - http://www.squeaksource.org/Xtreams for the Xtreams package >> >> - http://www.squeaksource.org/MetacelloRepository for >> >> ConfigurationOfXtreams (but I just copied the last Config to above >> repo) >> >> A very important repository for resources of all kind from the original >> >> authors is https://code.google.com/p/xtreams/ >> >> >> >> Those versions above do not load in Pharo3.0 due to several problems >> >> - FileDirectory deprecation (there is an extension method that should >> be >> >> removed in Pharo branch) >> >> - Xtras package of Xtreams depends on FFI, and FFI does not load >> cleanly >> >> in Pharo (at least the one found from the ConfigurationOfXtreams) >> because >> >> ShortRunArray is not found... >> >> >> >> I will try and publish a Pharo branch, but before I do so, is anyone >> aware >> >> of more recent work, or repository? >> >> >> >> >> >> >> >> >> >> 2013/11/12 Sven Van Caekenberghe <sven(a)stfx.eu> >> >>> >> >>> Nicolas, >> >>> >> >>> Is it currently possible to load some latest version of Xtream into >> Pharo >> >>> 3.0 ? >> >>> >> >>> If yes, from which repository using which Configuration ? >> >>> >> >>> I know that at ESUG 2012, Sean and Martin worked a bit on getting all >> >>> different versions better in sync. >> >>> >> >>> It would be cool if we could at least load it, separate from the >> >>> transition strategy (I agree with your proposal BTW), because many >> people do >> >>> not know or have not seen what we are actually talking about. >> >>> >> >>> The clean, start from scratch approach of Xtreams also includes a much >> >>> tighter and semantically better defined API. IMHO, a consequence is >> that >> >>> #get / #next and #put: / #nextPut: are not just plain aliases (a >> modern use >> >>> of exception handling is one big difference). The compatibility layer >> might >> >>> be more of a challenge. >> >>> >> >>> The biggest gain is of course if clients switch to the newer API ;-) >> >>> >> >>> Sven >> >>> >> >>> On 12 Nov 2013, at 14:31, Nicolas Cellier >> >>> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >>> >> >>> > It's just a matter of selecting a strategy. I've proposed two: >> >>> > A) create a wrapper class for legacy Stream compatibility selectors >> >>> > B) create extensions for Legacy Stream compatibility selectors >> >>> > My preference goes to A) >> >>> > >> >>> > The legacy support MUST be minimal (next nextPut: nextPutAll: peek >> >>> > upTo: ...), otherwise we will import all the cruft in Xtream and >> would go >> >>> > back to our starting point... >> >>> > Once the minimal support written (a few hours should be enough), we >> >>> > should gradually switch each every legacy Stream usage -> Xtream. >> >>> > >> >>> > An area which require more work is those Streams that have mixed >> >>> > conventions (one portion is interpreted as text, another as binary). >> >>> > In theory that's easy, we just have two streams and they both wrap >> on a >> >>> > low level binary stream, but that means we have to be very cautious >> with >> >>> > buffers and caches. >> >>> > >> >>> > Another area of work is usage of ugly selectors like name (we try to >> >>> > access the file name from the Stream API, arghh). Those usages are >> bad and >> >>> > require a rewrite. >> >>> > >> >>> > >> >>> > 2013/11/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> >>> > >> >>> >> >> >>> >> or of course, you start looking at porting XStreams to pharo ;), >> which >> >>> >> on the long run will >> >>> >> solve many more problems. The current situation is not that >> >>> >> satisfactory >> >>> > >> >>> > having experience with it and thinking about a plan for the >> beginning >> >>> > of 40 would be great. >> >>> > I know that nicolas ported XTream to pharo/squeak. Now understanding >> >>> > how integrate it would be nice. >> >>> > Stef >> >>> > >> >>> > >> >>> >> >>> >> >> >> > >> >> >

Nov. 13, 2013

Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic

by Nicolas Cellier

In original VW works, there is no FileDirectory nor FileReference nor FileSystem nor... So Xtreams-Terminals was thought as a dialect specific package... Of course, these terminals are still 95% compatible between Squeak4.x and Pharo3.x, so we can make a better packaging. Before deciding what is a good package delimitation, and what's not, I wanted to experiment a bit without compatibility constraints. So I created a .Pharo3 branch in Terminals and TerminalsTests. There's a little more than FileDirectory references: I also used the FileHandle class provided by FileSystem package, rather than Xtreams-Support XTIOFileHandle. Anyway, the Squeak/Pharo version is way behind the visualworks version, so yes, there is definitely some work needed. Up to now, I diffed the versions in VW and manually ported to Squeak. The good thing is that I can try to learn and understand the changes. It is also mandatory to cop with the small differences (some VW method might be absent in Squeak/Pharo and require a Xtreams-Support counterpart, the classes need a XT prefix, ...). The bad things are that - there are many versions to integrate, and the history is not linear; - I have only ten fingers, two eyes, and a single brain, the whole comes with very limited multitasking capabilities. There must be a better way, like trying to automate the port of shared implementations, and review only the dialect-specific parts. Or just put more brains, finger and eyes in the loop... 2013/11/12 Frank Shearar <frank.shearar(a)gmail.com> > Yep, they do. build.squeak.org uses this repo. See also > https://code.google.com/p/xtreams/issues/detail?id=2 > > About time for us to pick up this work? > > frank > > On 12 November 2013 21:29, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > And the tests pass, except the file tests which are based on creating a > > stream thru (FileDirectory default / ...) > > > > > > 2013/11/12 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > >> > >> Hi Sven, > >> The last Squeak/Pharo locations I am aware of are: > >> - http://www.squeaksource.org/Xtreams for the Xtreams package > >> - http://www.squeaksource.org/MetacelloRepository for > >> ConfigurationOfXtreams (but I just copied the last Config to above repo) > >> A very important repository for resources of all kind from the original > >> authors is https://code.google.com/p/xtreams/ > >> > >> Those versions above do not load in Pharo3.0 due to several problems > >> - FileDirectory deprecation (there is an extension method that should be > >> removed in Pharo branch) > >> - Xtras package of Xtreams depends on FFI, and FFI does not load cleanly > >> in Pharo (at least the one found from the ConfigurationOfXtreams) > because > >> ShortRunArray is not found... > >> > >> I will try and publish a Pharo branch, but before I do so, is anyone > aware > >> of more recent work, or repository? > >> > >> > >> > >> > >> 2013/11/12 Sven Van Caekenberghe <sven(a)stfx.eu> > >>> > >>> Nicolas, > >>> > >>> Is it currently possible to load some latest version of Xtream into > Pharo > >>> 3.0 ? > >>> > >>> If yes, from which repository using which Configuration ? > >>> > >>> I know that at ESUG 2012, Sean and Martin worked a bit on getting all > >>> different versions better in sync. > >>> > >>> It would be cool if we could at least load it, separate from the > >>> transition strategy (I agree with your proposal BTW), because many > people do > >>> not know or have not seen what we are actually talking about. > >>> > >>> The clean, start from scratch approach of Xtreams also includes a much > >>> tighter and semantically better defined API. IMHO, a consequence is > that > >>> #get / #next and #put: / #nextPut: are not just plain aliases (a > modern use > >>> of exception handling is one big difference). The compatibility layer > might > >>> be more of a challenge. > >>> > >>> The biggest gain is of course if clients switch to the newer API ;-) > >>> > >>> Sven > >>> > >>> On 12 Nov 2013, at 14:31, Nicolas Cellier > >>> <nicolas.cellier.aka.nice(a)gmail.com> wrote: > >>> > >>> > It's just a matter of selecting a strategy. I've proposed two: > >>> > A) create a wrapper class for legacy Stream compatibility selectors > >>> > B) create extensions for Legacy Stream compatibility selectors > >>> > My preference goes to A) > >>> > > >>> > The legacy support MUST be minimal (next nextPut: nextPutAll: peek > >>> > upTo: ...), otherwise we will import all the cruft in Xtream and > would go > >>> > back to our starting point... > >>> > Once the minimal support written (a few hours should be enough), we > >>> > should gradually switch each every legacy Stream usage -> Xtream. > >>> > > >>> > An area which require more work is those Streams that have mixed > >>> > conventions (one portion is interpreted as text, another as binary). > >>> > In theory that's easy, we just have two streams and they both wrap > on a > >>> > low level binary stream, but that means we have to be very cautious > with > >>> > buffers and caches. > >>> > > >>> > Another area of work is usage of ugly selectors like name (we try to > >>> > access the file name from the Stream API, arghh). Those usages are > bad and > >>> > require a rewrite. > >>> > > >>> > > >>> > 2013/11/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >>> > > >>> >> > >>> >> or of course, you start looking at porting XStreams to pharo ;), > which > >>> >> on the long run will > >>> >> solve many more problems. The current situation is not that > >>> >> satisfactory > >>> > > >>> > having experience with it and thinking about a plan for the beginning > >>> > of 40 would be great. > >>> > I know that nicolas ported XTream to pharo/squeak. Now understanding > >>> > how integrate it would be nice. > >>> > Stef > >>> > > >>> > > >>> > >>> > >> > > > >

Nov. 12, 2013

Re: [Pharo-dev] PharoV20.source

by ClÃ©ment Bera

Hello, Currently the idea is to put the source file as a compressed AST in the image. The status is: - standard AST is 300Mb for the whole image, which is too much - standard AST with nodes shared between RBMethodNodes (made by Camille) is 16Mb, so already half the size of the current sources - same as last one but with additional bit compression: not done yet ! It should be around 4Mb (but that's a lucky guess), growing the size of the image from 16Mb to 20Mb, which is okay. The source file should not be in the VM. One image can use only 1 source file, but 1 VM can run several images using different source files. Therefore you would need to add multiple source files in the VM, which ends up nowhere. 2013/11/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > you want as less as possible thing in the vm. > > Stef > > On Nov 12, 2013, at 8:46 PM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > > Hi! > > > > Why not to include this file in the VM? > > It often happens to me that this place is wrongly placed. When this > happens, Pharo just shows a white screen, without letting what is the error. > > > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > >

Nov. 12, 2013

Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic

by Frank Shearar

Yep, they do. build.squeak.org uses this repo. See also https://code.google.com/p/xtreams/issues/detail?id=2 About time for us to pick up this work? frank On 12 November 2013 21:29, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > And the tests pass, except the file tests which are based on creating a > stream thru (FileDirectory default / ...) > > > 2013/11/12 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> >> >> Hi Sven, >> The last Squeak/Pharo locations I am aware of are: >> - http://www.squeaksource.org/Xtreams for the Xtreams package >> - http://www.squeaksource.org/MetacelloRepository for >> ConfigurationOfXtreams (but I just copied the last Config to above repo) >> A very important repository for resources of all kind from the original >> authors is https://code.google.com/p/xtreams/ >> >> Those versions above do not load in Pharo3.0 due to several problems >> - FileDirectory deprecation (there is an extension method that should be >> removed in Pharo branch) >> - Xtras package of Xtreams depends on FFI, and FFI does not load cleanly >> in Pharo (at least the one found from the ConfigurationOfXtreams) because >> ShortRunArray is not found... >> >> I will try and publish a Pharo branch, but before I do so, is anyone aware >> of more recent work, or repository? >> >> >> >> >> 2013/11/12 Sven Van Caekenberghe <sven(a)stfx.eu> >>> >>> Nicolas, >>> >>> Is it currently possible to load some latest version of Xtream into Pharo >>> 3.0 ? >>> >>> If yes, from which repository using which Configuration ? >>> >>> I know that at ESUG 2012, Sean and Martin worked a bit on getting all >>> different versions better in sync. >>> >>> It would be cool if we could at least load it, separate from the >>> transition strategy (I agree with your proposal BTW), because many people do >>> not know or have not seen what we are actually talking about. >>> >>> The clean, start from scratch approach of Xtreams also includes a much >>> tighter and semantically better defined API. IMHO, a consequence is that >>> #get / #next and #put: / #nextPut: are not just plain aliases (a modern use >>> of exception handling is one big difference). The compatibility layer might >>> be more of a challenge. >>> >>> The biggest gain is of course if clients switch to the newer API ;-) >>> >>> Sven >>> >>> On 12 Nov 2013, at 14:31, Nicolas Cellier >>> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> >>> > It's just a matter of selecting a strategy. I've proposed two: >>> > A) create a wrapper class for legacy Stream compatibility selectors >>> > B) create extensions for Legacy Stream compatibility selectors >>> > My preference goes to A) >>> > >>> > The legacy support MUST be minimal (next nextPut: nextPutAll: peek >>> > upTo: ...), otherwise we will import all the cruft in Xtream and would go >>> > back to our starting point... >>> > Once the minimal support written (a few hours should be enough), we >>> > should gradually switch each every legacy Stream usage -> Xtream. >>> > >>> > An area which require more work is those Streams that have mixed >>> > conventions (one portion is interpreted as text, another as binary). >>> > In theory that's easy, we just have two streams and they both wrap on a >>> > low level binary stream, but that means we have to be very cautious with >>> > buffers and caches. >>> > >>> > Another area of work is usage of ugly selectors like name (we try to >>> > access the file name from the Stream API, arghh). Those usages are bad and >>> > require a rewrite. >>> > >>> > >>> > 2013/11/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> > >>> >> >>> >> or of course, you start looking at porting XStreams to pharo ;), which >>> >> on the long run will >>> >> solve many more problems. The current situation is not that >>> >> satisfactory >>> > >>> > having experience with it and thinking about a plan for the beginning >>> > of 40 would be great. >>> > I know that nicolas ported XTream to pharo/squeak. Now understanding >>> > how integrate it would be nice. >>> > Stef >>> > >>> > >>> >>> >> >

Nov. 12, 2013

Re: [Pharo-dev] Spec new release :)

by Benjamin

Yes it is planned :) The idea is to have it ready for the release of Pharo 3.0 (at last). There is a git repo I just opened[1] where the doc will be :) Every body is free to fork it and to pull-request me :) Ben [1]https://github.com/BenjaminVanRyseghem/Spec_Documentation On 12 Nov 2013, at 23:09, kilon alios <kilon.alios(a)gmail.com> wrote: > Is there any new documentation planned ? > > > On Tue, Nov 12, 2013 at 11:42 PM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > Confirmed and fixed :P > https://pharo.fogbugz.com/default.asp?12153 > > > Ben > > On 12 Nov 2013, at 17:08, Martin Dias <tinchodias(a)gmail.com> wrote: > >> (Checked in Pharo 30567) >> >> On Tue, Nov 12, 2013 at 5:08 PM, Martin Dias <tinchodias(a)gmail.com> wrote: >>> Thanks Ben. It's neat to have Spec models for tree columns. It was >>> strange to instantiate MorphTreeColumnMorph directly from my Spec >>> model. >>> >>> I found an issue in TreeModel: Only one level of children is shown. >>> Reproduce with: >>> >>> TreeModel new >>> roots: (1 to: 5); >>> childrenBlock: [ :item | 1+item to: 5+item ]; >>> openWithSpec >>> >>> Should I report? >>> >>> MartÃn >>> >>> On Tue, Nov 12, 2013 at 2:59 PM, Benjamin >>> <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >>>> Itâs this one: https://pharo.fogbugz.com/default.asp?12135 >>>> >>>> Ben >>>> >>>> On 12 Nov 2013, at 14:49, Martin Dias <tinchodias(a)gmail.com> wrote: >>>> >>>> I forgot to specify: in latest Pharo (30565) >>>> >>>> On Tue, Nov 12, 2013 at 2:48 PM, Martin Dias <tinchodias(a)gmail.com> wrote: >>>> >>>> I think there is some issue with TreeColumnModel. For example: >>>> >>>> TreeModel exampleWithCustomColumnsAndNodes >>>> >>>> Raises "ByteSymbol(Object)>>doesNotUnderstand: #adapt:" >>>> >>>> Should I report in fogbugz? >>>> >>>> thanks, >>>> MartÃn >>>> >>>> On Tue, Nov 12, 2013 at 2:21 PM, StÃ©phane Ducasse >>>> <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> Yes this is what I did for the change sorter. I do not like this DSL like >>>> way of passing block over block over block >>>> over blocks. >>>> >>>> I love blocks but methods are named blocks and I prefer them. >>>> >>>> Stef >>>> >>>> biut that method can be written: >>>> >>>> aMenu addGroup: (MenuGroupModel new >>>> addItem: (MenuItemModel new >>>> name: 'Browse Full'; >>>> action: [ self browseSelectedObject ]; >>>> shortcut: $b command mac | $b alt win | $b alt unix); >>>> addItem: (MenuItem new >>>> name: 'Browse Class'; >>>> action: [ self browseSelectedObjectClass ])). >>>> >>>> and you do not have to declare variables for that (and is a lot better than >>>> using a block, IMO). >>>> >>>> >>>> >>>> On Nov 12, 2013, at 9:36 AM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> >>>> wrote: >>>> >>>> One can just use an object too. >>>> >>>> Itâs just that otherwise, it pollutes a bit the method with tons of inst >>>> vars >>>> (and then you forget to use them :P) >>>> >>>> Ben >>>> >>>> On 12 Nov 2013, at 13:05, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> >>>> On Nov 12, 2013, at 4:22 AM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> >>>> wrote: >>>> >>>> It is not necessary better, but it saves you from having hundreds of temp >>>> vars :) >>>> >>>> Ben >>>> >>>> On 12 Nov 2013, at 01:49, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>> wrote: >>>> >>>> >>>> Example: >>>> aMenu addGroup: [ :aGroup | >>>> aGroup addItem: [ :anItem | >>>> anItem name: 'Browse Full'; >>>> action: [ self browseSelectedObject ]; >>>> shortcut: $b command mac | $b alt win | $b alt unix ]. >>>> aGroup addItem: [ :anItem | >>>> anItem name: 'Browse Class'; >>>> action: [ self browseSelectedObjectClass ] ] ]. >>>> >>>> >>>> I do not see the value of passing block to add element to groups >>>> why not the normal way i.e. passing an object. I do not get why executing >>>> a block with an object is better? >>>> >>>> >>>> he, I thought the same :) >>>> >>>> >>>> Stef >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >> > >

Nov. 12, 2013