- Pharo-users - lists.pharo.org

Re: [Pharo-users] when iterating over a collection how to determine the current objects index

by Werner Kassens

Hi, there are several methods that end with withBlaBla: aBlabla (ok, they have generally several arguments). hence i would expect doWithIndex: to have this form #doWithIndex: anIndex. and anything that ends with do: expects a doBlock and several methods that have the form doSomething: dont expect a block as argument. iow i find withIndexDo: more logical than doWithIndex: werner

March 16, 2015

Re: [Pharo-users] when iterating over a collection how to determine the current objects index

by jtuchel＠objektfabrik.de

Nicolai, Am 16.03.15 um 11:59 schrieb Nicolai Hess: > > 2015-03-14 11:55 GMT+01:00 Sean P. DeNigris <sean(a)clipperadams.com > <mailto:sean@clipperadams.com>>: > > Marcus Denker-4 wrote > > which version do we pick? We should pick one, rename the callers > > As someone mentioned earlier in the thread, #doWithIndex: has the > advantage > of mirroring the argument order (although this still should be > documented), > and it's the one most people are probably most familiar with, so > IMHO it > makes sense to standardize on that. > > > I like withIndexDo: because code like > so how would you name the current #do: if you had the choice? I still think this looks very logical: #do: #do:separatedBy: #doWithIndex: #doWithSomeOtherSpecialty:andEvenMoreStuff: And then there still ist the question if the order of the arguments should be changed: today: do: [:each| ] doWithIndex: [:each :index| ] future: do: [:each| ] withIndexDo: [:idx :each | ] Do you really think that is better? I think that if we move the withIndex part to the beginning of the message, it overstates the importance of the fact that we also need the index inside the iteration block. > aCollection withIndexDo: aBlock > reads like > "a collection with index" do > This would make sense if it was a Collection with an Index. If there was an IndexedCollection class and maybe some message like asIndexedCollection or withIndex, which turns any collection into an IndexedCollection. Then the message might be a shortcut for "make thsi an indexed collection and iterate over it using its index" - comparable to Dictionary>>#keysAndValuesDo: - but please be aware that a Dictionary has keys and values by its very own nature. A Collection doesn't have an index (other than the fact that the elements are stored in some non-guarantueed order). This may all sound quite picky, but I think this is plain wrong and you are about to introduce not only incompatible, but also misleading naming for methods that exist on all Smalltalk dialects. Joachim > > > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/when-iterating-over-a-collection-how-to-determine-the… > Sent from the Pharo Smalltalk Users mailing list archive at > Nabble.com. > > -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1 http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1

March 16, 2015

Re: [Pharo-users] when iterating over a collection how to determine the current objects index

by Nicolai Hess

2015-03-14 11:55 GMT+01:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Marcus Denker-4 wrote > > which version do we pick? We should pick one, rename the callers > > As someone mentioned earlier in the thread, #doWithIndex: has the advantage > of mirroring the argument order (although this still should be documented), > and it's the one most people are probably most familiar with, so IMHO it > makes sense to standardize on that. > I like withIndexDo: because code like aCollection withIndexDo: aBlock reads like "a collection with index" do > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/when-iterating-over-a-collection-how-to-determine-the… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

March 16, 2015

Re: [Pharo-users] Error while loading GitFileTree in Pharo 4.0

by Jigyasa Grover

The 'missing' files are present in the zip folder , but they arent in the github-cache folder from where the Pharo is accessing it On Mon, Mar 16, 2015 at 2:51 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Can you check if the missing file is present in the zip, and in the > decompressed part on disk? > > Note that we are dealing with a Metacello/FileTree error, not a > GitFileTree one. > > Thierry > > 2015-03-16 9:56 GMT+01:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: > >> Yes Sir. >> I have checked 'em all. >> >> [image: Inline image 2][image: Inline image 1][image: Inline image 4][image: >> Inline image 3] >> >> On Mon, Mar 16, 2015 at 2:22 PM, Thierry Goubier < >> thierry.goubier(a)gmail.com> wrote: >> >>> This is strange. >>> >>> I tried both the Gofer and the Metacello script before replying to you, >>> and they both worked. >>> >>> Do you have a file named >>> github-dalehenrichfiletreepharo40dev<number>.zip in your pharo repository? >>> Do you have a directory named >>> >>> >>> github-cache/dalehenrich/filetree/pharo4.0_dev/dalehenrich-filetree-7f998e5 >>> >>> Thierry >>> >>> 2015-03-16 9:43 GMT+01:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: >>> >>>> Sir >>>> I have cleared the previous files and tried to load directly from >>>> github as directed by you. >>>> The error still persists. There are missing files again. >>>> >>>> Thanks >>>> Jigyasa Grover >>>> >>>> On Mon, Mar 16, 2015 at 2:07 PM, Thierry Goubier < >>>> thierry.goubier(a)gmail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> an alternative solution is to load directly from github, with: >>>>> >>>>> Metacello new >>>>> baseline: 'FileTree'; >>>>> repository: 'github://dalehenrich/filetree:pharo4.0_dev/repository'; >>>>> load: 'Git' >>>>> >>>>> Missing files may mean a leftover from a previous, failed load attempt. >>>>> >>>>> Thierry >>>>> >>>>> 2015-03-16 8:19 GMT+01:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: >>>>> >>>>>> Thanks! >>>>>> >>>>>> The error now says = File missing : >>>>>> ..\repository\MonticelloFileTree-Git.package\monticello.meta\version >>>>>> >>>>>> What is the way out ? >>>>>> >>>>>> >>>>> >>>> >>> >> >

March 16, 2015

Re: [Pharo-users] Error while loading GitFileTree in Pharo 4.0

by Thierry Goubier

Can you check if the missing file is present in the zip, and in the decompressed part on disk? Note that we are dealing with a Metacello/FileTree error, not a GitFileTree one. Thierry 2015-03-16 9:56 GMT+01:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: > Yes Sir. > I have checked 'em all. > > [image: Inline image 2][image: Inline image 1][image: Inline image 4][image: > Inline image 3] > > On Mon, Mar 16, 2015 at 2:22 PM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> This is strange. >> >> I tried both the Gofer and the Metacello script before replying to you, >> and they both worked. >> >> Do you have a file named github-dalehenrichfiletreepharo40dev<number>.zip >> in your pharo repository? Do you have a directory named >> >> >> github-cache/dalehenrich/filetree/pharo4.0_dev/dalehenrich-filetree-7f998e5 >> >> Thierry >> >> 2015-03-16 9:43 GMT+01:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: >> >>> Sir >>> I have cleared the previous files and tried to load directly from github >>> as directed by you. >>> The error still persists. There are missing files again. >>> >>> Thanks >>> Jigyasa Grover >>> >>> On Mon, Mar 16, 2015 at 2:07 PM, Thierry Goubier < >>> thierry.goubier(a)gmail.com> wrote: >>> >>>> Hi, >>>> >>>> an alternative solution is to load directly from github, with: >>>> >>>> Metacello new >>>> baseline: 'FileTree'; >>>> repository: 'github://dalehenrich/filetree:pharo4.0_dev/repository'; >>>> load: 'Git' >>>> >>>> Missing files may mean a leftover from a previous, failed load attempt. >>>> >>>> Thierry >>>> >>>> 2015-03-16 8:19 GMT+01:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: >>>> >>>>> Thanks! >>>>> >>>>> The error now says = File missing : >>>>> ..\repository\MonticelloFileTree-Git.package\monticello.meta\version >>>>> >>>>> What is the way out ? >>>>> >>>>> >>>> >>> >> >

March 16, 2015

Re: [Pharo-users] Viva: animation framework published in the metaRepo for Pharo40

by Nicolai Hess

2015-03-15 21:34 GMT+01:00 stepharo <stepharo(a)free.fr>: > Hi > > Viva is a small framework to define animation developed by igor Stasenko. > It is used by Roassal2 for its animation. > Now Viva is published in its own repository > > MCHttpRepository > location: 'http://www.smalltalkhub.com/mc/RMoD/Viva/main' > user: '' > password: '' > > and published in the configuration repository for Pharo 40. > > Stef > > Looks good, pretty much what I had in mind for a basic animation framework. How about making the animated value more generic and independent of a timer, more like a "binding" source -> property binding -> target and an (timer-)animated binding timer as source -> property binding -> target As I was thinking about an animation framework I got the idea of some more generic components. The components I had in mind: Clock EventQueue Task Binding or PropertyWrapper Range (as a source for interpolators) Interpolators Transition/Animation ( connection of a source(timer) and property bind, together with a range interpolator). scaling/easing function (linear/quad/quadIn/quadOut) Clock, EventQueue and Task classes (maybe we have some of them already) may be usable for other things and are used here as building blocks for the (transition/animation) framework. (The idea is, to not invent a TimerFrameWorkClock/ TimerFrameWorkEvent / TimerFrameWorkXXX....) Do you know this Squeak (Morphic) Animation Framework ( https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/wiki…) ? I like how it wraps different property animation in different animation classes (AlphaBlendAnimation/ColorAnimation ...). (I wonder why it is nowhere used) And there is GLMAnimation, but I don't like how it is implemented. nicolai

March 16, 2015

Re: [Pharo-users] Error while loading GitFileTree in Pharo 4.0

by Jigyasa Grover

Yes Sir. I have checked 'em all. [image: Inline image 2][image: Inline image 1][image: Inline image 4][image: Inline image 3] On Mon, Mar 16, 2015 at 2:22 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > This is strange. > > I tried both the Gofer and the Metacello script before replying to you, > and they both worked. > > Do you have a file named github-dalehenrichfiletreepharo40dev<number>.zip > in your pharo repository? Do you have a directory named > > github-cache/dalehenrich/filetree/pharo4.0_dev/dalehenrich-filetree-7f998e5 > > Thierry > > 2015-03-16 9:43 GMT+01:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: > >> Sir >> I have cleared the previous files and tried to load directly from github >> as directed by you. >> The error still persists. There are missing files again. >> >> Thanks >> Jigyasa Grover >> >> On Mon, Mar 16, 2015 at 2:07 PM, Thierry Goubier < >> thierry.goubier(a)gmail.com> wrote: >> >>> Hi, >>> >>> an alternative solution is to load directly from github, with: >>> >>> Metacello new >>> baseline: 'FileTree'; >>> repository: 'github://dalehenrich/filetree:pharo4.0_dev/repository'; >>> load: 'Git' >>> >>> Missing files may mean a leftover from a previous, failed load attempt. >>> >>> Thierry >>> >>> 2015-03-16 8:19 GMT+01:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: >>> >>>> Thanks! >>>> >>>> The error now says = File missing : >>>> ..\repository\MonticelloFileTree-Git.package\monticello.meta\version >>>> >>>> What is the way out ? >>>> >>>> >>> >> >

March 16, 2015

Re: [Pharo-users] Error while loading GitFileTree in Pharo 4.0

by Thierry Goubier

This is strange. I tried both the Gofer and the Metacello script before replying to you, and they both worked. Do you have a file named github-dalehenrichfiletreepharo40dev<number>.zip in your pharo repository? Do you have a directory named github-cache/dalehenrich/filetree/pharo4.0_dev/dalehenrich-filetree-7f998e5 Thierry 2015-03-16 9:43 GMT+01:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: > Sir > I have cleared the previous files and tried to load directly from github > as directed by you. > The error still persists. There are missing files again. > > Thanks > Jigyasa Grover > > On Mon, Mar 16, 2015 at 2:07 PM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> Hi, >> >> an alternative solution is to load directly from github, with: >> >> Metacello new >> baseline: 'FileTree'; >> repository: 'github://dalehenrich/filetree:pharo4.0_dev/repository'; >> load: 'Git' >> >> Missing files may mean a leftover from a previous, failed load attempt. >> >> Thierry >> >> 2015-03-16 8:19 GMT+01:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: >> >>> Thanks! >>> >>> The error now says = File missing : >>> ..\repository\MonticelloFileTree-Git.package\monticello.meta\version >>> >>> What is the way out ? >>> >>> >> >

March 16, 2015

Re: [Pharo-users] Error while loading GitFileTree in Pharo 4.0

by Jigyasa Grover

Sir I have cleared the previous files and tried to load directly from github as directed by you. The error still persists. There are missing files again. Thanks Jigyasa Grover On Mon, Mar 16, 2015 at 2:07 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Hi, > > an alternative solution is to load directly from github, with: > > Metacello new > baseline: 'FileTree'; > repository: 'github://dalehenrich/filetree:pharo4.0_dev/repository'; > load: 'Git' > > Missing files may mean a leftover from a previous, failed load attempt. > > Thierry > > 2015-03-16 8:19 GMT+01:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: > >> Thanks! >> >> The error now says = File missing : >> ..\repository\MonticelloFileTree-Git.package\monticello.meta\version >> >> What is the way out ? >> >> >

March 16, 2015

Re: [Pharo-users] Error while loading GitFileTree in Pharo 4.0

by Thierry Goubier

Hi, an alternative solution is to load directly from github, with: Metacello new baseline: 'FileTree'; repository: 'github://dalehenrich/filetree:pharo4.0_dev/repository'; load: 'Git' Missing files may mean a leftover from a previous, failed load attempt. Thierry 2015-03-16 8:19 GMT+01:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: > Thanks! > > The error now says = File missing : > ..\repository\MonticelloFileTree-Git.package\monticello.meta\version > > What is the way out ? > >

March 16, 2015