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

2017-08-09 Thread 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 thi

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

2017-08-09 Thread 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 wrote: > > > On Wed, Aug 2, 2017 at 12:55 PM, Stephane Ducasse > wrote: >> >> Hi martin

[Pharo-users] Checking in on source/dependency management

2017-08-09 Thread 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

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

2017-08-09 Thread Herby Vojčík
Esteban A. Maringolo wrote: 2017-08-08 17:49 GMT-03:00 Esteban Lorenzano: 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:

Re: [Pharo-users] API docs as HTML

2017-08-09 Thread 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

Re: [Pharo-users] API docs as HTML

2017-08-09 Thread Esteban Lorenzano
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 hi

[Pharo-users] API docs as HTML

2017-08-09 Thread 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 Smalltal

[Pharo-users] Adding the checksum of a file to another (was Re: Problems verifying the cryptographic signature of a file.)

2017-08-09 Thread Offray Vladimir Luna Cárdenas
Hi, After talking with Peter at discord, I think that my question is clearer. I have two procedures. One that writes a file ( GrafoscopioNotebook>>saveToFile: ) and other that returns the SHA1 checksum of that file ( GrafoscopioNotebook>>checksum ). What I would like to do is to add the checksum

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

2017-08-09 Thread Esteban A. Maringolo
2017-08-08 17:49 GMT-03:00 Esteban Lorenzano : > 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, exten

Re: [Pharo-users] gtInspector override default select behavior

2017-08-09 Thread Andrei Chis
On Mon, Aug 7, 2017 at 11:11 PM, Evan Donahue wrote: > Perfect. > > Do you know if these methods are systematically documented anywhere? I feel > like if I understood Glamour better these things might be more obvious, but > I can never manage to infer the gtInspector calls from the Glamour docs.

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

2017-08-09 Thread Henrik Johansen
> On 8 Aug 2017, at 22:39 , Herby Vojčík wrote: > > Hello! > > I've got this portion in my delegate: > > requestPayload ifNotNil: [ uuidKeys do: [ :each | > requestPayload at: each ifPresent: [ :s | > requestPayload at: each put: (UUID fromString: s) ] ] ]. >

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

2017-08-09 Thread PBKResearch
Sean One extra point. You may need to post-process the parse to get what you want. In the 'restricted' line, if you don't have a #gen then 'gen negate' will have succeeded and will generate its own node in the parse - in your example of ' Paul' as input it will be $P. Assuming you don't want this