From: jamos@oboj.net
To: 9front@9front.org
Subject: Netsurf 3.9 for Plan 9 (work in progress)
Date: Thu, 02 Jan 2020 00:02:20 +0200 [thread overview]
Message-ID: <30b184ac47ef349337078b6caee9c0c4@oboj.net> (raw)
Hello everyone,
As some of you know from the 9fans discord channels, I am trying to port
the web browser Netsurf to Plan9 (9front).
My port is still very much work in progress, but I wanted to publish a
first version for the ones that might find it interesting to compile and
run. I started out with the prior work of Jens Staal and AAP that I
found in different contrib directories, but my port is based on the
latest stable version.
My port so far uses the 'framebuffer' driver, which means that the
browser draws in a memory bitmap, than then is copied to a Plan 9 Image
using loadimage(). It does not work to snarf or paste. If I get good
success with the framebuffer frontend, I will try to write a native
frontend for Plan 9 there is already ones for amiga, atari, beos, gtk,
riscos and windows present.
There is a lot of functionality lacking currently, but it is possible to
load local web pages, even if they don't display so nicely. There are
many things to figure out. I have not given fonts any thoughts. It is
little endian (as I commented out the code that checked for endianess).
In reality not so much works, but it compiles and something shows... :-)
There is a lot of README files though, and I am open to all kinds of
input.
You can the source code here:
https://webbkurs.ei.hv.se/~imjam/plan9/netsurf-3.9-2020-01-01.tgz
//Jonas Amoson
Ps. Oh, and the port relies heavily on APE-shit, and being a browser it
also supports a lot of WEB-shit ;-)
next reply other threads:[~2020-01-01 22:02 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 22:02 jamos [this message]
2020-01-01 22:57 ` [9front] " ori
2020-01-02 0:59 ` jamos
2020-01-02 16:45 ` ori
2020-01-03 3:12 ` Kyle Nusbaum
2020-01-03 3:30 ` ori
2020-01-03 20:14 ` Kyle Nusbaum
2020-01-03 21:01 ` ori
2020-01-03 21:35 ` Kyle Nusbaum
2020-01-04 0:22 ` hiro
2020-01-04 10:21 ` Steve Simon
2020-01-04 13:41 ` No rendering of pages (Re: [9front] Netsurf 3.9 for Plan 9 (work in progress)) jamos
2020-01-04 15:49 ` ori
2020-01-04 12:08 ` [9front] Netsurf 3.9 for Plan 9 (work in progress) jamos
2020-01-04 17:14 ` ori
2020-01-04 21:33 ` jamos
2020-01-08 4:23 ` Kyle Nusbaum
2020-01-08 4:25 ` Kyle Nusbaum
2020-01-24 8:09 ` Eli Cohen
2020-01-24 10:09 ` hiro
2020-01-24 18:16 ` Kyle Nusbaum
2020-01-24 18:40 ` jamos
2020-01-25 15:11 ` Eli Cohen
2020-01-26 21:10 ` jamos
2020-01-29 20:42 ` Ori Bernstein
2020-02-03 16:00 ` ori
2020-02-04 20:19 ` Kyle Nusbaum
2020-02-04 20:11 ` ori
2020-02-04 20:29 ` Kyle Nusbaum
2020-01-03 10:39 ` telephil9
2020-01-03 10:44 ` telephil9
2020-01-03 15:07 ` ori
2020-01-03 15:14 ` telephil9
2020-01-03 11:55 ` Steve Simon
2020-01-03 15:08 ` telephil9
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30b184ac47ef349337078b6caee9c0c4@oboj.net \
--to=jamos@oboj.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).