Hi Richard,

Op vr 14 jun. 2019 om 12:58 schreef Richard O'Keefe <raoknz@gmail.com>:
There was a thread about this two years ago.

Mmmm. Sounds not like a ready to use solution at all.
Given the fact that I am a Pharo n00b it wouldn't be an easy way to go I guess.

There is Scamper for Squeak,��https://github.com/HPI-SWA-Teaching/Scamper
It used to come standard in Squeak.�� When I knew it, it couldn't quite
handle HTML 3.2.�� I imagine it was removed from Squeak (and SqueakMap)
because it was quite impractical to keep up with the rapid changes in
the web.�� It would be cruel to say that some browser engineers never
saw a feature they didn't like; the truth often hurts.

Same "problem" here I guess?
��
There is already something called tODE, which apparently can make Pharo
tools visible in browser windows.�� That may be a better way to go.

This one? https://github.com/dalehenrich/tode/blob/master/repository/Tode-Client-Pharo.package/monticello.meta/version
And what do you mean with "Pharo tools" here?

...

We already have the tools needed to talk to WebKit; there is very
little benefit to the Pharo team from pouring vast resources into
duplicating what already exists.����

Of course, I agree!
Would you be so kind to point me to some docs about this?

May I conclude that *maybe* "tODE" and "the tools needed to talk to WebKit" are the best ways to achieve my goal(s)?
But, between the lines I read that it would be a rough way (for me at least), which would be a bit too rough for me as aa Pharo n00b.

In C# I can do this literally in a few hours, given the fact that ready made components exist.��
So, maybe I'd better stick with that for this project and try my hands on a bit easier and smaller Pharo projects :-)

Anyway, I really appreciate the help!

Many thx!
�� /Arie