- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Monkey timeout

by Max Leske

> On 18 Nov 2016, at 19:41, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > Anything we can do about the monkey timeout > a CIChangeCaseValidationRule: Timeout (after 0:01:40:00) > +1 This time itâs persistent... > This occurs even shortly after the validation starts. > >

Nov. 21, 2016

Re: [Pharo-dev] Monkey timeout

by Nicolai Hess

2016-11-18 19:41 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > Anything we can do about the monkey timeout > a CIChangeCaseValidationRule: Timeout (after 0:01:40:00) > > This occurs even shortly after the validation starts. > > reboot ?

Nov. 20, 2016

Re: [Pharo-dev] Improving comments cool action

by Nicolai Hess

2016-11-20 22:06 GMT+01:00 stepharo <stepharo(a)free.fr>: > Now we have package comments :) so we should take also advantage of them. >>> >> Stupid question, how exactly does one add package comments ? Can it only >> be done in the latest 6 ? Is it somehow compatible with older versions ? >> >> In latest version you press on a package and comment and you can accept > text. > > Is it somehow compatible with older versions ? > > I do not know. I did not check its implementation. > I imagine that the package comments is stored in the manifest. So it is > probably not displayed but not lost if you load your package in Pharo 50. > > Yes, it is stored as a class side method (#description) on the package manifest class

Nov. 20, 2016

Re: [Pharo-dev] Improving comments cool action

by stepharo

>> Now we have package comments :) so we should take also advantage of them. > Stupid question, how exactly does one add package comments ? Can it only be done in the latest 6 ? Is it somehow compatible with older versions ? > In latest version you press on a package and comment and you can accept text. Is it somehow compatible with older versions ? I do not know. I did not check its implementation. I imagine that the package comments is stored in the manifest. So it is probably not displayed but not lost if you load your package in Pharo 50.

Nov. 20, 2016

Re: [Pharo-dev] STON doesn't produce valid JSON - it shouldn't escape quation mark

by Sven Van Caekenberghe

I committed the following in STON (sthub.com, ss3.gemstone.com & github.com) #bleedingEdge: === Name: STON-Core-SvenVanCaekenberghe.78 Author: SvenVanCaekenberghe Time: 20 November 2016, 7:48:23.799323 pm UUID: ee198da8-80e8-4944-ba9b-dffae331c57c Ancestors: STON-Core-SvenVanCaekenberghe.77 In JSON compatibility mode STON should not encode single quotes. (Thanks Peter UhnÃ¡k for reporting this). Patch STONWriter>>#encodeCharacter: Fix the encoding of forward slash ($/). This was already in the (external) documentation. Patch STONWriter class>>#initializeSTONCharacters - force STONWriter class>>#initialize to change too Fix the representation of Time by adding nanoseconds when there are any. This was already in the (external) documentation. Patch Time>>#stonOn: Adjust unit tests accordingly (esp. STONWriterTests>>#testDoubleQuotedString). Minor comment changes. === Name: STON-Tests-SvenVanCaekenberghe.68 Author: SvenVanCaekenberghe Time: 20 November 2016, 7:48:46.115446 pm UUID: 70402f28-f0e8-44e9-8746-3539c4add09b Ancestors: STON-Tests-SvenVanCaekenberghe.67 In JSON compatibility mode STON should not encode single quotes. (Thanks Peter UhnÃ¡k for reporting this). Patch STONWriter>>#encodeCharacter: Fix the encoding of forward slash ($/). This was already in the (external) documentation. Patch STONWriter class>>#initializeSTONCharacters - force STONWriter class>>#initialize to change too Fix the representation of Time by adding nanoseconds when there are any. This was already in the (external) documentation. Patch Time>>#stonOn: Adjust unit tests accordingly (esp. STONWriterTests>>#testDoubleQuotedString). Minor comment changes. === Now you get NeoJSONReader fromString: (STON toJsonString: 'single='' & double="'). "'single='' & double=""'" STON toString: { Time now. Date today. DateAndTime now }. "'[Time[''19:51:15.452023''],Date[''2016-11-20''],DateAndTime[''2016-11-20T19:51:15.454147+01:00'']]'" STON toString: 'back-slash=\ & forward-slash=/'. "'''back-slash=\\ & forward-slash=\/'''" Sven > On 19 Nov 2016, at 20:56, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Peter, > > You are right, that is a bug. > > STON should be a bit more strict when it is in JSON mode. I'll fix it and let you know. > > Thanks for reporting this issue. > > Sven > >> On 19 Nov 2016, at 17:46, <i.uhnak(a)gmail.com> <i.uhnak(a)gmail.com> wrote: >> >> \â is not a valid JSON escape character, so STONâs JSON ouput is not a valid JSON string. >> >> ston := STON toJsonString: 'element''s'. -> "element\'s" >> neo := NeoJSONWriter toString: 'element''s'. -> "element's" >> >> NeoJSONReader fromString: ston. -> invalid escape character \â >> >> Peter >

Nov. 20, 2016

Re: [Pharo-dev] Improving comments cool action

by Sven Van Caekenberghe

More and better documentation, I am all for it. > On 20 Nov 2016, at 17:26, stepharo <stepharo(a)free.fr> wrote: > > Now we have package comments :) so we should take also advantage of them. Stupid question, how exactly does one add package comments ? Can it only be done in the latest 6 ? Is it somehow compatible with older versions ?

Nov. 20, 2016

Improving comments cool action

by stepharo

Hi guys I would like to see how we could build a concerted action to improve the class and method comments in Pharo. Now we have package comments :) so we should take also advantage of them. I would love that a newbie is highlithed by class comments. So I would like to start to comment key core classes. I'm sure that if we all spend 30 min per week we can really have a huge impact. I was planning to start with collection classes. Now let me know if you want to help. Stef

Nov. 20, 2016

Re: [Pharo-dev] STON doesn't produce valid JSON - it shouldn't escape quation mark

by Sven Van Caekenberghe

Peter, You are right, that is a bug. STON should be a bit more strict when it is in JSON mode. I'll fix it and let you know. Thanks for reporting this issue. Sven > On 19 Nov 2016, at 17:46, <i.uhnak(a)gmail.com> <i.uhnak(a)gmail.com> wrote: > > \â is not a valid JSON escape character, so STONâs JSON ouput is not a valid JSON string. > > ston := STON toJsonString: 'element''s'. -> "element\'s" > neo := NeoJSONWriter toString: 'element''s'. -> "element's" > > NeoJSONReader fromString: ston. -> invalid escape character \â > > Peter

Nov. 19, 2016

STON doesn't produce valid JSON - it shouldn't escape quation mark

by i.uhnak＠gmail.com

\â is not a valid JSON escape character, so STONâs JSON ouput is not a valid JSON string. ston := STON toJsonString: 'element''s'. -> "element\'s" neo := NeoJSONWriter toString: 'element''s'. -> "element's" NeoJSONReader fromString: ston. -> invalid escape character \â Peter

Nov. 19, 2016

Monkey timeout

by Nicolai Hess

Anything we can do about the monkey timeout a CIChangeCaseValidationRule: Timeout (after 0:01:40:00) This occurs even shortly after the validation starts.

Nov. 18, 2016