May 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Package comments

by stepharo

Kasper our idea is that each package should have meta-data: - default code formatting - false positive for rules - and of course package comment. So for now the simplest thing we did was to add a class called ManifestXXX for packageXXX. This way it is versionned with the classes and we can browse it.... Stef Le 4/5/15 18:33, Kasper Osterbye a Ã©crit : > In the Nautilus browser I have been working a bit on allowing Pillar for > class comments. When browsing that part of Nautilus, I notice that there are > some hooks for package comments in the getComments and addComments methods. > > Is there a history of "package comments" somewhere in the system? I was not > able to find anything like that. Also it does not seem like there are any > fields in the hierarchy of MBInfo that has anything to do with > documentation. Is that the case? > > > > > > -- > View this message in context: http://forum.world.st/Package-comments-tp4824353.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > >

May 6, 2015

Re: [Pharo-dev] last time I had insomnia...

by Esteban Lorenzano

I added you as contributor :) > On 06 May 2015, at 19:03, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > One question, how can I contribute? > > Uko > > >> On 28 Apr 2015, at 17:28, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >> >> >> >> 2015-04-28 15:32 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >> >> > On 28 Apr 2015, at 15:20, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> > >> > >> >> On 28 Apr 2015, at 15:16, Hilaire <hilaire(a)drgeo.eu <mailto:hilaire@drgeo.eu>> wrote: >> >> >> >> Le 28/04/2015 15:05, Esteban Lorenzano a Ã©crit : >> >>> I have to say that I started this because I failed miserably to made >> >>> the eclipse icons work fine in Dark mode. Pharo does not understand >> >>> SVG out of the box, Roassal does it but in the conversion things where >> >>> not rightâ¦ so I found this solution. >> >>> >> >>> Btwâ¦ they look good also in standard theme: >> >>> >> >> >> >> Thanks Esteban, looks is simple, clean. >> >> Did you convert the svg to png or can you import the svg form? >> > >> > No, I failed to convert svg to png (probably just my ignorance) then I took this icons who where already in png but with good transparencies :) >> > >> > Esteban >> >> But on which stage are Athens? Because maybe we can use them for SVG? >> >> It is not that bad. I just fixed one bug with linear gradient construction (used deprecated/removed api). >> >> You can load the latest configuration from the Athens repository. >> And if you have a folder with some svg icons: >> >> >> |files| >> files := ('A_FOLDER_WITH_SVG_FILES' asFileReference allChildrenMatching:'*.svg'). >> files collect:[: >> file ||form| >> [form := ((ASVGMorph fromFile:file)setZoom:5; imageForm) ] on:Error do:[:ex | ]] >> >> many icons are "loadable" but I did not compare the results >> >> >> >> Uko >> >> > >> >> >> >> Hilaire >> >> >> >> -- >> >> Dr. Geo - http://drgeo.eu <http://drgeo.eu/> >> >> iStoa - http://istoa.drgeo.eu <http://istoa.drgeo.eu/> >> >> >> >> >> >> >> > >> >

May 6, 2015

Re: [Pharo-dev] RewriteTool

by Sean P. DeNigris

Sean P. DeNigris wrote > http://smalltalkhub.com/#!/~MarkRizun/RewriteTool/ , which is now about 70 > commits ahead of the first! Alarmingly, Mark's repo seems to only be intermittently available. Many times sthub returns 404... ----- Cheers, Sean -- View this message in context: http://forum.world.st/RewriteTool-tp4824877p4824881.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 6, 2015

RewriteTool

by Sean P. DeNigris

There are two repos: http://smalltalkhub.com/#!/~PharoExtras/RewriteTool , which seems to have been forked some time ago and http://smalltalkhub.com/#!/~MarkRizun/RewriteTool/ , which is now about 70 commits ahead of the first! What should be done? ----- Cheers, Sean -- View this message in context: http://forum.world.st/RewriteTool-tp4824877.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 6, 2015

New Cog VMs available

by Eliot Miranda

... at http://www.mirandabanda.org/files/Cog/VM/VM.r3319. CogVM binaries as per VMMaker.oscog-eem.1288/r3319 Spur: Implement remembered table pruning via ref counts. The algorithm selectively tenures objects to reduce the remembered table, instead of merely tenuring everything. Be selective about remembering tenured objects; actually scan their contents before remembering willy-nilly. StackVM: Allow setting preemptionYields in the stack VM. Cogit: Use new register allocation in #== with V3 in order to limit register moves. -- best, Eliot

May 6, 2015

Re: [Pharo-dev] Package comments

by Nicolas Cellier

2015-05-06 13:08 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > > > On 06 May 2015, at 10:53, Christophe Demarey < > Christophe.Demarey(a)inria.fr> wrote: > > > > > > Le 5 mai 2015 Ã 17:14, Kasper Osterbye a Ã©crit : > > > >> Marcus Denker-4 wrote > >>> Right now we do not have yet Package comments. > >>> > >>> But we should! > >>> > >>> MBInfo seems to be a private class of Versionnerâ¦ > >>> > >>> For package comments we first need to evaluate the design spaceâ¦ > >>> e.g. where to store it in the image, how to store it in Monticelloâ¦ > >> > >> OK - Makes sense. > >> > >> From my perspective, the key to getting this of the ground is to make > sure > >> such comments can be written and read in Nautilus. The package objects > used > >> in Nautilus are from "RPackage". > >> Thus, the problem, in my view reduces to: > >> a) How to make room in RPackage for a comment field (add one more IV) > >> b) How to integrate the storage of this field in connection with > Monticello > >> as Marcus writes. > > > > I don't think is the good way to do that. > > We are working on adding meta-data to packages. These meta-data includes > a package description (or comment) but also a lot of other data. > > You will not be able to store everything in rpackage inst. var. And of > course, there is also the problem that Monticello is not able to store > meta-data (e.g. STON files). > > For now, the best option is to use a PackageManifest. > > > > If you want to allow package comments in Nautilus, I would display the > content of the description method of the package manifest if available. > > > > Yesâ¦ this could be the easiest for now. > > Then as a second step, we add support to store resources in Monticello. > > Marcus > > > Adding metadata to MC cannot be very difficult, MC already carries plenty of metadata ;) Coordination with other dialects (squeak/gemstone/...) would be welcome, because i'm sure that every dialect would benefit from package comments, or already has package comments (vw along with many other properties). No long discussion required, if no consensus, just let Pharo lead. I remember that Bert has experimented adding a comment to PackageInfo, but I don't know in which state it did end up (MC-wise). Nicolas

May 6, 2015

Re: [Pharo-dev] last time I had insomnia...

by Yuriy Tymchuk

One question, how can I contribute? Uko > On 28 Apr 2015, at 17:28, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-04-28 15:32 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: > > > On 28 Apr 2015, at 15:20, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > > > > > >> On 28 Apr 2015, at 15:16, Hilaire <hilaire(a)drgeo.eu <mailto:hilaire@drgeo.eu>> wrote: > >> > >> Le 28/04/2015 15:05, Esteban Lorenzano a Ã©crit : > >>> I have to say that I started this because I failed miserably to made > >>> the eclipse icons work fine in Dark mode. Pharo does not understand > >>> SVG out of the box, Roassal does it but in the conversion things where > >>> not rightâ¦ so I found this solution. > >>> > >>> Btwâ¦ they look good also in standard theme: > >>> > >> > >> Thanks Esteban, looks is simple, clean. > >> Did you convert the svg to png or can you import the svg form? > > > > No, I failed to convert svg to png (probably just my ignorance) then I took this icons who where already in png but with good transparencies :) > > > > Esteban > > But on which stage are Athens? Because maybe we can use them for SVG? > > It is not that bad. I just fixed one bug with linear gradient construction (used deprecated/removed api). > > You can load the latest configuration from the Athens repository. > And if you have a folder with some svg icons: > > > |files| > files := ('A_FOLDER_WITH_SVG_FILES' asFileReference allChildrenMatching:'*.svg'). > files collect:[: > file ||form| > [form := ((ASVGMorph fromFile:file)setZoom:5; imageForm) ] on:Error do:[:ex | ]] > > many icons are "loadable" but I did not compare the results > > > > Uko > > > > >> > >> Hilaire > >> > >> -- > >> Dr. Geo - http://drgeo.eu <http://drgeo.eu/> > >> iStoa - http://istoa.drgeo.eu <http://istoa.drgeo.eu/> > >> > >> > >> > > > >

May 6, 2015

Re: [Pharo-dev] Class Comment Template Suggestion

by Richard Sargent

stepharo wrote > I have no problem with changing it this is just that we should in > general write much better class comments. This is true for all commentary. :-) One of the most important things to include in comments and which is usually omitted is the rationale. Explain why the class exists (it may be obvious in many cases; but usually not so obvious to an outsider), when and why you would use the class. And of course, this doesn't mean we should ignore how to use it. > Stef > > Le 29/4/15 15:17, Sean P. DeNigris a Ã©crit : >> The class comment template begins: "For the Class part: State the name >> of >> the class with one line description: For example, I'm xxx the root of the >> hierarchy of visitor objects." >> >> Unlike a traditional CRC card, we are already in a live programming >> environment with good tools! So the class name is duplicated info (the >> browser already shows this) which will have to be manually changed on a >> class rename. Also, the specific example provides an implementation >> detail >> duplicated by the class hierarchy tree already shown in the browser. I'd >> like to change it to: "For the Class part: State a one line summary. For >> example, "I represent a paragraph of text."" >> >> Any objections? >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Class-Comment-Template-Suggestion-tp4822890.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> -- View this message in context: http://forum.world.st/Class-Comment-Template-Suggestion-tp4822890p4824840.h… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 6, 2015

Re: [Pharo-dev] [Pharo-Dev] BDD framework

by Dennis Schetinin

There's Mocketry [http://www.smalltalkhub.com/#!/~dionisiy/Mocketry] It does not support the Given-When-Then constructs, but it has its own Spec DSL (nearly natural english indeed:) and I believe it is pretty enough to practice TDD/BDD. -- Best regards, Dennis Schetinin 2015-05-06 18:50 GMT+04:00 Maximiliano Taborda <mtaborda(a)gmail.com>: > Hi people, > Is there some framework for BDD in Pharo? Something like Behave or > Cucumber? > > Thanks. > > Regards. > Maxi >

May 6, 2015

Re: [Pharo-dev] [Pharo-Dev] BDD framework

by Christophe Demarey

Hi, I have this link but no more information: Kiwi TDD (https://www.youtube.com/watch?v=m2t_MbVAdis) Regards, Christophe Le 6 mai 2015 Ã 16:50, Maximiliano Taborda a Ã©crit : > Hi people, > Is there some framework for BDD in Pharo? Something like Behave or Cucumber? > > Thanks. > > Regards. > Maxi

May 6, 2015