On Friday 23 May 2008 22:40, Michael T?nzer wrote:
> Matthew Toseland schrieb:
> > On Friday 23 May 2008 11:38, Matthew Toseland wrote:
> >>> I'm not pushing for any immediate changes, but perhaps being more
> >>> user-friendly regarding the custom FF profile is something to consider
> >>> for 0.7.1?
> >> I'd welcome any suggestions. So far, afaics the options are:
> >> 1) Fix the Firefox bug that causes the profile resetting. -no-remote 
should 
> >> cause it not only to not coalesce with an existing Firefox copy, but also 
> > not 
> >> to write to the default profile. Also find a new skin that works with 
FF3, 
> >> and ideally is a little more stable!
> >> 2) Build something using XULRunner. I believe this is the recommended way 
of 
> >> doing things according to the Firefox devs. They provide a sample browser 
> >> implemented in XUL, but it's *really* minimal, no right-click-go-back for 
> >> example.
> >> 3) Bundle a "portable" browser.
> > 4) Bundle a browser plugin.
> 
> Maybe we can steal some code from this plugin:
> https://nic-nac-project.org/~kaosmos/profileswitcher-en.html
> 
> it's under GPLv3 (source is in the .xpi) and as far as I have tested, it
> doesn't have the bug you described. So we could still provide a
> Firefox-Profile (which isn't used by default) but also ask (in the
> install wizard) to install the plugin. We alter it's behaviour in such a
> way, that it simply provides a "Browse Freenet" button or menu item
> which then loads our custom profile.
> The advantage would be, that the user has to opt-in and that while he's
> in the browser he can easily browse Freenet (no need to switch through
> start menus).

Don't we want the user to be able to browse Freenet (in a customised browser) 
and non-freenet sites at the same time?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20080524/aee001fc/attachment.pgp>

Reply via email to