Setting Up a Server to Handle Squeak Projects
dan at shafermedia.com
Mon May 29 05:48:36 UTC 2006
Thanks, Milan. Very helpful. I see that the server doesn't need to be
aware of the data type of the content because you use an embedded
object in the browser's code to circumvent. I know basically how to
do that, so I'm off to do some trial work now.
On May 28, 2006, at 1:32 AM, Milan Zimmermann wrote:
> A few notes below:
> On 2006 May 28 02:32, Dan Shafer wrote:
>> OK, I downloaded the Squeak plug-in and I seem to be able to
>> access .pr files stored on other sites. But how do I deploy a Squeak
>> project as a plugin? I think the questions I need answered are:
>> 1. What does the server (Apache) need to know in order to serve
>> Squeak projects as files? Anything?
> I am using Kom as Http server (not Apache), and this is the piece
> of HTML that
> works - I guess it piggibacks the .pr file through squeakland. The
> important thing is the href:
> alt=""Squeak"saver" title="Make your own
> style="border: 5px solid ; width: 250px; height: 175px;"></a>
> I suspect it will work on Apache as well, but do not know for sure.
> Perhaps you can start with this, just t test your project works
> etc, and take
> it from there, ask questions , plus more info about the HTTP plugin:
> and this message from Diego I saved:
> And also:
>>> ID="SqueakOCX Control"
>>> WIDTH=1024 HEIGHT=768
>>> ALIGN=center BORDER=2
>> 2. Will detection of the plugin be semi-automatic? I.e., if a user
>> without the plugin tries to download a Squeak project, will he get an
>> error, an ugly binary dump or something meaningful?
> From what I remember, in the life without the plugin in all my
> browsers, if
> done "correctly" it will redirect user to the site where to find
> the plugin.
> If you use the simple version on top, it will do it right.
>> 3. Anything else I need to know about deployment?
> I am sure there is more and people more qualified will comment,
> hopefully the
> above is a start,
More information about the Squeak-dev