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

Re: [Pharo-dev] It would be too expensive to add a description for packages in Configuration Browser?

by StÃ©phane Ducasse

On Dec 7, 2013, at 8:44 PM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Is there a specific reason why this was not implemented? Is someone working on this? We added catalog metadata to configuration now - the tools should take into account about that - people should add such metadata to their configuration If you modify the package browser to present description it will be in the system Stef > See the "Perl Package Manager" for example. > > When you launch it, takes some time to update but each item displays the Details and you have an Abstract colum. > > Cheers, > > HernÃ¡n > >

Dec. 7, 2013

It would be too expensive to add a description for packages in Configuration Browser?

by HernÃ¡n Morales Durand

Is there a specific reason why this was not implemented? Is someone working on this? See the "Perl Package Manager" for example. When you launch it, takes some time to update but each item displays the Details and you have an Abstract colum. Cheers, HernÃ¡n

Dec. 7, 2013

Re: [Pharo-dev] Voronoi diagram

by HernÃ¡n Morales Durand

Check this out http://www.smalltalkhub.com/#!/~goonsh/Voronoi-2d-Diagram http://www.squeaksource.com/VoronoiDiagram.html There is also an old package implementing Voronoi diagrams also, I can have a look if you those are not enough for your needs. Cheers HernÃ¡n El 07/12/2013 13:59, Natalia Tymchuk escribiÃ³: > Hello. > I started implementing visualization of Voronoi diagrams and I need to > do a lot of operations on the lines and polygons. I have some questions: > Is it implemented somewhere? > Did somebody do something with the Voronoi diagrams? > > Best regards, > Natalia > >

Dec. 7, 2013

Voronoi diagram

by Natalia Tymchuk

Hello. I started implementing visualization of Voronoi diagrams and I need to do a lot of operations on the lines and polygons. I have some questions: Is it implemented somewhere? Did somebody do something with the Voronoi diagrams? Best regards, Natalia

Dec. 7, 2013

Re: [Pharo-dev] Pharo magic

by Alexandre Bergel

Yes, this is great! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Dec 6, 2013, at 3:05 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Maybe others noticed the same: > > - the numbers of closed issues is amazing(see the news on the homepage) > - Pharo3.0 is already really usable and a pleasure to work with > - more and more nice projects appear on STHub and elsewhere > - more and more Pharo projects use continuous integration > - most projects and packages are loadable from the config browser and other places without > conflicting with each other > - there is so much activity regarding Pharo these days on mailinglists, bug-tracker, > twitter, conferences, blogs, stackoverflow, github ... it becomes hard to follow > but this is a good sign > - I see more and more fixes and improvements already as an update coming in before > I really realize that an own bug is needed because it improves the situation > - more and more new names appear on the dev and user mailinglist which is a good > sign that there is growing interest > - Pharo is on the right track and I like to be on the train > > Step by step it goes... > > Bye > T. > > > >

Dec. 7, 2013

Re: [Pharo-dev] Committing slices to Pharo30Inbox still doesn't work for me

by Marcus Denker

It should be noted that until now, nobody did anything. On 05 Dec 2013, at 08:10, Marcus Denker <marcus.denker(a)inria.fr> wrote: > It would be nice if someone else but me could do thisâ¦ small things like this can suck away *all* time > if only one person does them. > > (and no, I *never* had problems to submit a sliceâ¦) > > > On 04 Dec 2013, at 20:54, Stephan Eggermont <stephan(a)stack.nl> wrote: > >> Hereâs a new slice, the corresponding packages are in the inbox. >> <SLICE-Issue-12324-There-should-be-no-class-side-implementations-of-packages-except-for-ClassDescription-StephanEggermont.2.mcz> > >

Dec. 7, 2013

[pharo-project/pharo-core] 70150f: 30630

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 70150f94f080ddeb4d25f9770e7c1fd5d0a7e6e0 https://github.com/pharo-project/pharo-core/commit/70150f94f080ddeb4d25f977… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-12-07 (Sat, 07 Dec 2013) Changed paths: M Gofer-Tests.package/GoferOperationTest.class/instance/utilities/hasPackage_.st M Gofer-Tests.package/GoferOperationTest.class/instance/utilities/hasVersion_.st R Komitter.package/KomitClass.class/instance/testing/isClass.st A Komitter.package/KomitClass.class/instance/testing/isKomitClass.st R Komitter.package/KomitLoadingNode.class/README.md R Komitter.package/KomitLoadingNode.class/definition.st R Komitter.package/KomitLoadingNode.class/instance/accessing/icon.st R Komitter.package/KomitLoadingNode.class/instance/as yet unclassified/label.st R Komitter.package/KomitNode.class/instance/as yet unclassified/=.st A Komitter.package/KomitNode.class/instance/comparing/=.st A Komitter.package/KomitNode.class/instance/comparing/hash.st R Komitter.package/KomitObject.class/instance/testing/isClass.st A Komitter.package/KomitObject.class/instance/testing/isKomitClass.st A Komitter.package/KomitPackage.class/instance/comparing/hash.st M Komitter.package/KomitSliceUI.class/definition.st R Komitter.package/KomitSliceUI.class/instance/protocol/loading.st R Komitter.package/KomitSliceUI.class/instance/protocol/loading_.st R Komitter.package/KomitTreeBuilder.class/class/private/stagingArea.st R Komitter.package/KomitTreeBuilder.class/class/protocol/roots.st A Komitter.package/KomitterManager.class/README.md A Komitter.package/KomitterManager.class/class/accessing/current.st A Komitter.package/KomitterManager.class/class/instance creation/new.st A Komitter.package/KomitterManager.class/definition.st A Komitter.package/KomitterManager.class/instance/initialize/initialize.st A Komitter.package/KomitterManager.class/instance/protocol/reset.st A Komitter.package/KomitterManager.class/instance/protocol/storeVersion_for_.st A Komitter.package/KomitterManager.class/instance/protocol/versionFor_.st M Komitter.package/KomitterUI.class/class/specs/defaultSpec.st M Komitter.package/KomitterUI.class/definition.st M Komitter.package/KomitterUI.class/instance/initialization/initializeLatelyPresenter.st M Komitter.package/MCKomitSubmitter.class/instance/protocol/commitSlice_.st M Komitter.package/MCKomitSubmitter.class/instance/protocol/createVersionFor_.st A Komitter.package/extension/MCPackage/instance/version.st M Komitter.package/extension/MCPatch/instance/initializeWithTarget_.st A Komitter.package/extension/MCWorkingCopy/instance/collectSliceDependenciesWithMessage_in_.st A Komitter.package/extension/MCWorkingCopy/instance/silentUniqueVersionNameIn_.st A Komitter.package/extension/MCWorkingCopy/instance/silentlyNewSliceVersionWithName_message_in_.st M Manifest-CriticBrowser.package/CriticBrowser.class/instance/menu/menu_shifted_.st M Manifest-CriticBrowser.package/CriticBrowser.class/instance/private/reapplyThisRule.st M Monticello.package/MCDictionaryRepository.class/instance/accessing/closestAncestorVersionFor_ifNone_.st M MonticelloGUI.package/MCSnapshotBrowser.class/instance/text/classCommentString.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script285.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30630.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30630 12364 Cherry pick does not work for slices https://pharo.fogbugz.com/f/cases/12364 12365 Critics browser menu not working https://pharo.fogbugz.com/f/cases/12365 12338 Cleanup on some Monticello related methods https://pharo.fogbugz.com/f/cases/12338 http://files.pharo.org/image/30/30630.zip

Dec. 7, 2013

[pharo-project/pharo-core]

by GitHub

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

Dec. 7, 2013

Re: [Pharo-dev] Pharo magic

by Sebastian Sastre

That's actually great advice coming from a time-tested source :D On Dec 7, 2013, at 6:38 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > Welcome Nicolai. Actually small contributions is what most open source projects are made of since the majority of people don't have the luxury of free time or the motivation to contribute big chunks of code. But as It has been said it makes a huge difference because when you count in the amount of small contribution they make a rather big chunk of code. Plus if I ever encounter a bug fix or enhancement that makes my life easier there is no way I will be complaining about its size if you know what I mean ;D > > We have a saying here at Greece "water drops can crack even the hardest rock" which dates back to ancient Greece.

Dec. 7, 2013

Re: [Pharo-dev] Using TreeModel>>selectAll

by Benjamin

roots := #(1 2 3) collect: [ :e | TreeNodeModel new content: e ; yourself ]. TreeModel new roots: roots; multiSelection: true; openWithSpec. roots third selected: true; takeHighlight Ben On 07 Dec 2013, at 05:44, Martin Dias <tinchodias(a)gmail.com> wrote: > ouch! thanks Ben. > > Another related question: is there any way of selecting an arbitrary > item? I tried (among others) with: > > TreeModel new > roots: #(1 2 3); > multiSelection: true; > openWithSpec; > selection: 3 > > without success. > > Cheers, > MartÃn > > > > On Thu, Dec 5, 2013 at 4:17 PM, Benjamin > <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >> your tree here is single selection so it will not work >> >> TreeModel new >> roots: #(1 2 3); >> multiSelection: true; >> openWithSpec; >> selectAll >> >> Ben >> >> On 05 Dec 2013, at 15:38, Martin Dias <tinchodias(a)gmail.com> wrote: >> >> Hi, >> >> I'm not sure how this method should be used. I tried in different >> ways, for example: >> >> TreeModel new >> roots: #(1 2 3); >> selectAll; >> openWithSpec >> >> But always the items are unselected. Is it a bug? or I didn't find the >> way to use it? >> >> Thanks, >> MartÃn >> >> >

Dec. 7, 2013