On December 23, 2004 02:41 am, Ned Konz wrote:
> On Wednesday 22 December 2004 8:57 pm, Milan Zimmermann wrote:
> > Hi Scott,
> >
<<snip>>
> > A related question that you or someone may be able to answer: Is there a
> > way, using the "object" tag, to force the plugin to download and use "my
> > image" (to which the project then would be loaded) as opposed to the
> > "default Browser Plugin image"? Not that I would want to polute people's
> > WebBrowser plugins with incompatible images, but it would be an
> > interesting exercise.
>
> I suspect that this wouldn't be too hard; you'd have to change the type in
> the EMBED tag from "application/x-squeak-source" to something else that
> would be associated with some specific version of the Squeak VM (possibly
> custom-built for your application) and "my image".
>
> And another Squeak plugin would have to be installed, with "my image" in
> the right place, and this plugin would have to register itself as a handler
> for the appropriate types.
>
> But since the plugin itself identifies the types that it's responsible for
> handling, and since these are hard-coded in the Squeak plugin, you might
> have to compile your own npsqueak (the Squeak plugin):
>
> $ strings ~/.mozilla/plugins/npsqueak.so | grep application
> application/x-squeak-source:sts:Squeak
> source;application/x-squeak-object:sqo:Squeak
> object;application/x-squeak-project:pr:Squeak project

Ned, Thanks for elluminating and thorough explananation - as always.  I may 
give it a try one day ,although i should really be spending time learning the 
Smalltalk environment and squeak instead. Appreciate you taking time on this,
Milan