I went through the forum and heard a lot of things about which browser (mostly mozilla) should be used as the default for ROS.
Just my idea, but I think that we should use a modified version of the Mozilla ActiveX control instead with a dummy browser placed on top. There are 3 reasons why I think that this (even though it may be more difficult) is probably the best choice in the long run.
-Programs that require IE will instead be redirected to use Mozilla's rendering engine instead -The dummy browser could store it's bookmarks in a similar manner to the way IE does adding to the startbutton/bookmarks compatibility -Still promotes OSS
Firebird and Mozilla are great and all, but if there isn't compatability with the myriads of programs that want to call IE for some reason or another ROS will be slower to be adopted
I also agree with this,
We should take Firebird (since its only the browser (not mail, IRC, composer, etc.) and its faster than IE) and add in the ActiveX control plug in (which you can get at: http://www.iol.ie/~locka/mozilla/plugin.htm) and also make a COM wrapper for the Gecko rendering engine, between those two we should have a full replacement to IE for the OS. I think that there was some Netscape employees working on making a COM wrapper for Mozilla, but I can't remember the website, and development seemed to be pretty inactive, but its better than starting from scratch.
David Dunn wrote:
I went through the forum and heard a lot of things about which browser (mostly mozilla) should be used as the default for ROS.
Just my idea, but I think that we should use a modified version of the Mozilla ActiveX control instead with a dummy browser placed on top. There are 3 reasons why I think that this (even though it may be more difficult) is probably the best choice in the long run.
-Programs that require IE will instead be redirected to use Mozilla's rendering engine instead -The dummy browser could store it's bookmarks in a similar manner to the way IE does adding to the startbutton/bookmarks compatibility -Still promotes OSS
Firebird and Mozilla are great and all, but if there isn't compatability with the myriads of programs that want to call IE for some reason or another ROS will be slower to be adopted _______________________________________________ ros-general mailing list ros-general@reactos.com http://reactos.com/mailman/listinfo/ros-general
I agree, but I thing that it would be better to develope a new Browser From Scratch, parhaps based on Gecko rendering Engine...
Well I was thinking maybe some interaction with the Mozilla group would draw more OSS Developer's attention to ReactOS, increasing the chances that some of them will simply put the parts needed by ReactOS directly into the official releases, it also increases the chances that they will write some of that code for us ;-)
João Jerónimo Barata de Oliveira wrote:
I agree, but I thing that it would be better to develope a new Browser From Scratch, parhaps based on Gecko rendering Engine... _______________________________________________ ros-general mailing list ros-general@reactos.com http://reactos.com/mailman/listinfo/ros-general
I agree, but I thing that it would be better to develope a new Browser From Scratch, parhaps based on Gecko rendering Engine...
hang on, ie has been identifying itself as mozilla for yaers now. couldn't we just drop ie in to reactos and let it continue to identify itself as mozilla ;)
les
I thought IE was based on NCSA Mosaic ? Or is Mozilla based on this also ?
Rgs Ian
-----Original Message----- From: ros-general-bounces@reactos.com [mailto:ros-general-bounces@reactos.com]On Behalf Of ros@xzite.fsnet.co.uk Sent: Friday, 6 February 2004 9:59 am To: ros-general@reactos.com Subject: Re: [ros-general] Browsers
I agree, but I thing that it would be better to develope a
new Browser
From Scratch, parhaps based on Gecko rendering Engine...
hang on, ie has been identifying itself as mozilla for yaers now. couldn't we just drop ie in to reactos and let it continue to identify itself as mozilla ;)
les
ros-general mailing list ros-general@reactos.com http://reactos.com/mailman/listinfo/ros-general
On Thu, 2004-02-05 at 17:15, Ian McLean wrote:
I thought IE was based on NCSA Mosaic ? Or is Mozilla based on this also ?
"Mozilla" == "Mosaic" (original browser) + "Godzilla" (famous monster, look at the old logo). Mozilla came from Mosaic, plus some stuff.
-Vizzini
Rgs Ian
-----Original Message----- From: ros-general-bounces@reactos.com [mailto:ros-general-bounces@reactos.com]On Behalf Of ros@xzite.fsnet.co.uk Sent: Friday, 6 February 2004 9:59 am To: ros-general@reactos.com Subject: Re: [ros-general] Browsers
I agree, but I thing that it would be better to develope a
new Browser
From Scratch, parhaps based on Gecko rendering Engine...
hang on, ie has been identifying itself as mozilla for yaers now. couldn't we just drop ie in to reactos and let it continue to identify itself as mozilla ;)
les
ros-general mailing list ros-general@reactos.com http://reactos.com/mailman/listinfo/ros-general
ros-general mailing list ros-general@reactos.com http://reactos.com/mailman/listinfo/ros-general
On Thu, 5 Feb 2004, Vizzini wrote:
On Thu, 2004-02-05 at 17:15, Ian McLean wrote:
I thought IE was based on NCSA Mosaic ? Or is Mozilla based on this also ?
Actually, I think IE is based on the Spyglass browser, which is probably only a distant cousin at this point to Mosaic.
BTW: Has anybody considered that the BSD TCP stack may be easier to port to ReactOS? I work with another open-source operating system called eCos, and it uses the BSD networking stack but its design is not like a traditional UNIX kernel.
Perhaps this might be an easier path. I think the BSD stacks were designed to be ported more easily than the Linux one. I guess the things we would need are:
* TDI "glue" * NDIS "glue" * A wrapper for a memory pool to allow the mbuf allocator to run. (we could just tie the mbuf allocator to the non-paged pool?)
Another cool thing would be to port OpenPF from the OpenBSD project to ReactOS. Its an excellent packet filter and designed to work with the OpenBSD stack as well.
But I really do think that ReactOS needs to get a working TCP stack before people worry too much about what browser to use.
L8r, Mark G.
Actually, I think IE is based on the Spyglass browser, which is probably only a distant cousin at this point to Mosaic.
Have a look at IE's help menu.
BTW: Has anybody considered that the BSD TCP stack may be easier to port to ReactOS? I work with another open-source operating system called eCos, and it uses the BSD networking stack but its design is not like a traditional UNIX kernel.
Actually NT's stack is said to be taken from BSD.