- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Smark doc/use?

by StÃ©phane Ducasse

thanks I will integrate it. Stef On Jun 16, 2013, at 8:00 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > actually that is related to a bug in 3.0 :/ > > => https://pharo.fogbugz.com/default.asp?10920 > > > On 2013-06-16, at 19:50, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> #profile: is supposed to open the profiler on the given benchmark. >> let me fix that :) >> >> On 2013-06-16, at 19:16, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> SMarkLoops profile: #benchArrayAccess >>> >>> does not work >>> >>> I was wondering if this is the class side version of runBenchmark: >>> >>> Stef >>> >>> >>> On Jun 16, 2013, at 12:12 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: >>> >>>> I started to read the code (and its self-documentation aspect is not totally there). >>>> >>>> >>>> (SMarkLoops new runOnly: #benchFloatLoop) run >>>> >>>> Stefan I started to comment the code so are you interested in the commits? >>>> >>>> >>>> Stef >>>> >>>> >>>>> Hi camillo/Stefan >>>>> >>>>> I would like to know how to use SMark and document it. >>>>> Do you have a start of a blog/doc/slide that I can use as a start? >>>>> >>>>> I'm thinking that I could use the implementation of Trie of Benoit and the one of Cuis >>>>> as an example to do some benchs. >>>>> Since I'm not fluent in benchmarks, I think that this the occasion to learn. >>>>> >>>>> Stef >

June 16, 2013

Re: [Pharo-dev] Smark doc/use?

by Camillo Bruni

actually that is related to a bug in 3.0 :/ => https://pharo.fogbugz.com/default.asp?10920 On 2013-06-16, at 19:50, Camillo Bruni <camillobruni(a)gmail.com> wrote: > #profile: is supposed to open the profiler on the given benchmark. > let me fix that :) > > On 2013-06-16, at 19:16, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> SMarkLoops profile: #benchArrayAccess >> >> does not work >> >> I was wondering if this is the class side version of runBenchmark: >> >> Stef >> >> >> On Jun 16, 2013, at 12:12 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: >> >>> I started to read the code (and its self-documentation aspect is not totally there). >>> >>> >>> (SMarkLoops new runOnly: #benchFloatLoop) run >>> >>> Stefan I started to comment the code so are you interested in the commits? >>> >>> >>> Stef >>> >>> >>>> Hi camillo/Stefan >>>> >>>> I would like to know how to use SMark and document it. >>>> Do you have a start of a blog/doc/slide that I can use as a start? >>>> >>>> I'm thinking that I could use the implementation of Trie of Benoit and the one of Cuis >>>> as an example to do some benchs. >>>> Since I'm not fluent in benchmarks, I think that this the occasion to learn. >>>> >>>> Stef

June 16, 2013

Re: [Pharo-dev] Smark doc/use?

by Camillo Bruni

#profile: is supposed to open the profiler on the given benchmark. let me fix that :) On 2013-06-16, at 19:16, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > SMarkLoops profile: #benchArrayAccess > > does not work > > I was wondering if this is the class side version of runBenchmark: > > Stef > > > On Jun 16, 2013, at 12:12 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > >> I started to read the code (and its self-documentation aspect is not totally there). >> >> >> (SMarkLoops new runOnly: #benchFloatLoop) run >> >> Stefan I started to comment the code so are you interested in the commits? >> >> >> Stef >> >> >>> Hi camillo/Stefan >>> >>> I would like to know how to use SMark and document it. >>> Do you have a start of a blog/doc/slide that I can use as a start? >>> >>> I'm thinking that I could use the implementation of Trie of Benoit and the one of Cuis >>> as an example to do some benchs. >>> Since I'm not fluent in benchmarks, I think that this the occasion to learn. >>> >>> Stef >>> >>> >> >> > >

June 16, 2013

Re: [Pharo-dev] Package Browser and System Organization

by GOUBIER Thierry

Hi Stephen, I already have such a top-level scheme, but a bit deeper than you describe, with three levels, for Pharo 2.0. It has top-level categories and then it uses a prefix-matching approach (i.e. all configurations goes under Packages>>Configurations). Then, if a package has categories, it will split between categories as an usual browser will do. The goal is to limit each level to a max of ~ 10 / 20 entries at most. It does not require any change to RPackage, PackageInfo and friends (but has to stay synchronized with their API and keep track of system changes such as loading/unloading/creating a package). You can have a look at the code at: https://github.com/ThierryGoubier/AltBrowser Specifically AltBrowser class>>defaultPackageCategoriesNames https://github.com/ThierryGoubier/AltBrowser/blob/master/Alt-Browser.packag… and AltBrowser class>>getRootItems https://github.com/ThierryGoubier/AltBrowser/blob/master/Alt-Browser.packag… Where you will see how the system uses the current list of existing packages and the MC/RPackage API. Thierry ________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Stephen Travis Pope [stephen(a)heaveneverywhere.com] Date d'envoi : samedi 15 juin 2013 21:20 Ã : pharo-dev(a)lists.pharo.org Objet : [Pharo-dev] Package Browser and System Organization Hello Phar-ites! I was at the STIC conference this week, and decided to do a small project in Pharo to "get my feet wet." I ported the "Package Browser" (AKA 6-paned browser) that I prefer to use. the basic idea of it is to parse the system categories into a 2-level hierarchy so that the left-most pane is the top-most packages (Collections, Kernel, System, etc.). If the system is well-organized, this list hardly needs a scroll bar! I'm attaching the code with this letter for your edification. To use the PackageBrowser, it really helps if the system categories form a nice 2-level hierarchy, as in , Collections-Abstract Collections-Arithmetic Collections-Arrayed Graphics-Files Graphics-Fonts Graphics-Primitives etc. The second file below is a system re-org for a Pharo 2.0 image. Obviously this is quite release-dependent, so it would be good to do this once in the release cycle for 3.0. In the "old days," there were about 12 top-level packages -- will this work in Pharo? Enjoy! Stephen Pope (stp) ---- Stephen Travis Pope - stephen(a)FASTLabInc.com<mailto:stephen@FASTLabInc.com> - Santa Barbara, CA

June 16, 2013

Re: [Pharo-dev] Smark doc/use?

by StÃ©phane Ducasse

ok apparently I was running it on 30 and not 20. Stef On Jun 16, 2013, at 7:16 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > SMarkLoops profile: #benchArrayAccess > > does not work > > I was wondering if this is the class side version of runBenchmark: > > Stef > > > On Jun 16, 2013, at 12:12 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > >> I started to read the code (and its self-documentation aspect is not totally there). >> >> >> (SMarkLoops new runOnly: #benchFloatLoop) run >> >> Stefan I started to comment the code so are you interested in the commits? >> >> >> Stef >> >> >>> Hi camillo/Stefan >>> >>> I would like to know how to use SMark and document it. >>> Do you have a start of a blog/doc/slide that I can use as a start? >>> >>> I'm thinking that I could use the implementation of Trie of Benoit and the one of Cuis >>> as an example to do some benchs. >>> Since I'm not fluent in benchmarks, I think that this the occasion to learn. >>> >>> Stef >>> >>> >> >> > >

June 16, 2013

Re: [Pharo-dev] Smark doc/use?

by StÃ©phane Ducasse

SMarkLoops profile: #benchArrayAccess does not work I was wondering if this is the class side version of runBenchmark: Stef On Jun 16, 2013, at 12:12 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > I started to read the code (and its self-documentation aspect is not totally there). > > > (SMarkLoops new runOnly: #benchFloatLoop) run > > Stefan I started to comment the code so are you interested in the commits? > > > Stef > > >> Hi camillo/Stefan >> >> I would like to know how to use SMark and document it. >> Do you have a start of a blog/doc/slide that I can use as a start? >> >> I'm thinking that I could use the implementation of Trie of Benoit and the one of Cuis >> as an example to do some benchs. >> Since I'm not fluent in benchmarks, I think that this the occasion to learn. >> >> Stef >> >> > >

June 16, 2013

Re: [Pharo-dev] GetText working with pharo 2.0

by Hilaire Fernandes

Thanks Hilaire Le 16/06/2013 09:54, Usman Bhatti a Ã©crit : > I made a few changes to make GetText pharo 2.0 compatible and now its > functional, I committed a version. I retraced the steps of the tutorial > <http://book.pharo-project.org/book/LanguageAndLibraries/Localisation/Instal…> > and its working. > Tests will be added a bit later ;). > > Usman -- Dr. Geo http://drgeo.eu

June 16, 2013

Re: [Pharo-dev] Package Browser and System Organization

by StÃ©phane Ducasse

>> Hello Phar-ites! >> >> I was at the STIC conference this week, and decided to do a small project in Pharo to "get my feet wet." I ported the "Package Browser" (AKA 6-paned browser) that I prefer to use. the basic idea of it is to parse the system categories into a 2-level hierarchy so that the left-most pane is the top-most packages (Collections, Kernel, System, etc.). If the system is well-organized, this list hardly needs a scroll bar! >> > > Yes, we need to improve how the browser shows the packages. And we need to seriously clean put he packages we haveâ¦. right now it is just far too un-organized and un-browsable. it is not that bad. You can find a package either directly typing the beginning of its name, or using a shortcut. For classes the short cut is working well. What we should do is to finish the rpackage integration. Because we will be able to get rid of PackageInfo. Esteban is aware of that and working on it so it will arrive soon. > Having some 4th categorization will be needed in some form (4th column is one, having packages that show their content as trees is another). > >> I'm attaching the code with this letter for your edification. >> >> To use the PackageBrowser, it really helps if the system categories form a nice 2-level hierarchy, as in , >> >> Collections-Abstract >> Collections-Arithmetic >> Collections-Arrayed >> Graphics-Files >> Graphics-Fonts >> Graphics-Primitives >> etc. >> >> The second file below is a system re-org for a Pharo 2.0 image. Obviously this is quite release-dependent, so it would be good to do this once in the release cycle for 3.0. In the "old days," there were about 12 top-level packages -- will this work in Pharo? > > Sadly it is a bit more complexâ¦ Categories vs. PackageInfo vs. Rpackageâ¦ we should really do another pass over RPackage. Just recategorizing is not enough, as we are managing the system with Monticello and "just" > recategorizing using System Categories is not enoughâ¦ We should not stress about that. If you take any large system you will have many packages. We will get rid of PackageInfo for real soon. So it will be a nice step in the right direction. Stef

June 16, 2013

Re: [Pharo-dev] Package Browser and System Organization

by Marcus Denker

On Jun 15, 2013, at 9:21 PM, Stephen Travis Pope <stephen(a)heaveneverywhere.com> wrote: > > Hello Phar-ites! > > I was at the STIC conference this week, and decided to do a small project in Pharo to "get my feet wet." I ported the "Package Browser" (AKA 6-paned browser) that I prefer to use. the basic idea of it is to parse the system categories into a 2-level hierarchy so that the left-most pane is the top-most packages (Collections, Kernel, System, etc.). If the system is well-organized, this list hardly needs a scroll bar! > Yes, we need to improve how the browser shows the packages. And we need to seriously clean put he packages we haveâ¦. right now it is just far too un-organized and un-browsable. Having some 4th categorization will be needed in some form (4th column is one, having packages that show their content as trees is another). > I'm attaching the code with this letter for your edification. > > To use the PackageBrowser, it really helps if the system categories form a nice 2-level hierarchy, as in , > > Collections-Abstract > Collections-Arithmetic > Collections-Arrayed > Graphics-Files > Graphics-Fonts > Graphics-Primitives > etc. > > The second file below is a system re-org for a Pharo 2.0 image. Obviously this is quite release-dependent, so it would be good to do this once in the release cycle for 3.0. In the "old days," there were about 12 top-level packages -- will this work in Pharo? Sadly it is a bit more complexâ¦ Categories vs. PackageInfo vs. Rpackageâ¦ we should really do another pass over RPackage. Just recategorizing is not enough, as we are managing the system with Monticello and "just" recategorizing using System Categories is not enoughâ¦ Marcus

June 16, 2013

Gmane list archive working again

by Marcus Denker

Hi, Gmane now has been updated to the new list addresses: http://dir.gmane.org/gmane.comp.lang.smalltalk.pharo.devel http://dir.gmane.org/gmane.comp.lang.smalltalk.pharo.user Marcus

June 16, 2013