On Saturday 31 May 2008 14:17, Michael Tänzer wrote: > Matthew Toseland schrieb: > > On Sunday 25 May 2008 18:42, Michael Tänzer wrote: > >> Matthew Toseland schrieb: > >>> 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? > >>> > >> Yes we would still have the two profiles method, the user has two > >> windows open, one with the Freenet profile and one with his default one. > >> We probably don't want Freenet and usual webpages in one window, because > >> it leads to having to use the same profile (I don't think you can do two > >> profiles in one window) which would affect both, performance and privacy. > >> The advantage of the button method is, that the user knows there where > >> adjustments done to his browser (because he had to confirm the install > >> of the plugin in Firefox), we provide a shortcut to the Freenet profile > >> (no hangling through menus) and it doesn't have the bug, that Firefox > >> uses the Freenet profile as the default if you close the default before > >> you close the Freenet profile (at least I haven't experienced it up > >> until now). > > > > So you can switch profiles on a per-window basis? > > > > Well, if you select another profile in the menu (or in our case click on > the "Browse Freenet" button) you will be asked whether you want to close > the current profile/window (you can also set a default in the settings > and you will not be asked, in our case setting the default to not > closing the current window might be reasonable) and then another window > with the new profile comes up. > So you can't switch the profile of the current window but you can open > another one with the selected profile. > Well, if it doesn't change the default profile, this might be an option...
pgpxqPDkYPM4D.pgp
Description: PGP signature
_______________________________________________ Devl mailing list [email protected] http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
