From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx.sdf.org ([205.166.94.20]) by ewsd; Fri Jan 3 15:14:22 EST 2020 Received: from [192.168.0.16] (c-98-212-152-230.hsd1.il.comcast.net [98.212.152.230]) (authenticated (0 bits)) by mx.sdf.org (8.15.2/8.14.5) with ESMTPSA id 003KEEsk015015 (using TLSv1.2 with cipher AES128-GCM-SHA256 (128 bits) verified NO); Fri, 3 Jan 2020 20:14:15 GMT Date: Fri, 03 Jan 2020 14:14:10 -0600 User-Agent: K-9 Mail for Android In-Reply-To: <62F1AEE13F2976E71E26F15E96FE7576@eigenstate.org> References: <62F1AEE13F2976E71E26F15E96FE7576@eigenstate.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9front] Netsurf 3.9 for Plan 9 (work in progress) To: 9front@9front.org, ori@eigenstate.org, jamos@oboj.net From: Kyle Nusbaum Message-ID: List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: hosting singleton element optimizer A shared repo would be nice=2E=20 My attempt at using webfs has hit a snag, which is that webfs does not exp= ose the http response header in any way, as far as I can tell=2E=20 I have it partially working in that it is getting and returning webpage da= ta, but netsurf wants the full response header=2E=20 I think webfs is not the right solution for this=2E It is not the general-= purpose http service I thought it was=2E For this purpose, it has several i= ssues=2E It provides no access to the raw header bytes=2E We could still us= e it as a hacky solution if we could reassemble the http header, but webfs = mangles header names when creating the header files and leaves out cookies= =2E=20 However, since netsurf seems to do all the parsing of the response except = separating header from body, and delivers the request URL and post data in = pre-packaged form, I think it's probably easier to just use a raw /net/tcp = connection=2E On January 2, 2020 9:30:50 PM CST, ori@eigenstate=2Eorg wrote: >> Forgive me for any duplicates=2E I mistakenly sent a copy of this >> mail with HTML=2E >>=20 >> This work is neat! >>=20 >> With Ori's changes I see the interface rendered=2E >>=20 >> I think the mouse handling is using absolute coordinates, because >> the address bar only works if I position the window in the upper left >> corner of my screen=2E >>=20 >> I can't get the program to actually render anything, even file:/// >> resources, but I can see them getting fetched=2E >>=20 >> I get CSSBase displayed at the bottom of the screen, seeming to >> correspond to the NSERROR_CSS_BASE error, but I can't figure out why >> that's happening=2E I'm guessing that's why nothing is rendered, but >> that may be a faulty assumption=2E > >I also haven't seen them render, but I got it to show the ui before >I had to run out the door, so I didn't try very hard=2E=20 > >> The fetcher interface looks pretty straightforward and I think it >> shouldn't be too difficult to write a webfs fetcher=2E I think I will >> try that in my spare time=2E >>=20 > >Cool=2E > >If we're going to have multiple people hacking on this, it >probably makes sense to set up a git repository=2E > >It'd be best to use upstream and fork a plan9 branch, so we can >merge their changes and start upstreaming our local diffs more >easily=2E -- Kyle