On Thu, 31 Aug 2000 16:14:50 +0200 (CEST) Bert Freudenberg bert@isg.cs.uni-magdeburg.de wrote:
Some comments, though (this applies to everyone who wants to create Squeaklets):
- You shouldn't use HTTPSocket to get stuff, but (FileStream requestURLStream: 'squeak.3ds')
which asks Netscape to fetch the file. You might also look at the PluginCodeLoader and PluginHTTPRequest stuff.
Bert,
Wouldn't this prevent those squeaklets from being used in Squeak that is *not* in a browser?
Cheers, Bob
On Thu, 31 Aug 2000, Bob Arning wrote:
On Thu, 31 Aug 2000 16:14:50 +0200 (CEST) Bert Freudenberg bert@isg.cs.uni-magdeburg.de wrote:
Some comments, though (this applies to everyone who wants to create Squeaklets):
- You shouldn't use HTTPSocket to get stuff, but (FileStream requestURLStream: 'squeak.3ds')
which asks Netscape to fetch the file. You might also look at the PluginCodeLoader and PluginHTTPRequest stuff.
Bert,
Wouldn't this prevent those squeaklets from being used in Squeak that is *not* in a browser?
Well, Squeaklets are intended to be viewed with a browser. OTOH, there's no definition of a "Squeaklet" yet. For now, it's just some Smalltalk code that is sent around ...
We could make the #requestURLStream switch to normal fetching when running in a stand-alone Squeak, though ...
-- Bert
Bob Arning wrote:
On Thu, 31 Aug 2000 16:14:50 +0200 (CEST) Bert Freudenberg bert@isg.cs.uni-magdeburg.de wrote:
Some comments, though (this applies to everyone who wants to create Squeaklets):
- You shouldn't use HTTPSocket to get stuff, but (FileStream requestURLStream: 'squeak.3ds')
which asks Netscape to fetch the file. You might also look at the PluginCodeLoader and PluginHTTPRequest stuff.
Bert,
Wouldn't this prevent those squeaklets from being used in Squeak that is *not* in a browser?
No, the code falls back to the HTTPSocket get when Squeak is not running inside a browser.
Michael
squeak-dev@lists.squeakfoundation.org
-
Bert Freudenberg -
Bob Arning -
Michael Rueger