December 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Tell me about your workflow

by Goubier Thierry

Le 11/12/2013 15:44, Sebastian Sastre a Ã©crit : > Hi Thierry > > On Dec 11, 2013, at 12:43 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >>> >>> I have packages (in the order of hundreds of classes) and save delays >>> and package click delays are starting to demand patience in a way that >>> doesn't feel like the right path >> >> Which operations ? I didn't remember noticing much with 179 classes on a laptop without a SSD. > > choose one. Just for clicking the package that will should you UUID, version and author I need to wait ~16 seconds. Sounds like a lot of overhead for reading a small .json file. This operation is fast with gitfiletree because I cache the commit history and avoid reading the version file everytime: the version reader is very slow, especially with large version files. You're using FileTree and not gitfiletree ? gitfiletree may solve the reading problem, if it fits with your workflow (and it reads cleanly pre-existing git/filetree repository without changing them). > But the write is the most worrisome This is something I haven't found a need to optimise yet, so maybe you're on something important. >>> All that is with a SSD disk, otherwise save delays would be /way/ beyond >>> unacceptable >> >> I'd like to know more, and understand the reason, for sure. As far as I know, filetree will rewrite the whole package to disk everytime... and maybe optimising that could be the solution. >> > > Well, that explains a lot. Writing all every time is the lazy thing that's okay for a prototype and temporary code in a proof of concept but that massive redundant reads certainly doesn't sounds like pro software. Specially for SSD's which has a limited quantity of writes Well, it ensures correctness and simplify the code ;) When it is confirmed to be a bottleneck, then we can act and change it. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Dec. 11, 2013

[ANN] traversal-enabled objects with DeepTraverser

by Tudor Girba

Hi, I put together a little implementation for traversals. It is inspired by an original implementation from Mariano. Using DeepTraverser, you can traverse arbitrary graphs by describing the traversal and by specifying the actions you want to perform on the nodes and relations. The code is available in the Moose image as part of the MooseAlgos subproject, but can also be loaded separately in a Pharo image via: Gofer new url: 'http://www.smalltalkhub.com/mc/Moose/DeepTraverser/main'; package: âConfigurationOfDeepTraverserâ; load. (Smalltalk globals at: #ConfigurationOfDeepTraverser) loadDevelopment. Just to give you an idea, here are some representative examples: Number deep: #subclasses do: [:each | Transcript show: each; cr]. Number deepCollect: #subclasses. Number deep: #subclasses collect: #name. Number deep: #subclasses do: [:each | Transcript show: each; cr] relationDo: [ :from :to | Transcript show: from; show: ' <-- '; show: to; cr ]. More details about the usages and a little description of the implementation can be found here: http://www.humane-assessment.com/blog/traversal-enabled-pharo-objects/ Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Dec. 11, 2013

Re: [Pharo-dev] Tell me about your workflow

by Esteban Lorenzano

I know there is a version of filetree without metadata (more compelling for projects that will never use other formats). Dale told me that there was a preview somewhere, but I didn't tested yet (lack of time) and now I cannot find the mail... Dale, can you re-send the link? cheers, Esteban On Wed, Dec 11, 2013 at 4:08 PM, Sebastian Sastre < sebastian(a)flowingconcept.com> wrote: > I should breath before I type, but you probably already got that I meant *redundant > writes* (not reads)... > > Anyway.. I was talking with Esteban and he mentions some kind of > compatibility metadata. > > If I'm going to give a leap of faith to filetree repos to save code why > should I care about mcz compatibility? Paying a toll for no reason is evil. > > Maybe we could make that optional so those who don't extract value from > that feature can opt-out? > > sebastian <https://about.me/sebastianconcept> > > o/ > > > > > > On Dec 11, 2013, at 12:44 PM, Sebastian Sastre < > sebastian(a)flowingconcept.com> wrote: > > Hi Thierry > > On Dec 11, 2013, at 12:43 PM, Goubier Thierry <thierry.goubier(a)cea.fr> > wrote: > > > I have packages (in the order of hundreds of classes) and save delays > and package click delays are starting to demand patience in a way that > doesn't feel like the right path > > > Which operations ? I didn't remember noticing much with 179 classes on a > laptop without a SSD. > > > choose one. Just for clicking the package that will should you UUID, > version and author I need to wait ~16 seconds. Sounds like a lot of > overhead for reading a small .json file. > > But the write is the most worrisome > > > All that is with a SSD disk, otherwise save delays would be /way/ beyond > unacceptable > > > I'd like to know more, and understand the reason, for sure. As far as I > know, filetree will rewrite the whole package to disk everytime... and > maybe optimising that could be the solution. > > > Well, that explains a lot. Writing all every time is the lazy thing that's > okay for a prototype and temporary code in a proof of concept but that > massive redundant reads certainly doesn't sounds like pro software. > Specially for SSD's which has a limited quantity of writes > > > Thierry > > sebastian <https://about.me/sebastianconcept> > > o/ > > > > > > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > > > > >

Dec. 11, 2013

Re: [Pharo-dev] Tell me about your workflow

by Sebastian Sastre

I should breath before I type, but you probably already got that I meant redundant writes (not reads)... Anyway.. I was talking with Esteban and he mentions some kind of compatibility metadata. If I'm going to give a leap of faith to filetree repos to save code why should I care about mcz compatibility? Paying a toll for no reason is evil. Maybe we could make that optional so those who don't extract value from that feature can opt-out? sebastian o/ On Dec 11, 2013, at 12:44 PM, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > Hi Thierry > > On Dec 11, 2013, at 12:43 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >>> >>> I have packages (in the order of hundreds of classes) and save delays >>> and package click delays are starting to demand patience in a way that >>> doesn't feel like the right path >> >> Which operations ? I didn't remember noticing much with 179 classes on a laptop without a SSD. > > choose one. Just for clicking the package that will should you UUID, version and author I need to wait ~16 seconds. Sounds like a lot of overhead for reading a small .json file. > > But the write is the most worrisome > > >>> All that is with a SSD disk, otherwise save delays would be /way/ beyond >>> unacceptable >> >> I'd like to know more, and understand the reason, for sure. As far as I know, filetree will rewrite the whole package to disk everytime... and maybe optimising that could be the solution. >> > > Well, that explains a lot. Writing all every time is the lazy thing that's okay for a prototype and temporary code in a proof of concept but that massive redundant reads certainly doesn't sounds like pro software. Specially for SSD's which has a limited quantity of writes > > >> Thierry >> >>> sebastian <https://about.me/sebastianconcept> >>> >>> o/ >>> >>> >>> >>> >>> >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> > >

Dec. 11, 2013

Re: [Pharo-dev] Tell me about your workflow

by Sebastian Sastre

Hi Thierry On Dec 11, 2013, at 12:43 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> >> I have packages (in the order of hundreds of classes) and save delays >> and package click delays are starting to demand patience in a way that >> doesn't feel like the right path > > Which operations ? I didn't remember noticing much with 179 classes on a laptop without a SSD. choose one. Just for clicking the package that will should you UUID, version and author I need to wait ~16 seconds. Sounds like a lot of overhead for reading a small .json file. But the write is the most worrisome >> All that is with a SSD disk, otherwise save delays would be /way/ beyond >> unacceptable > > I'd like to know more, and understand the reason, for sure. As far as I know, filetree will rewrite the whole package to disk everytime... and maybe optimising that could be the solution. > Well, that explains a lot. Writing all every time is the lazy thing that's okay for a prototype and temporary code in a proof of concept but that massive redundant reads certainly doesn't sounds like pro software. Specially for SSD's which has a limited quantity of writes > Thierry > >> sebastian <https://about.me/sebastianconcept> >> >> o/ >> >> >> >> >> > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

Dec. 11, 2013

Re: [Pharo-dev] Tell me about your workflow

by Goubier Thierry

Le 11/12/2013 15:18, Sebastian Sastre a Ã©crit : > Are you using git with your Pharo based software? Yes > If you do, are you using filetree? gitfiletree (it uses the filetree code path for writing, and a git archive path for reading) > I ask because I'm worried about scale. > > I have packages (in the order of hundreds of classes) and save delays > and package click delays are starting to demand patience in a way that > doesn't feel like the right path Which operations ? I didn't remember noticing much with 179 classes on a laptop without a SSD. > All that is with a SSD disk, otherwise save delays would be /way/ beyond > unacceptable I'd like to know more, and understand the reason, for sure. As far as I know, filetree will rewrite the whole package to disk everytime... and maybe optimising that could be the solution. Thierry > sebastian <https://about.me/sebastianconcept> > > o/ > > > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Dec. 11, 2013

Tell me about your workflow

by Sebastian Sastre

Are you using git with your Pharo based software? If you do, are you using filetree? I ask because I'm worried about scale. I have packages (in the order of hundreds of classes) and save delays and package click delays are starting to demand patience in a way that doesn't feel like the right path All that is with a SSD disk, otherwise save delays would be way beyond unacceptable sebastian o/

Dec. 11, 2013

Re: [Pharo-dev] Searchbar in the browser

by Juraj Kubelka

Does it means, when I start to type â-Pâ it will display all the packages which contain class with character âpâ or âPâ? In order to be consists we should use the same regular expressions as for packages. So, If I want all packages which contain class beginning with âpâ, it should be â-^pâ. Regular expressions are case insensitive. Thanks, Jura El 11-12-2013, a las 4:48, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> escribiÃ³: > No in fact this is about filtering classes directly without opening the finder > >>> Hi Stef, >>> >>> I am thinking about the -Point suggestion. Why this? Why not to use Cmd+f,cmd+c (find class), or shift+enter (spotlight)? >> >> Indeed we do not need it :) >> >> > >

Dec. 11, 2013

Re: [Pharo-dev] Searchbar in the browser

by Juraj Kubelka

El 11-12-2013, a las 4:09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> escribiÃ³: > > On Dec 10, 2013, at 11:42 PM, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: > >> We can use any regular expression. For that reason I am thinking how to do the filter feature more apparent. Maybe a ghost text is enough. I will play with it. > > ghosttext is simple and working. OK, I did it this way and we will see :-) https://pharo.fogbugz.com/f/cases/12384/Package-filter-dialog-Make-the-feat… Thanks, Jura >> >> Jura >> >> El 10-12-2013, a las 19:14, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> escribiÃ³: >> >>> I like it! >>> use it all the time. I was not aware that we could use | >>> >>> >>>> >>>> El 10-12-2013, a las 9:12, Alexandre Bergel <alexandre.bergel(a)me.com> escribiÃ³: >>>> >>>>>> If I search for something, I always Shift-Enter and that works super. For the rest, there are menus and keyboard shortcuts. >>>>> >>>>> Actually, this is quite different. Shift-Enter this is for searching. The textfield in Nautilus is for filtering packages >>>>> >>>> >>>> Yes, the package filter allows to see only packages you are interested. See the attachment. >>>> Cheers, >>>> Jura >>>> >>>> <Captura de pantalla 2013-12-10 a la(s) 18.24.33.png> >>>> >>>> >>>>> Alexandre >>>>> >>>>> >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>> >>> >> >

Dec. 11, 2013

[pharo-project/pharo-core]

by GitHub

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

Dec. 11, 2013