Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-27 Thread Stephane Ducasse
Hi stephan not really this is more "not thinking in terms of large dependencies" :) Stef On Mon, Nov 27, 2017 at 12:26 PM, stephan wrote: > On 27-11-17 11:02, Alistair Grant wrote: >> >> As >> we've seen from Pillar and Magritte, the more dependencies the greater >> the maintenance costs and p

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-27 Thread Stephane Ducasse
Hi alistair I understand. If this is a useful combination my practice is to create a separate projects which loads both. For Pillar and Magritte this is another story. When magritte is used deep down in the core of Magritte then you end up being forced to load magritte even when you do not need i

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-27 Thread stephan
On 27-11-17 11:02, Alistair Grant wrote: As we've seen from Pillar and Magritte, the more dependencies the greater the maintenance costs and potential for incompatibility. That conclusion is not supported by the actual code. The maintenance costs for Pillar were high because of ignoring exis

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-27 Thread Alistair Grant
Hi Stef, On 26 November 2017 at 22:39, Stephane Ducasse wrote: > Hi Alistair > > If you want help I can add a baseline that automtically load DataFrame. > Because users should not load by themselves external project. Thanks for the offer, but Pharo-Chrome isn't actually dependent on DataFrame.

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-26 Thread Stephane Ducasse
Hi Alistair If you want help I can add a baseline that automtically load DataFrame. Because users should not load by themselves external project. Stef On Sat, Nov 25, 2017 at 3:57 PM, Sean P. DeNigris wrote: > Alistair Grant wrote >> https://github.com/PolyMathOrg/DataFrame > > Cool, thanks! I

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-25 Thread Sean P. DeNigris
Alistair Grant wrote > https://github.com/PolyMathOrg/DataFrame Cool, thanks! I didn't know about this project. - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-25 Thread Alistair Grant
On 25 November 2017 at 14:18, Sean P. DeNigris wrote: > Alistair Grant wrote >> An updated version is available including: > > Great, thanks! #exampleEvalutionOfJavaScript and #exampleNavigation both > work now. Also, the finance.yahoo.com example from this thread worked until > missing class Data

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-25 Thread Sean P. DeNigris
Alistair Grant wrote > An updated version is available including: Great, thanks! #exampleEvalutionOfJavaScript and #exampleNavigation both work now. Also, the finance.yahoo.com example from this thread worked until missing class DataFrame. IIUC you said this was from a different project, but I did

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-17 Thread Alistair Grant
An updated version is available including: * The fix for spaces in the executable name mentioned below. * Support for Chrome headless mode. * Improved screenshot capture (it now captures the entire page, see the README) * Extended documentation (README.md) Cheers, Alistair On 16 November 2017 a

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-17 Thread Guillermo Polito
Yes, everything is on official's Mariano repository. On Fri, Nov 17, 2017 at 10:29 AM, Stephane Ducasse wrote: > > > > Well, in general the idea is to use the "upstream" project and not > personal > > forks. As far as I am aware of, I have merged all PR from Guille into > > `master`. > > Ok so t

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-17 Thread Stephane Ducasse
> > Well, in general the idea is to use the "upstream" project and not personal > forks. As far as I am aware of, I have merged all PR from Guille into > `master`. Ok so this is good > So unless he has recent commits that were not yet made available via a PR, > then my upstream project should be

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-16 Thread Mariano Martinez Peck
On Thu, Nov 16, 2017 at 6:27 PM, Stephane Ducasse wrote: > Hi mariano > > pay attention to really use the version of guillermo because he was > fixing some bugs. > > Hi Stef, Well, in general the idea is to use the "upstream" project and not personal forks. As far as I am aware of, I have merged

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-16 Thread Stephane Ducasse
Hi mariano pay attention to really use the version of guillermo because he was fixing some bugs. Stef On Wed, Nov 15, 2017 at 3:15 AM, Mariano Martinez Peck wrote: > If this is a problem with OSSubprocess I am happy to help it debug it, but > please share with me the exact steps to reproduce it

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-16 Thread Alistair Grant
Hi Sean & Mariano, On 16 November 2017 at 00:21, Sean P. DeNigris wrote: > Alistair Grant wrote >> I'm glad (and relieved :-)) to hear that it is working. >> >> Would you mind sending the modified command path that you're using so >> I can update the code? (I guess that it is just removing the >

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-16 Thread Mariano Martinez Peck
On Wed, Nov 15, 2017 at 7:04 PM, Sean P. DeNigris wrote: > Alistair Grant wrote > > Sorry for making you do all the work > > Not at all; happy to help. It takes a village! BTW I tracked it down to the > spaces in the command path. IIRC from my OSP hacking days, it probably has > something to do w

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-15 Thread Sean P. DeNigris
Alistair Grant wrote > I'm glad (and relieved :-)) to hear that it is working. > > Would you mind sending the modified command path that you're using so > I can update the code? (I guess that it is just removing the > backspaces, but just in case...). That is correct… OSSUnixSubprocess new

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-15 Thread Alistair Grant
Hi Sean, On 15 November 2017 at 23:04, Sean P. DeNigris wrote: > Alistair Grant wrote >> Sorry for making you do all the work > > Not at all; happy to help. It takes a village! BTW I tracked it down to the > spaces in the command path. IIRC from my OSP hacking days, it probably has > something to

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-15 Thread Sean P. DeNigris
Alistair Grant wrote > Sorry for making you do all the work Not at all; happy to help. It takes a village! BTW I tracked it down to the spaces in the command path. IIRC from my OSP hacking days, it probably has something to do with the path not being run through the shell to interpret the $\s.

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-15 Thread Alistair Grant
Hi Sean, On 15 November 2017 at 10:23, Sean P. DeNigris wrote: > Alistair Grant wrote >> Sorry (and to Offray) for the trouble, but thanks for persevering. > > Not at all! Thanks for updating the library :) > > > Alistair Grant wrote >> Would you mind setting a breakpoint in >> AKGOSProcess>>comm

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-15 Thread Sean P. DeNigris
Alistair Grant wrote > Sorry (and to Offray) for the trouble, but thanks for persevering. Not at all! Thanks for updating the library :) Alistair Grant wrote > Would you mind setting a breakpoint in > AKGOSProcess>>command:arguments:, printing the command and arguments > and making sure that the

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-14 Thread Alistair Grant
Hi Sean, Sorry (and to Offray) for the trouble, but thanks for persevering. On 15 November 2017 at 01:47, Sean P. DeNigris wrote: > Alistair Grant wrote >> This looks like you are using an old (cached?) version. > > Ugh, yes. I just deleted the local clone and let Iceberg reclone. > > Now when I

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-14 Thread Alistair Grant
Hi Offray, On 15 November 2017 at 00:18, Offray Vladimir Luna Cárdenas wrote: > Hi Alistair, > > The example is not working for me. When I run it, a chrome session is > open but nothing happens there, except that my image gets frozen until I > close chrome and then I get this message: "Connection

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-14 Thread Mariano Martinez Peck
If this is a problem with OSSubprocess I am happy to help it debug it, but please share with me the exact steps to reproduce it and which code to look at. And which OS and which Pharo. And it should be 32 bits (OSSubprocess doesn't work on 64 yet) Thanks, On Tue, Nov 14, 2017 at 9:47 PM, Sean P.

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-14 Thread Sean P. DeNigris
Alistair Grant wrote > This looks like you are using an old (cached?) version. Ugh, yes. I just deleted the local clone and let Iceberg reclone. Now when I tried: `GoogleChrome get: 'https://finance.yahoo.com/quote/%5EAXJO/history?p=%5EAXJO'` I got: Error: Error: posix_spawn(), code: 2, d

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-14 Thread Offray Vladimir Luna Cárdenas
The last was a question :-P Is PharoChrome expecting to be logged in to some Google account to work? Cheers, Offray On 14/11/17 18:18, Offray Vladimir Luna Cárdenas wrote: > Hi Alistair, > > The example is not working for me. When I run it, a chrome session is > open but nothing happens there,

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-14 Thread Offray Vladimir Luna Cárdenas
Hi Alistair, The example is not working for me. When I run it, a chrome session is open but nothing happens there, except that my image gets frozen until I close chrome and then I get this message: "ConnectionTimedOut: Cannot connect to 127.0.0.1:9222". What is the expected behavior? PharoChrome e

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-14 Thread Offray Vladimir Luna Cárdenas
OK, the development branch solve this, as shown in http://ws.stfx.eu/O6J4CJ1FZF89. Now I'm getting an unresponsive image until I close Chrome, but I think that was talked in the thread. I'll revise. Cheers, Offray On 14/11/17 17:28, Offray Vladimir Luna Cárdenas wrote: > Hi Alistar, > > I have

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-14 Thread Offray Vladimir Luna Cárdenas
Hi Alistar, I have tried to run the examples, but seems that installation doesn't include all needed package. At the beginning I installed OSUnix and then OSLinuxUbuntu. None of them seems to include "AKGOSProcess", so the "GoogleChrome get: 'http://pharo.org'" example raises: "#command:arguments:

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-14 Thread Alistair Grant
On 14 November 2017 at 19:13, Alistair Grant wrote: > Hi Sean, > > On 14 November 2017 at 19:06, Sean P. DeNigris wrote: >> Alistair Grant wrote >>> I've committed some fixes to the development branch: >> >> Thanks! >> >> I tried your example, but apparently the OSXProcess class, which is >> refe

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-14 Thread Alistair Grant
Hi Sean, On 14 November 2017 at 19:06, Sean P. DeNigris wrote: > Alistair Grant wrote >> I've committed some fixes to the development branch: > > Thanks! > > I tried your example, but apparently the OSXProcess class, which is > referenced in openChromeWith: is missing. Also, no class in the image

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-14 Thread Sean P. DeNigris
Alistair Grant wrote > I've committed some fixes to the development branch: Thanks! I tried your example, but apparently the OSXProcess class, which is referenced in openChromeWith: is missing. Also, no class in the image seems to define #createProcess:, which is sent to OSXProcess there -

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-14 Thread Alistair Grant
I've committed some fixes to the development branch: 1. MacOS hopefully works now (I don't have access to the platform, so can't test it). 2. The development version of Beacon is loaded (which is required for the InMemoryLogger). 3. The README is a tiny bit better. 4. Added #extractTables. As an

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-12 Thread Alistair Grant
Hi Sean, Thanks for your feedback! (responses below) On 12 November 2017 at 18:11, Sean P. DeNigris wrote: > Alistair Grant wrote >> https://github.com/akgrant43/Pharo-Chrome > > Wow, that was a wild ride! Sorry about that. > Lessons learned along the way: > 1. On a Mac, to use the snazzy `

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-12 Thread Stephane Ducasse
Tx and one day we can turn it into another little booklet :) Stef On Sun, Nov 12, 2017 at 3:04 PM, Alistair Grant wrote: > Hi Stef, > > On 12 November 2017 at 14:47, Stephane Ducasse > wrote: >> exampleNavigation >> | chrome page logger | >> logger := InMemoryLogger new. >> logger start. >> ch

[Pharo-users] Pharo-Chrome (was: Soup bug(fix))

2017-11-12 Thread Alistair Grant
Hi Stef, On 12 November 2017 at 14:47, Stephane Ducasse wrote: > exampleNavigation > | chrome page logger | > logger := InMemoryLogger new. > logger start. > chrome := GoogleChrome new > debugOn; > debugSession; > open; > yourself. > page := chrome tabPages first. > page enablePage. > page enable