From mboxrd@z Thu Jan 1 00:00:00 1970 From: errno To: 9fans@9fans.net Date: Sat, 30 Apr 2011 02:48:51 -0700 User-Agent: KMail/1.13.6 (Linux/2.6.38-ARCH; KDE/4.6.2; i686; ; ) References: <9ad5871bf83f37b7e7ed19169d389f6d@quintile.net> In-Reply-To: <9ad5871bf83f37b7e7ed19169d389f6d@quintile.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104300248.51973.errno@cox.net> Subject: Re: [9fans] Compiling 9atom kernel WAS: Re: spaces in filenames Topicbox-Message-UUID: d998054a-ead6-11e9-9d60-3106f5b1d025 On Saturday, April 30, 2011 01:25:53 AM Steve Simon wrote: > First I assume you have used abaco - it is incomplete but its the best > plan9 has at present - without using linuxemu. > I appreciate abaco for what it is, but unfortunately it's not something I can expect to satisfy most users' activities on the web. I still haven't tried a browser through linuxemu though... maybe that'll end up being sufficient. > If you are saying that you are willing to take this on (getting a modern > native plan9 web browser running) I may be able to help in some areas > Excellent - I'm definitely willing to see how far I can get. My little 9 network is currently in the midst of being re-deployed (was going to play around with 9front); when I get it back online (so I have an instance to work from), I'll send you an email - I could definitely use the advice/pointers of someone more experienced. Thanks! > One idea I was considering for several years was trying to get Dillo > running as a fairly compliant browser, initially under an X11 server but > later you might be able to merge the framebuffer backend to dillo (via a > library I cannot remember) and replace it with a library which talks > /dev/draw rather than linux framebuffer. > Interesting... I did spend some time seeking out other, possible more simple, alternatives, dillo for instance - but I came to the spoiled-minded conclusion that to do it right - so that it's not just another "kind-of basically working for a limited subset of use-cases" situation - that it really should use a current and active engine such as webkit (preferable) or gecko. > just some random thoughts. > Thankyou! Cheers