9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: jamos@oboj.net, 9front@9front.org
Subject: Re: [9front] Netsurf 3.9 for Plan 9 (work in progress)
Date: Wed, 1 Jan 2020 14:57:07 -0800	[thread overview]
Message-ID: <1DCB150A539D8B14987387850715D909@eigenstate.org> (raw)
In-Reply-To: <30b184ac47ef349337078b6caee9c0c4@oboj.net>

[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]

> 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.

Well, that's definitely progress -- and I'm definitely interested
in enough browser to get me past captive portals and such.

For me, though -- it builds, and it runs, but the image that 
Well, it builds, at least. But when I try to run it, I get a garbled
image (see attached).

The garbled image doesn't change with respect to window size.

 
> 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 ;-)

[-- Attachment #2: Type: image/png, Size: 8438 bytes --]

  reply	other threads:[~2020-01-01 22:57 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-01 22:02 jamos
2020-01-01 22:57 ` ori [this message]
2020-01-02  0:59   ` [9front] " 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
2020-01-31 10:38 kokamoto
2020-01-31 16:34 ` ori
2020-02-01 23:46 kokamoto
2020-02-02 15:24 ` jamos
2020-02-03  1:31 ` ori
2020-02-03  5:54   ` telephil9
2020-02-03  5:58     ` telephil9
2020-02-03  2:08 kokamoto
2020-02-03  3:03 ` ori
2020-02-03  3:16 ` Kurt H Maier
2020-02-04 23:40 kokamoto
2020-02-04 23:57 ` Kyle Nusbaum
2020-02-04 23:58   ` ori
2020-02-05  1:20     ` Kyle Nusbaum
2020-02-06  7:04   ` ori
2020-02-06  8:16     ` hiro
2020-02-06 10:10       ` Steve Simon
2020-02-06 15:29       ` ori
2020-02-05  2:13 kokamoto
2020-02-05  2:28 ` Kyle Nusbaum
2020-02-05 10:00   ` jamos
2020-02-05 17:44     ` Kyle Nusbaum
2020-02-05 18:40       ` jamos
2020-02-05 18:48         ` Eli Cohen
2020-02-05 19:04           ` Kyle Nusbaum
2020-02-05 19:10           ` ori
2020-02-05 19:06         ` Kyle Nusbaum
2020-02-05 20:17         ` Kyle Nusbaum
2020-02-05 20:56           ` Kyle Nusbaum
2020-02-05  3:10 kokamoto
2020-02-05  3:25 kokamoto
2020-02-05  6:44 kokamoto
2020-02-06  0:08 kokamoto
2020-02-06  0:24 ` Kyle Nusbaum
2020-02-06 11:26   ` jamos
2020-02-06 14:42     ` hiro
2020-02-07 12:04       ` Steve Simon
2020-02-07  3:12 kokamoto
2020-02-08  0:15 kokamoto
2020-02-08  0:19 ` ori

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=1DCB150A539D8B14987387850715D909@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.org \
    --cc=jamos@oboj.net \
    /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).