From: telephil9@gmail.com
To: 9front@9front.org
Cc: telephil9@gmail.com
Subject: netsurf native frontend
Date: Thu, 21 May 2020 17:54:03 +0200 [thread overview]
Message-ID: <592FB65470BC7FE96B27C51B46F47948@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
Hi,
I've just committed the initial release for the netsurf native frontend.
Feature-wise it is almost on par with the framebuffer frontend except for images that are not handled yet.
I tried to make it look and behave like a native application but would like to have some feedback on this.
All code is in the main repository: http://github.com/netsurf-plan9
In order not to mess with the current framebuffer frontend, I created a separate mkfile found in netsurf/mkfile.native.
To build this new frontend, just run mk as usual and then run mk -f mkfile.native in the netsurf directory.
Regards,
Philippe
[-- Attachment #2: ns9_20200521.png --]
[-- Type: image/png, Size: 22624 bytes --]
next reply other threads:[~2020-05-21 15:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 15:54 telephil9 [this message]
2020-05-21 16:06 ` [9front] " hiro
2020-05-21 17:59 ` Romano
2020-07-28 7:11 ` [9front] netsurf native frontend (text_insert: illegal combination FCVTZSDW FCON NONE REG) Romano
2020-07-29 6:08 ` arm64 fails to link when float converted to int (Was Re: [9front] netsurf native frontend (text_insert: illegal combination FCVTZSDW FCON NONE REG)) Romano
2020-08-01 11:43 ` cinap_lenrek
2020-08-01 12:23 ` Anthony Martin
2020-05-21 21:16 ` [9front] netsurf native frontend Dave MacFarlane
2020-05-23 11:03 ` telephil9
2020-05-23 15:42 ` Stanley Lieber
2020-05-23 16:13 ` Stanley Lieber
2020-05-23 4:08 ` kokamoto
2020-05-23 6:13 ` Eli Cohen
2020-05-23 6:18 ` telephil9
2020-05-23 6:37 ` Eli Cohen
2020-05-23 20:10 ` jamos
2020-05-24 0:02 ` kokamoto
2020-05-25 3:51 ` kokamoto
2020-05-24 2:13 ` sl
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=592FB65470BC7FE96B27C51B46F47948@gmail.com \
--to=telephil9@gmail.com \
--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).