Re: [Pharo-users] Iceberg is cool!

NorbertHartl wrote > Well done and thank you… You broke the rule!!! We never say anything positive about Iceberg - only complaints - because we want to keep Esteban on his toes ha ha ;) Seriously though, it just keeps getting better and better over a very short time… - Cheers, Sean --

Re: [Pharo-users] Iceberg is cool!

> Am 13.12.2017 um 13:06 schrieb Mariano Martinez Peck : > > Well, I am enjoying it too even if I still would need more features :) > BTW, how can I update a Pharo 6.1 that came with 0.6.2 to 0.6.5 ? Can I > simply run the update script listed here [1] ? > I use

Re: [Pharo-users] Iceberg is cool!

Well, I am enjoying it too even if I still would need more features :) BTW, how can I update a Pharo 6.1 that came with 0.6.2 to 0.6.5 ? Can I simply run the update script listed here [1] ? Thanks in advance [1] https://github.com/pharo-vcs/iceberg#for-pharo-6 On Wed, Dec 13, 2017 at 8:42

[Pharo-users] Iceberg is cool!

I just got back from vacation and prepared a new image to work on the current project. Well, I upgraded iceberg to 0.6.5 and everything works like expected. I can see nicely what my colleagues have done while I was away. I can update everything easily. And most important I can do changes and

Re: [Pharo-users] FLSerialization>>analysisStep too slow?

Thanks Mariano. There is no such method: FLSerializer>>setDebug and FLDebugSerialization class in my 6.1 image. Anyway, my object has an instance variable that save the serialized glamour browser. I deleted that variable, and the saving process became quicker than before. Best regards,

Re: [Pharo-users] Metalinks arguments as Array ?

Ok, i found it digging the mailing list... Working example is in testReifySendArgsAsArray method, where it suffice to use link options: #(argsAsArray). I should try searching in the list before asking...

[Pharo-users] Metalinks arguments as Array ?

Hi, can we somehow provide an array of reifications to a metalink metaobject ? For ex.: link metaObject: [:args| do stuff with args]. link selector: #valueWithArguments:. link arguments: #(object node link receiver sender) So that when the link executes, args in the block would be an

Re: [Pharo-users] Iceberg: Code directory missing

I have a lot of "Clarification" wishe list ofr iceberg :) You cannot imagine it. :) On Tue, Dec 12, 2017 at 10:00 PM, Evan Donahue wrote: > Got it. I didn't realize the code subdirectory wasn't automatically created > by Iceberg if it didn't exist. I deleted the subdirectory

Re: [Pharo-users] Pharo intro talk in spanish

Thanks a lot. I'm starting to learn spanish (you talk too fast but this is fun to hear). Stef On Wed, Dec 13, 2017 at 1:02 AM, Offray Vladimir Luna Cárdenas wrote: > Thanks Rafael! > > Is good to see more content in native languages and support more > diversity and

Re: [Pharo-users] Zinc JSON parsing error handling

> On 13 Dec 2017, at 10:54, Norbert Hartl wrote: > >> >> Am 13.12.2017 um 10:18 schrieb Sven Van Caekenberghe : >> >> >> >>> On 13 Dec 2017, at 10:14, Norbert Hartl wrote: >>> >>> To make your core a little bit more reliable you

Re: [Pharo-users] REST client hints

https://github.com/RMODINRIA-Blockchain Inria = 200 teams 4000 researchers :) On Sun, Dec 10, 2017 at 9:12 AM, Ben Coman wrote: > > > On 10 December 2017 at 15:27, Stephane Ducasse > wrote: >> >> Tx for your report :) >> >>

Re: [Pharo-users] Zinc JSON parsing error handling

> Am 13.12.2017 um 10:18 schrieb Sven Van Caekenberghe : > > > >> On 13 Dec 2017, at 10:14, Norbert Hartl wrote: >> >> To make your core a little bit more reliable you should not catch the >> general error but a NeoJSONParseError. And you need to guard the

Re: [Pharo-users] Zinc JSON parsing error handling

> On 13 Dec 2017, at 10:14, Norbert Hartl wrote: > > To make your core a little bit more reliable you should not catch the general > error but a NeoJSONParseError. And you need to guard the dictionary access. > There is no guarantee you get something back that inlcudes

Re: [Pharo-users] Zinc JSON parsing error handling

To make your core a little bit more reliable you should not catch the general error but a NeoJSONParseError. And you need to guard the dictionary access. There is no guarantee you get something back that inlcudes key success and message. Norbert > Am 13.12.2017 um 09:54 schrieb Ben Coman

Re: [Pharo-users] Zinc JSON parsing error handling

hi Sven, > On 13 Dec 2017, at 07:59, Ben Coman wrote: > > > > > > With... > > Object subclass: #BittrexResponse > > instanceVariableNames: 'success message result' > > classVariableNames: '' > > package: 'Bittrex' > > > > Object subclass:

Re: [Pharo-users] REST client hints

> > > > > On 13 Dec 2017, at 05:37, Ben Coman wrote: > > > > > > Hi Sven (et al), > > > > > > On 10 December 2017 at 11:45, Ben Coman wrote: > > > > > > 3. Finally parse into real objects the nested level holding the data > you really want... > > > > >