- Pharo-users - lists.pharo.org

Re: [Pharo-users] [ann] moldable brick editor - alpha

by stephan

On 10-08-17 13:09, stephan wrote: > On 05-08-17 00:19, Tudor Girba wrote: > >Iceberg enableMetacelloIntegration: true. > > That doesn't work. It hangs the image, keeping one CPU > busy. With 60510 that is non-interruptable, b.t.w. Stephan

Aug. 10, 2017

Re: [Pharo-users] [ann] moldable brick editor - alpha

by stephan

On 05-08-17 00:19, Tudor Girba wrote: >Iceberg enableMetacelloIntegration: true. That doesn't work. It hangs the image, keeping one CPU busy. (latest 32 bit vm, ubuntu 16.04LTS) Also the Moz2D is not correctly installed/deinstalled. After warning that the library is not correctly installed, the start/stop script needs to be cleanly removed. Stephan

Aug. 10, 2017

UK Smalltalk User Group Meeting - Monday 21st August

by Giovanni Corriga

The next meeting of the UK Smalltalk User Group Meeting will be on Monday, 21st August. We'll meet at a new venue The City Pride ( http://www. cityprideclerkenwell.co.uk/ ) at 7pm. If you'd like to join us, you can just show up at the pub. You can also sign up in advance at the meeting's Meetup page: *https://www.meetup.com/UKSTUG/events/242432390/ <https://www.meetup.com/UKSTUG/events/242432390/> *. See you there!

Aug. 10, 2017

Re: [Pharo-users] PetitParser: Parse X as long as it's not Y

by Sean P. DeNigris

Peter Kenny wrote > You may need to post-process the parse to get what you > want. Good point. I omitted several ` ==> #second` in several places for readability on the list, but we should mention that for posterity. Also, duh `gen negate and` should be `gen not`! ----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-Parse-X-as-long-as-it-s-not-Y-tp4958895p4… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 10, 2017

Re: [Pharo-users] about a pillar based output format for Epicea

by Stephane Ducasse

Hi for the menu I did a really ugly copy and paste and hack inside and versioned in my package. I did not find the time to think about menu building for Spec. Stef On Wed, Aug 9, 2017 at 6:09 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > > > On Wed, Aug 2, 2017 at 12:55 PM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: >> >> Hi martin >> >> I would like to wlak over epicea objects and save the changed methods >> to be able to write booklets faster. >> What advices can you give me? >> Create a special visitor? > > > For the record, I copy this small explanation from a private email: > > --------- > Epicea models: > - IDE events (refactorings, monticello) -> EpEvent > - code changes (class addition, method modification) -> EpCodeChange > > where EpCodeChange is subclass of EpEvent. > > To create visitors you have EpTEventVisitor and EpTCodeChangeVisitor, that > provide default visitXX: implementations. > ---------- > > Stef, any update on the menu extension? > > indeed I'm not proud of that method you included in another email. I didn't > consider the need to extend such menu (besides it's ugly code, anyway). > > MartÃn > >> >> Stef >> >

Aug. 9, 2017

Checking in on source/dependency management

by sergio ruiz

Hi, all.. I am just checking in on source and dependency management.Â I have been using Pharo 6 for a bit now, and i know that there has been a lot of talk about going to bit for source code management.Â I am wondering how far along that is, and if there is a package we can start using to work through that. I am also wondering if metacello is still the dependency management system of choice. I was using the GUI tool in for package management in pharo 5, but i was having issues with getting my project mangled. Is there a new current view on how all this should be done? Thanks! ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Aug. 9, 2017

Re: [Pharo-users] Stylistic question: private helper vs extension method?

by Herby VojÄÃk

Esteban A. Maringolo wrote: > 2017-08-08 17:49 GMT-03:00 Esteban Lorenzano<estebanlm(a)gmail.com>: >> Extension. Helpers are for javaers. > > Extensions are concise, and right to the point, but as long as they > stay in your private image or prove of value to everybody else both in > function and selector naming. > > My guides are: > A. If it's your image, extend Dictionary, Object or whatever you want. > It's your mess, your image, your rules.\ True. > B. If you're going to share the code with others (as a library), then > you should check whether the selectors clash with existing ones, or > have "side effects". > C. If it's going in the "core" image, then the selector should be well > thought, having broad application semantics and coherence with the > existing selectors, like the current #at:ifAbsent:, #at:ifPresent:, > etc. > > In this case I'd go for something like: > > Dictionary>>#at: key ifPresentPut: aBlock Never imagined it should be at:ifPresentPut:. Not clear at the first sight, but undobutedly it is the best pick, on the second one. > "Lookup the given key in the receiver. If it is present, update it > with the value of evaluating the given block with the value associated > with the key. Otherwise, answer nil." > > ^self at: key ifPresent: [ :object | self at: key put: (aBlock > cull: object) ] Well, if it is seen as a thing of value, you or someone can add it to pharo7 (I probably can not, not having and not wanting to have github account). Maybe for Array / String as well. > And you'd call it like: > responsePayload at: each ifPresentPut: [ :uuid | uuid asString ]. In my case, `responsePayload at: each ifPresentPut: #asString` probably. I don't care for a bit of perf hit (I like Symbol >> value:, during Amber development I often do `Smalltalk packages do: #commit` to commit everything and see what changed in git diff). > or: > responsePayload at: each ifPresentPut: [ 'FooBaz' ]. > > > Regards, > > Esteban A. Maringolo Thanks, Herby

Aug. 9, 2017

Re: [Pharo-users] API docs as HTML

by Offray Vladimir Luna CÃ¡rdenas

Thanks Esteban, Any documentation to start with? How can I install this? Cheers, Offray On 09/08/17 10:08, Esteban Lorenzano wrote: > this was the webdoc project (made originally by Camillo Bruni) > > https://github.com/estebanlm/pharo-webdoc > > butâ¦ you will need to massage it a bit to make it work :) > also, Guille made a simplification some time agoâ¦ he will know where > it is or whatâs his status. > > Esteban > >> On 9 Aug 2017, at 16:41, Offray Vladimir Luna CÃ¡rdenas >> <offray.luna(a)mutabit.com <mailto:offray.luna@mutabit.com>> wrote: >> >> Hi, >> >> For the JOSS (Journal of Open Source Software) I need to add to a >> package documentation the API documentation as an external file >> (hopefully in HTML). So I would like to export the source code in a way >> that can be used as API documentation. I remember that some API >> documentation about Smalltalk/Pharo can be found online, but I don't >> know how to produce such documents. Any pointers to explore? >> >> Cheers, >> >> Offray >> >> >> >

Aug. 9, 2017

Re: [Pharo-users] API docs as HTML

by Esteban Lorenzano

this was the webdoc project (made originally by Camillo Bruni) https://github.com/estebanlm/pharo-webdoc <https://github.com/estebanlm/pharo-webdoc> butâ¦ you will need to massage it a bit to make it work :) also, Guille made a simplification some time agoâ¦ he will know where it is or whatâs his status. Esteban > On 9 Aug 2017, at 16:41, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi, > > For the JOSS (Journal of Open Source Software) I need to add to a > package documentation the API documentation as an external file > (hopefully in HTML). So I would like to export the source code in a way > that can be used as API documentation. I remember that some API > documentation about Smalltalk/Pharo can be found online, but I don't > know how to produce such documents. Any pointers to explore? > > Cheers, > > Offray > > >

Aug. 9, 2017

API docs as HTML

by Offray Vladimir Luna CÃ¡rdenas

Hi, For the JOSS (Journal of Open Source Software) I need to add to a package documentation the API documentation as an external file (hopefully in HTML). So I would like to export the source code in a way that can be used as API documentation. I remember that some API documentation about Smalltalk/Pharo can be found online, but I don't know how to produce such documents. Any pointers to explore? Cheers, Offray

Aug. 9, 2017