> I am wondering about the support of Firefox in our default > SetupEnvironment. Currently it reads: > > export LIBRARY_PATH= > "%A/lib:$HOME/config/lib:/boot/common/lib:/boot/beos/system/lib" > export ADDON_PATH= > "%A/add-ons:$HOME/config/add-ons:/boot/beos/system/add-ons" > > We could change that to: > > export LIBRARY_PATH= > "%A/.:%A/components:%A/lib:$HOME/config/lib:/boot/common/lib:/boot/beos > /system/lib" > export ADDON_PATH= > "%A/.:%A/components:%A/add-ons:$HOME/config/add-ons:/boot/beos/system/ > add-ons" > > ... in order to support Firefox in "native app" mode. Opinions? Tweaking our SetupEnvironment in order to make one single non-native-friendly app to run like a charm sounds quite counter-intuitive to me. Better make this app behave more like any native ones, no? > On the other hand, I would have to prepare a package, where the script has > been removed and firefox-bin renamed to Firefox. In case it works, I might > as well change the package further and move the components into an > "add-ons" subfolder. +1 I like this way better: improve Firefox/BeZilla beos/haiku "nativeness" behavior. Just my .02 cent, as my recent involvement in Haiku is near zero... Sigh. Philippe