[squeak-dev] squeak plugin in ff 2/3

> Hey,
>
> I'm trying to get Epaati to work in the browser, on the XO eventually,
> and I'm running into two problems:
>
> - In ff3 beta 5 on Linux (Ubuntu 8.04) I can't seem to get ff to
> recognise the squeak plugin. Has anybody got experience with ff3 and
> the plugin, good or bad?
> My setup mirrors the requirements for a ff2 plugin configuration. When
> running npsqueakrun squeak will launch a session. I tested both the
> npsqueak.so from a pretty new sugar-jbuild as well as a version which
> works with ff2 (I know there were problems with the standard squeak
> plugin from squeakland not registering with ff properly (which last
> time I checked (about 3 weeks/a month ago) still was the plugin
> available for download. Should perhaps be updated?)).
>
> - In ff2 I can load our activities from a server, but only if the .pr
> file isn't to big. If it is of moderate size or more, I'm getting
> space-low warnings followed by a crash on project load. Would anybody
> happen to know why this is happening? Is there perhaps some memory
> variable that's easily adjustable?
>
> Thanks,
> /Ties
>

> To answer my own questions,
> first of all, running the squeak installer puts the plugin in
> /usr/lib/mozilla/plugins, which doesn't get picked up, on my setup in
> any case. putting the plugin in tilde/.mozilla/plugins does register
> with ff3. As for the space low message, this is fixed by adjusting
> (taking away) the -mmap startup option in npsqueakrun.
>
> /Ties
>
> On Mon, Jul 14, 2008 at 3:09 PM, Ties Stuij <[hidden email]> wrote:
>> Hey,
>>
>> I'm trying to get Epaati to work in the browser, on the XO  
>> eventually,
>> and I'm running into two problems:
>>
>> - In ff3 beta 5 on Linux (Ubuntu 8.04) I can't seem to get ff to
>> recognise the squeak plugin. Has anybody got experience with ff3 and
>> the plugin, good or bad?
>> My setup mirrors the requirements for a ff2 plugin configuration.  
>> When
>> running npsqueakrun squeak will launch a session. I tested both the
>> npsqueak.so from a pretty new sugar-jbuild as well as a version which
>> works with ff2 (I know there were problems with the standard squeak
>> plugin from squeakland not registering with ff properly (which last
>> time I checked (about 3 weeks/a month ago) still was the plugin
>> available for download. Should perhaps be updated?)).
>>
>> - In ff2 I can load our activities from a server, but only if the .pr
>> file isn't to big. If it is of moderate size or more, I'm getting
>> space-low warnings followed by a crash on project load. Would anybody
>> happen to know why this is happening? Is there perhaps some memory
>> variable that's easily adjustable?
>>
>> Thanks,
>> /Ties
>>
>

> On Wednesday 16 Jul 2008 1:08:03 am Bert Freudenberg wrote:
>> Does Ubuntu have a designated location for browser plugins?
>
> The convention is to put files like plugins in /usr/lib/<app>/
> plugins/. But
> that is just that - a convention and that can change with time and  
> across
> distros. 64-bit systems use /usr/lib64/<app>/plugins. Upstream  
> installers
> like npsqueakregister should take in a list of paths for placing  
> links to
> squeak plugin. This allows distro packagers or sysadmins to override  
> them
> (with say /opt/<app>/plugins) without having to patch scripts.
>
> I can make a patch for npsqueakregister if there is any interest.
>
> If no path list is given,
> globbing /usr/{local/lib,lib}/{firefox,mozilla,netscape}/plugins is  
> a safe
> bet.
>
> Subbu

>
> Am 15.07.2008 um 22:22 schrieb K. K. Subramaniam:
>
>> On Wednesday 16 Jul 2008 1:08:03 am Bert Freudenberg wrote:
>>> Does Ubuntu have a designated location for browser plugins?
>>
>> The convention is to put files like plugins in
>> /usr/lib/<app>/plugins/. But
>> that is just that - a convention and that can change with time and
>> across
>> distros. 64-bit systems use /usr/lib64/<app>/plugins. Upstream
>> installers
>> like npsqueakregister should take in a list of paths for placing
>> links to
>> squeak plugin. This allows distro packagers or sysadmins to override
>> them
>> (with say /opt/<app>/plugins) without having to patch scripts.
>>
>> I can make a patch for npsqueakregister if there is any interest.
>>
>> If no path list is given,
>> globbing /usr/{local/lib,lib}/{firefox,mozilla,netscape}/plugins is a
>> safe
>> bet.
>>
>> Subbu
>
> Did I ever answer this? Sure, send the patch.
>
> - Bert -
>
>
>
>