At least for gecko, there will be a libbeosembedgecko.so library , that any app can utilize. It justs a matter of getting ito work properly that's been giving me grief.
As usual, any help whatsoever is more than appreciated, welcomed, and possibly worshipped :)
At least for gecko, there will be a libbeosembedgecko.so library , that any app can utilize. It justs a matter of getting ito work properly that's been giving me grief.
As usual, any help whatsoever is more than appreciated, welcomed, and possibly worshipped :)
I think khtml would be cool, but gecko is probably more easily ported.
I'm pretty confident that we can get Gecko running quite soon. I've learned some of the pitfalls working on the native app patch which should help embedding.
Maybe I should do some work on getting embedding to run.
If someone has the time and energy: The more the merrier 8)
It's really a nice app. Tiny (2.3 MB all the sources, binary 350 KB), fast, but still in heavy development. I tryed to compile it at BeOS R5.0.3, it will not build with old gcc, although it starts well. Well, I'll have a look ...
As I just mentioned in another thread, Dillo is a great, lightweight, tiny browser, but if your intention is to build a full featured browser around it, I believe you're barking up the wrong tree. Its not designed in a way that would easily facillitate this.
If you're just looking for something lightweight and efficient, Dillo is indeed a great choice.
hate to dredge up old threads about this - but here's some inspiration right?
Considering all the effort and writing done to write threads about developing a native browser, I have to wonder how far a browser would be if the effort was placed in coding instead.
Please don't get into this. It's not constructive. Anyone could be told to code instead of posting to forums. This goes for this post, your post and everyone elses too. Discussion is healthy (mostly).
hate to dredge up old threads about this - but here's some inspiration right?
Considering all the effort and writing done to write threads about developing a native browser, I have to wonder how far a browser would be if the effort was placed in coding instead.
Of course - but don't underestimate the power of discussion - you might be suprised at how a little bit of discussion can spark someone into trying something different and finding a solution to previous problems.
I don't feel I'm "coder enough" to work on an embedded gecko rendering widget or a native browser - otherwise I'd take a shot at it in my spare time too... but in the meantime, I certainly am capable of discussing it.
Please don't get into this. It's not constructive. Anyone could be told to code instead of posting to forums. This goes for this post, your post and everyone elses too. Discussion is healthy (mostly).
umccullough wrote:
Of course - but don't underestimate the power of discussion - you might be suprised at how a little bit of discussion can spark someone into trying something different and finding a solution to previous problems.
Sorry, apparently I shouldn't think out loud. :oops: It wasn't meant as a personal attack against anyone. Probably feeling guilty since I hadn't done any coding lately at that point. I was actually kicking myself in the rear with that one. (It worked, at least for a little bit.)
And just for the record, I think it can be seen that I do like discussions.
Comments
browser kit?
first we need to get one of the rendering engines , Gecko , KHTML, or WebCore embeddable in BeOS ... check out my reply at the bottom of page 1 http://haiku-os.org/forums/viewtopic.php?t=19&start=0
At least for gecko, there will be a libbeosembedgecko.so library , that any app can utilize. It justs a matter of getting ito work properly that's been giving me grief.
As usual, any help whatsoever is more than appreciated, welcomed, and possibly worshipped :)
browser kit?
I think khtml would be cool, but gecko is probably more easily ported.
browser kit?
I'm pretty confident that we can get Gecko running quite soon. I've learned some of the pitfalls working on the native app patch which should help embedding.
Maybe I should do some work on getting embedding to run.
browser kit?
There seem to be a project for this on BeClan:
http://www.beclan.org/os_projects.php
BeOS Gecko Embedding Implementation.
Project URL: http://www.mmmgoodpc.com/beos/embedgecko/
Contact matt madia
Licence Mozilla Public Licence
Maby smart to have a look at this before reinventing the wheel..
Or, wait.. that's what HAIKU is all about.. reinvent that wheel! :D
browser kit?
Guess what mmadia is working on :P
I'm helping out to try and get it to a usable state.
browser kit?
Ah! Then it is ALL good! :)
browser kit?
Somebody once posted a suggestion on The Green Board that we should try Dillo as a (lightweight) Net+ replacement.
Kev
browser kit?
ugh
browser kit?
If someone has the time and energy: The more the merrier 8)
browser kit?
It's really a nice app. Tiny (2.3 MB all the sources, binary 350 KB), fast, but still in heavy development. I tryed to compile it at BeOS R5.0.3, it will not build with old gcc, although it starts well. Well, I'll have a look ...
browser kit?
As I just mentioned in another thread, Dillo is a great, lightweight, tiny browser, but if your intention is to build a full featured browser around it, I believe you're barking up the wrong tree. Its not designed in a way that would easily facillitate this.
If you're just looking for something lightweight and efficient, Dillo is indeed a great choice.
browser kit?
hate to dredge up old threads about this - but here's some inspiration right?
http://www.skyos.org/?q=node/539
browser kit?
I'm stuck in windows until my wifi-card has usable drivers or Haiku's network stack is done. So right now it's not so much motivation.
browser kit?
For BHtmlView/native browser/rendering engines/etc -
Reference the previous *long* (forum record) running thread here:
http://haiku-os.org/forums/viewtopic.php?t=412
Personally, I believe the Nirvana project using KHTML is the way to go.
http://nirvana.berlios.de/
browser kit?
Please don't get into this. It's not constructive. Anyone could be told to code instead of posting to forums. This goes for this post, your post and everyone elses too. Discussion is healthy (mostly).
browser kit?
Of course - but don't underestimate the power of discussion - you might be suprised at how a little bit of discussion can spark someone into trying something different and finding a solution to previous problems.
I don't feel I'm "coder enough" to work on an embedded gecko rendering widget or a native browser - otherwise I'd take a shot at it in my spare time too... but in the meantime, I certainly am capable of discussing it.
browser kit?
Sorry, apparently I shouldn't think out loud. :oops: It wasn't meant as a personal attack against anyone. Probably feeling guilty since I hadn't done any coding lately at that point. I was actually kicking myself in the rear with that one. (It worked, at least for a little bit.)
And just for the record, I think it can be seen that I do like discussions.