Hi everyone,
Fabio recently found some primitive which got us curious: StandardFileStream>>#primBrowserReady. After some investigation it turns out that there are a number of primitives, methods, and classes (e.g. PluginHTTPDownloadRequest) related to running Squeak as a Browser Plugin. Is this currently supported? If not I would suggest dropping support by removing the correpsonding code.
Bests, Patrick
Hi Patrick,
Tim has recently removed a large chunk of the browser plugin support (HTTPClient), so I'm fairly sure FileStreams can be cleaned up as well.
Levente
On Mon, 18 Mar 2019, patrick.rein@hpi.uni-potsdam.de wrote:
Hi everyone,
Fabio recently found some primitive which got us curious: StandardFileStream>>#primBrowserReady. After some investigation it turns out that there are a number of primitives, methods, and classes (e.g. PluginHTTPDownloadRequest) related to running Squeak as a Browser Plugin. Is this currently supported? If not I would suggest dropping support by removing the correpsonding code.
Bests, Patrick
On Mon, Mar 18, 2019 at 8:02 AM patrick.rein@hpi.uni-potsdam.de wrote:
Hi everyone,
Fabio recently found some primitive which got us curious: StandardFileStream>>#primBrowserReady. After some investigation it turns out that there are a number of primitives, methods, and classes (e.g. PluginHTTPDownloadRequest) related to running Squeak as a Browser Plugin. Is this currently supported? If not I would suggest dropping support by removing the correpsonding code.
I'd say it's time to remove that code, since browsers have pretty much dropped support for plugins.
- Bert -
squeak-dev@lists.squeakfoundation.org
-
Bert Freudenberg -
Levente Uzonyi -
patrick.rein＠hpi.uni-potsdam.de