I saw that basic networking works under vmware player, so wouldn't it make testing compatibility easier if I would have the ability to download beos applications straight from any page?
As soon as there is a working *free* web browser that can be included with Haiku without licensing restrictions, I assume it will be done.
Right now, FireFox doesn't work properly in Haiku and is actually quite large to include in testing images and Net+ from R5 cannot be distributed legally.
wget is included with Haiku already, you can use it to retrieve files from http/ftp locations.
In my opinion firefox is not the, um, ideal browser *philosophically* for BeOS... The default browser should use Be features like translation kit and duplicates IMO.. Not to forget native widgets.
In my opinion firefox is not the, um, ideal browser *philosophically* for BeOS... The default browser should use Be features like translation kit and duplicates IMO.. Not to forget native widgets.
All fine and good - but in the grand scheme of things, it's got the most capable renderer and javascript engine of any current BeOS browser. This is very important in the current internet age.
As mentioned countless times, an embeddable gecko or KHTML rendering engine in a native shell would be awesome for BeOS/Haiku - but as of yet, there haven't been any concrete options that have surfaced.
In my opinion firefox is not the, um, ideal browser *philosophically* for BeOS... The default browser should use Be features like translation kit and duplicates IMO.. Not to forget native widgets.
All fine and good - but in the grand scheme of things, it's got the most capable renderer and javascript engine of any current BeOS browser. This is very important in the current internet age.
As mentioned countless times, an embeddable gecko or KHTML rendering engine in a native shell would be awesome for BeOS/Haiku - but as of yet, there haven't been any concrete options that have surfaced.
Personally I find Firefox as the best option and not because of what umccullough said but because Firefox being open source can, in time, be personalized for haiku. There is already a haiku theme that can be used if it's decided to use from now on Firefox in each build.
Talking about personalization, look at KDE's Konqueror and Gnome's Epiphany which use just like Firefox the Gecko engine.
So first we can use Firefox with just the theme changed for the current builds and after the R1 release focus on a personalized browser but still keep the same internals as starting base.
As mentioned countless times, an embeddable gecko or KHTML rendering engine in a native shell would be awesome for BeOS/Haiku - but as of yet, there haven't been any concrete options that have surfaced.
I agree with you Urias! That would be the best solution.
Firefox is the most complete web browser out there for alternative OSes ( like Linux, BSD, BeOS, etc. and even Windows too though they also have IE7 ).
But having said that. Firefox is somewhat sluggish on BeOS because it is a posix port and on the heavy side.
Ideally it would be nice to have a web browser that is: natively coded or somewhat natively optimized and more of a mid weight version.
This all depends on the developers and how much time they want to spend but a short term solution could be to bring up to date NetOptimist and add more features to it to satisfy most users ( making it a fast, light to mid weight internet browser ).
Also, BeZilla team could work on making Firefox more native to Haiku. I believe they're doing this with Firefox 3.
Talking about personalization, look at KDE's Konqueror and Gnome's Epiphany which use just like Firefox the Gecko engine.
Konqueror uses KHTML...
In any case, this is what I was referring to - a native shell using just the rendering engine: either Gecko or KHTML.
For OS X there's Safari (KHTML->WebCore derivative) and Camino (Gecko-based) - both native shells on a portable rendering engine.
"Theming" Firefox is a sub-optimal solution. Firefox is great because of all the XUL-based extensions, but it *is* heavy. Granted, I use it exclusively on my Windows machines now.
Yea I understand that there are practical constraints relating to firefox, which is why I said *philosophically*. Especially with AJAX'y stuff everywhere, it sounds crazy to think of a totally new engine. I was having gecko in mind cuz I remember reading something that the major problem with using KHTML is that the QT will have to be stripped from it..
The nirvana project is interesting for the future but for the moment any open source browser would do just fine because it will only be intended for testing and presentation. It's purpose would be just to keep someone who is testing haiku for the first a longer time in it. If every nightly build has an internet browser people will spent at least more time in HAIKU, searching for a page or just playing around, maybe noticing other features. Like this maybe their interest in the os will grow.
OS without web-browser is not an OS today. But I think that default OS browser shouldn't be this massive customizable monster (like FFox). It should just let u do maybe basic browsing and get u to stuff that u want to download. Get u to FFox, and from there on u can maybe use that, if u want to. Also it is needed to read all sorts of documentation on local machine. On my linux-box i use FFox to surf the net, but documentation i read with dillo. And if i need just quickly to find something from net i use dillo or links2. No tabs, no sessions, no extensions, themes etc...
Maybe porting Dillo or Links2 would be a good thing to Haiku? They are light, open and do the basic job. Links2 browses the web better but Dillo has better interface, imho.
Btw. i think there's already a port of links2 to Beos, maybe that could be used as a starting point? Just add nicer GUi...
Ryan Leavengood is working on a WebKit port for Haiku through a bounty that has already raised over $600.
Indeed, thanks for mentioning it Dennis. I hadn't seen this thread here, but after reading the various posts I think in the end you will all be satisfied with my solution.
A modern browser is a complicated beast, and it is not a viable option to create your own renderer and JavaScript engine these days, at least not with nice open source alternatives like Gecko and WebKit. I feel WebKit is more in the spirit of Haiku which is why I decided to port it. I made this decision before the bounty was created, but the bounty is a great bonus.
I will take a look at Themis and NetOptimist to see what might be useful in their code, but in general I plan to create a new browser. Most of the work will be in porting WebKit, but once that is done a lot of what makes a browser will be there.
I plan to keep the browser fairly lightweight and simple, but at the same time good enough to replace Firefox for most purposes. Firefox is a great browser and I've used it since it was called Phoenix, but it seems with each release it gets more bloated and slow. After playing with WebKit-based browsers which are very fast and lightweight feeling, going back to Firefox can feel unpleasant.
I will try to provide updates on Haikuware as I make progress on the port, and I hope to deliver a nice new browser by this Christmas. I hope you all can be patient as I have a day job like most Haiku volunteer developers :)
I am actually really excited for this port that Ryan is working on. I have also been using Firefox since about version 0.9 and while it is a great browser for windows and Linux I agree with Ryan that it's not really "in the spirit of Haiku". Hopefully this new project will produce something that others will eventually take an interest in and maybe include it in Haiku as its native browser (of course this is just me so the folks with the appropriate authority will make the call).
Thanks for the hard work Ryan and if you ever need a tester or if there is anything I can do to help let me know.
I'm going to vote a little web browser that could. It is for Debian Linux (used in Fluxbuntu 7.10) and its very small.
Kazehakase is the name of this 1.3MB browser, it may not be like Firefox or Opera with all its nice features. I must say I was surprised with what it could do. It's still below a 1.0 version and the programmer is Japanese. check it out at:
Something lighter than Firefox already exists as an optional package: Links
Not really the same thing. :-)
I meant a graphical ( GUI ) browser not a text based one.
I played with Links back in the late 90s in University. Never liked it. I'd say that Links ( text based ) does not compare to a graphical web browser. And very few people would want to use Links.
I have to agree with tonestone57. It's not really the same thing and personally, I would not really want to use a text based browser on a regular basis. However, it is useful for testing when there isn't much else available.
Firefox does work better than it once did. Has there been any work done lately on the WebKit port and browser that Ryan Leavengood started on as part of a bounty a while back?
I meant a graphical ( GUI ) browser not a text based one.
Wow, picky. I certainly wasn't suggesting that Links was to be a native replacement for Net+
It supports graphics, it supports CLICKABLE links... damn, what else could you ask for...
The *LAST* thing Haiku needs is a million weird little apps that all do the same thing, but slightly different. There's already an OS you can use for that.
Anyhow, why squabble over what browser should be written for Haiku at this point.
I only posted to let people know that mmu_man *is* porting over NetSurf ( currently works on Zeta ). So, there would be another web browser available to Haiku users. I wasn't advocating to make another browser - just informing users here of what is happening.
Urias, you're the one that got all out of control because I said I didn't like Links. And I'm sure many others don't either.
And by your logic. We have VLC, so why should anyone create a mediaplayer, soundplayer, etc. Reason is, because we all like to have choice. If you don't like choice then good for you - go use Links & be happy. But don't tell people we have Links ( text based ), Firefox ( heavy/bloated ), Opera ( old, outdated ), Net+ ( old, outdated ) and that we don't need another, newer graphical browser. In my previous post, I didn't suggest or push for any browser in particular - just updating this post with new info on what is taking place.
I'm not sure why you lost it like that. I wasn't pushing to port NetSurf, it is something already happening on its own. What is your problem??? If you like Links then great for you. Just Because YOU Like It Doesn't Mean Everyone Else Should Too!
And you had no reason to rudely attack me! I found what you wrote offensive and negative. I wonder if this is how you respond to your co-workers at work when they don't agree with you? Or maybe that is the type of person you are? ( I found your attitude to be condescending and negative ).
***DISCUSSIONS ARE ABOUT CONTRIBUTING INFORMATION, AND POINTS OF VIEW AND NOT ABOUT ATTACKING ( OR PUTTING DOWN ) OTHER PEOPLE BECAUSE THEY SIMPLY DON'T AGREE WITH YOU ON THE TOPIC.***
Urias, you're the one that got all out of control because I said I didn't like Links. And I'm sure many others don't either.
Out of control... you think my comments were out of control? jeez... clearly my communication style is overwhelming. (I'll try not to use the word "damn" next time - clearly that was over the top).
Quote:
And you had no reason to rudely attack me! I found what you wrote offensive and negative.
It was hardly that - please take your sensitive chip-on-shoulder somewhere else.
Has there been any work done lately on the WebKit port and browser that Ryan Leavengood started on as part of a bounty a while back?
Work has been stalled on this for a while, for no other reason than I have not had time to work on it, and no one else has helped since January. But help at this point might not be good anyhow because there is a lot to be done to update the port to the latest WebKit code. Our port is over 6 months out of date compared to WebKit Top of Trunk (ToT.)
Once I update the port and finally get our code into the WebKit repository I will start working on the browser shell, probably piecing together the code from some of the other MIT-licensed BeOS browsers written in the past (with proper attribution of course.)
I can't say when we will have something usable, but hopefully within a month or two. Obviously the browser won't be at the level of Firefox, Opera or Safari (with all the wanted features and stability) for some time. I am realistic at least ;)
I don't think there is a big hurry since Haiku isn't even at Alpha yet. But obviously a good browser is even useful and wanted now, so I would like to get it going soon.
Comments
Re: Internet browser part of every build
As soon as there is a working *free* web browser that can be included with Haiku without licensing restrictions, I assume it will be done.
Right now, FireFox doesn't work properly in Haiku and is actually quite large to include in testing images and Net+ from R5 cannot be distributed legally.
wget is included with Haiku already, you can use it to retrieve files from http/ftp locations.
Re: Internet browser part of every build
Ask and you shall receive.
NetOptimist ( a Net+ clone ). Not finished, but somewhere near halfway done and should work fairly alright.
At least a good starting point.
More information here:
http://netoptimist.sourceforge.net/
Source Code is available here ( MIT License? ):
http://sourceforge.net/projects/netoptimist/
And the Bebits page too.
http://bebits.com/app/2071
I'm sure Haiku could use the source from here and work on it further. Should be good enough to even use now.
Re: Internet browser part of every build
I remember hearing about NetOptimist YEARS ago ... but I never tried it, and completely forgot about it :)
I'll take a look myself in a few days.
Re: Internet browser part of every build
In my opinion firefox is not the, um, ideal browser *philosophically* for BeOS... The default browser should use Be features like translation kit and duplicates IMO.. Not to forget native widgets.
Re: Internet browser part of every build
In my opinion firefox is not the, um, ideal browser *philosophically* for BeOS... The default browser should use Be features like translation kit and duplicates IMO.. Not to forget native widgets.
All fine and good - but in the grand scheme of things, it's got the most capable renderer and javascript engine of any current BeOS browser. This is very important in the current internet age.
As mentioned countless times, an embeddable gecko or KHTML rendering engine in a native shell would be awesome for BeOS/Haiku - but as of yet, there haven't been any concrete options that have surfaced.
Re: Internet browser part of every build
In my opinion firefox is not the, um, ideal browser *philosophically* for BeOS... The default browser should use Be features like translation kit and duplicates IMO.. Not to forget native widgets.
All fine and good - but in the grand scheme of things, it's got the most capable renderer and javascript engine of any current BeOS browser. This is very important in the current internet age.
As mentioned countless times, an embeddable gecko or KHTML rendering engine in a native shell would be awesome for BeOS/Haiku - but as of yet, there haven't been any concrete options that have surfaced.
Personally I find Firefox as the best option and not because of what umccullough said but because Firefox being open source can, in time, be personalized for haiku. There is already a haiku theme that can be used if it's decided to use from now on Firefox in each build.
Talking about personalization, look at KDE's Konqueror and Gnome's Epiphany which use just like Firefox the Gecko engine.
So first we can use Firefox with just the theme changed for the current builds and after the R1 release focus on a personalized browser but still keep the same internals as starting base.
Re: Internet browser part of every build
As mentioned countless times, an embeddable gecko or KHTML rendering engine in a native shell would be awesome for BeOS/Haiku - but as of yet, there haven't been any concrete options that have surfaced.
I agree with you Urias! That would be the best solution.
Firefox is the most complete web browser out there for alternative OSes ( like Linux, BSD, BeOS, etc. and even Windows too though they also have IE7 ).
But having said that. Firefox is somewhat sluggish on BeOS because it is a posix port and on the heavy side.
Ideally it would be nice to have a web browser that is: natively coded or somewhat natively optimized and more of a mid weight version.
This all depends on the developers and how much time they want to spend but a short term solution could be to bring up to date NetOptimist and add more features to it to satisfy most users ( making it a fast, light to mid weight internet browser ).
Also, BeZilla team could work on making Firefox more native to Haiku. I believe they're doing this with Firefox 3.
Re: Internet browser part of every build
Talking about personalization, look at KDE's Konqueror and Gnome's Epiphany which use just like Firefox the Gecko engine.
Konqueror uses KHTML...
In any case, this is what I was referring to - a native shell using just the rendering engine: either Gecko or KHTML.
For OS X there's Safari (KHTML->WebCore derivative) and Camino (Gecko-based) - both native shells on a portable rendering engine.
"Theming" Firefox is a sub-optimal solution. Firefox is great because of all the XUL-based extensions, but it *is* heavy. Granted, I use it exclusively on my Windows machines now.
Re: Internet browser part of every build
Yea I understand that there are practical constraints relating to firefox, which is why I said *philosophically*. Especially with AJAX'y stuff everywhere, it sounds crazy to think of a totally new engine. I was having gecko in mind cuz I remember reading something that the major problem with using KHTML is that the QT will have to be stripped from it..
Re: Internet browser part of every build
What would be great is; to port over Apple's implementation of KHTML (WebCore and JavaScriptCore) and meld a Net+ like interface to the frontend.
Re: Internet browser part of every build
What would be great is; to port over Apple's implementation of KHTML (WebCore and JavaScriptCore) and meld a Net+ like interface to the frontend.
That would basically summarize the "Nirvana" project - but it hasn't been terribly active:
http://nirvana.berlios.de/
Re: Internet browser part of every build
The nirvana project is interesting for the future but for the moment any open source browser would do just fine because it will only be intended for testing and presentation. It's purpose would be just to keep someone who is testing haiku for the first a longer time in it. If every nightly build has an internet browser people will spent at least more time in HAIKU, searching for a page or just playing around, maybe noticing other features. Like this maybe their interest in the os will grow.
Re: Internet browser part of every build
How about Themis? It's not that active now :(
http://themis.sourceforge.net/faqs.php
(http://themis.svn.sourceforge.net/viewvc/themis/trunk/themis/)
But as part of Haiku-OS no but if some one made a distro yes.
What would be nice thoue are building tools etc and a bigger partion than 100 MB
Re: Internet browser part of every build
OS without web-browser is not an OS today. But I think that default OS browser shouldn't be this massive customizable monster (like FFox). It should just let u do maybe basic browsing and get u to stuff that u want to download. Get u to FFox, and from there on u can maybe use that, if u want to. Also it is needed to read all sorts of documentation on local machine. On my linux-box i use FFox to surf the net, but documentation i read with dillo. And if i need just quickly to find something from net i use dillo or links2. No tabs, no sessions, no extensions, themes etc...
Maybe porting Dillo or Links2 would be a good thing to Haiku? They are light, open and do the basic job. Links2 browses the web better but Dillo has better interface, imho.
Btw. i think there's already a port of links2 to Beos, maybe that could be used as a starting point? Just add nicer GUi...
http://links.twibright.com/
http://www.dillo.org/
~~~~~~~~
I like your Christ, I do not like your Christians. Your Christians are so unlike your Christ.
Mahatma Gandhi
Re: Internet browser part of every build
Ryan Leavengood is working on a WebKit port for Haiku through a bounty that has already raised over $600.
http://www.haikuware.com/index.php?option=com_content&task=view&id=54&It...
http://www.saveload.org - Alternative OS News
http://www.nerfd.net - Nerfd Technologies
http://www.nerfd.biz - Online Software & OS Store
Re: Internet browser part of every build
Ryan Leavengood is working on a WebKit port for Haiku through a bounty that has already raised over $600.
Indeed, thanks for mentioning it Dennis. I hadn't seen this thread here, but after reading the various posts I think in the end you will all be satisfied with my solution.
A modern browser is a complicated beast, and it is not a viable option to create your own renderer and JavaScript engine these days, at least not with nice open source alternatives like Gecko and WebKit. I feel WebKit is more in the spirit of Haiku which is why I decided to port it. I made this decision before the bounty was created, but the bounty is a great bonus.
I will take a look at Themis and NetOptimist to see what might be useful in their code, but in general I plan to create a new browser. Most of the work will be in porting WebKit, but once that is done a lot of what makes a browser will be there.
I plan to keep the browser fairly lightweight and simple, but at the same time good enough to replace Firefox for most purposes. Firefox is a great browser and I've used it since it was called Phoenix, but it seems with each release it gets more bloated and slow. After playing with WebKit-based browsers which are very fast and lightweight feeling, going back to Firefox can feel unpleasant.
I will try to provide updates on Haikuware as I make progress on the port, and I hope to deliver a nice new browser by this Christmas. I hope you all can be patient as I have a day job like most Haiku volunteer developers :)
Regards,
Ryan Leavengood
Re: Internet browser part of every build
I am actually really excited for this port that Ryan is working on. I have also been using Firefox since about version 0.9 and while it is a great browser for windows and Linux I agree with Ryan that it's not really "in the spirit of Haiku". Hopefully this new project will produce something that others will eventually take an interest in and maybe include it in Haiku as its native browser (of course this is just me so the folks with the appropriate authority will make the call).
Thanks for the hard work Ryan and if you ever need a tester or if there is anything I can do to help let me know.
PS the bounty is over $750 now. :) :) :)
Cheers!
http://www.saveload.org - Alternative OS News
http://www.nerfd.net - Nerfd Technologies
http://www.nerfd.biz - Online Software & OS Store
Re: Internet browser part of every build
I'm going to vote a little web browser that could. It is for Debian Linux (used in Fluxbuntu 7.10) and its very small.
Kazehakase is the name of this 1.3MB browser, it may not be like Firefox or Opera with all its nice features. I must say I was surprised with what it could do. It's still below a 1.0 version and the programmer is Japanese. check it out at:
http://kazehakase.sourceforge.jp/
Re: Internet browser part of every build
There is a port in the works by mmu_man for NetSurf. See here:
http://joomla.iscomputeron.com/index.php?option=com_content&task=view&id...
NetSurf screenshots:
http://www.netsurf-browser.org/about/screenshots/
It'll be nice to have something lighter than Firefox to use for basic web browsing.
Re: Internet browser part of every build
It'll be nice to have something lighter than Firefox to use for basic web browsing.
Something lighter than Firefox already exists as an optional package: Links
It's quite usable... should give it a try.
Re: Internet browser part of every build
Something lighter than Firefox already exists as an optional package: Links
Not really the same thing. :-)
I meant a graphical ( GUI ) browser not a text based one.
I played with Links back in the late 90s in University. Never liked it. I'd say that Links ( text based ) does not compare to a graphical web browser. And very few people would want to use Links.
Re: Internet browser part of every build
I have to agree with tonestone57. It's not really the same thing and personally, I would not really want to use a text based browser on a regular basis. However, it is useful for testing when there isn't much else available.
Firefox does work better than it once did. Has there been any work done lately on the WebKit port and browser that Ryan Leavengood started on as part of a bounty a while back?
Re: Internet browser part of every build
I meant a graphical ( GUI ) browser not a text based one.
Wow, picky. I certainly wasn't suggesting that Links was to be a native replacement for Net+
It supports graphics, it supports CLICKABLE links... damn, what else could you ask for...
The *LAST* thing Haiku needs is a million weird little apps that all do the same thing, but slightly different. There's already an OS you can use for that.
Anyhow, why squabble over what browser should be written for Haiku at this point.
Re: Internet browser part of every build
I only posted to let people know that mmu_man *is* porting over NetSurf ( currently works on Zeta ). So, there would be another web browser available to Haiku users. I wasn't advocating to make another browser - just informing users here of what is happening.
Urias, you're the one that got all out of control because I said I didn't like Links. And I'm sure many others don't either.
And by your logic. We have VLC, so why should anyone create a mediaplayer, soundplayer, etc. Reason is, because we all like to have choice. If you don't like choice then good for you - go use Links & be happy. But don't tell people we have Links ( text based ), Firefox ( heavy/bloated ), Opera ( old, outdated ), Net+ ( old, outdated ) and that we don't need another, newer graphical browser. In my previous post, I didn't suggest or push for any browser in particular - just updating this post with new info on what is taking place.
I'm not sure why you lost it like that. I wasn't pushing to port NetSurf, it is something already happening on its own. What is your problem??? If you like Links then great for you. Just Because YOU Like It Doesn't Mean Everyone Else Should Too!
And you had no reason to rudely attack me! I found what you wrote offensive and negative. I wonder if this is how you respond to your co-workers at work when they don't agree with you? Or maybe that is the type of person you are? ( I found your attitude to be condescending and negative ).
***DISCUSSIONS ARE ABOUT CONTRIBUTING INFORMATION, AND POINTS OF VIEW AND NOT ABOUT ATTACKING ( OR PUTTING DOWN ) OTHER PEOPLE BECAUSE THEY SIMPLY DON'T AGREE WITH YOU ON THE TOPIC.***
Re: Internet browser part of every build
Urias, you're the one that got all out of control because I said I didn't like Links. And I'm sure many others don't either.
Out of control... you think my comments were out of control? jeez... clearly my communication style is overwhelming. (I'll try not to use the word "damn" next time - clearly that was over the top).
And you had no reason to rudely attack me! I found what you wrote offensive and negative.
It was hardly that - please take your sensitive chip-on-shoulder somewhere else.
Re: Internet browser part of every build
Has there been any work done lately on the WebKit port and browser that Ryan Leavengood started on as part of a bounty a while back?
Work has been stalled on this for a while, for no other reason than I have not had time to work on it, and no one else has helped since January. But help at this point might not be good anyhow because there is a lot to be done to update the port to the latest WebKit code. Our port is over 6 months out of date compared to WebKit Top of Trunk (ToT.)
Once I update the port and finally get our code into the WebKit repository I will start working on the browser shell, probably piecing together the code from some of the other MIT-licensed BeOS browsers written in the past (with proper attribution of course.)
I can't say when we will have something usable, but hopefully within a month or two. Obviously the browser won't be at the level of Firefox, Opera or Safari (with all the wanted features and stability) for some time. I am realistic at least ;)
I don't think there is a big hurry since Haiku isn't even at Alpha yet. But obviously a good browser is even useful and wanted now, so I would like to get it going soon.