snes_rocks wrote:Assuming that the Haiku browser will be implemented as a special BView, how will developers control it? I would assume that the basic BHtmlView would be created by passing a basic HTML page, in a really large string, to the constructor or similar. However, how would a developer pass externally linked files, like CSS stylesheets and Javascript snippets? For most things, it would probably be possible to just make a single file HTML, such as for help pages, but most Internet web pages aren't made like that.
So how would this BHtmlView be passed external files?
--Walter Huf--
Yay, a SANE POST.
I would have some sort of simple API, where the component is given a URL/Filename, or some sort of file handle. Then component then goes off and retrives/parses/rendered that file, and downloads all other required files into a cache - and similarly parsing/rendering them too when appropriately designated by the main file’s parser.
One of my biggest goals is to write a Web Browser, and a layout engine is a huge step in the right direction. I have been planning (As in thinking about, and sketching some designs) of making one for almost 6 months (Give or take a bit).
My two biggest problems are procrastination and a lack of a Be OS. I am unable to compile Haiku (Or BeOS applications) on Windows or FreeBSD, and i am unable to run BeOS R5 on my main computer (With or without BONE). BeOS does run on my laptop, but it has no means of communication from the outside world - It’s USB is busted, it has no supported ethernet (It has a PCMCIA Card, that i’ve never gotten to work), and it doesn’t have a CD Burner. Also, i can’t afford Zeta 1.1.
I am slowly trying to get Haiku to compile on FreeBSD (I’ve built the kernel, but the current problem is the kernel.so wont link).
But anyway, as soon as i can i will start to develop so sort of BWebView. (Not BHtmlView, which in my view is redundant since it’s outdated and should be shunned upon).
This is how KHTML Looks (It’s a bit complex IMHO):
http://developer.kde.org/documentation/library/3.4-api/khtml/html/classKHTMLPart.html
And KHTML’s site:
http://khtml.info/wiki/index.php?title=Main_Page
noisetonepause wrote:Two points relating to the last few posts:
- Firefox is a bit crap
- I don’t think this community should hold any delusions of breaking the Windows monopoly over the next few years!
Since we’re not really here to take over the world or make money, I say we focus on building the best darn desktop OS around instead of pandering to a potential user base by relying on the familiar second or third best (if it was possible to port MS Office and IE, should we?). The way I see it, making that OS involves making an incredible web browser that feels well integrated and usable. Firefox isn’t and won’t ever be because it has to be cross platform and support plug ins, themes and what not. I find I end up using Net+ 95% of the time because it doesn’t feel like an app, it’s a natural extension of the rest of the interface (like StyledEdit, BeMail and People are). I can close the last Net+ window and then remember that I needed to do something else and five seconds later I’ll be back online looking at the page… but woe be unto him who closes the last Firefox tab! FF is a clunky beast of an app and far too hungry and complex for what a browser should do: display web pages.
Keep it elegant and keep it light is what I say.
-Paws
Keeping it elegant and light – Is what i agree with. KHTML or a native layout engine is the way to go. Gecko isn’t.
Oh and BTW: Haiku wont have that large a user base to start with, but it will grow many times faster then Linux or *BSD. People want an alternative to Windows they can trust – Let’s make one safe, elegant and easy to use desktop alternative.
- but I’m mostly a windows user ATM.