Project status documentation
by Michael Drake
Hello,
I'd like to update the various project status documents. Please say if
this lot looks OK:
PLAN -- http://netsurf.sourceforge.net/plan
Set Absolute positioning and Lists to "done". I think any outstanding
stuff with them like stacking order or list marker position and stuff
can be treated as bugs, rather than outstanding features.
That would just leave Cookies on the Plan.
TODO-HTML --
http://svn.semichrome.net/*checkout*/trunk/netsurf/Docs/TODO-HTML
Remove Lists and Frames sections. I'm not sure if the form "disabled"
attribute is done yet.
TODO-CSS --
http://svn.semichrome.net/*checkout*/trunk/netsurf/Docs/TODO-CSS
I think list-style and list-style-type are done. I am not sure about
list-style-image.
"static position not implemented" can be removed from position.
PROGRESS -- http://netsurf.sourceforge.net/progress
I'm not sure if
CSS1 - Nearly done
CSS2 - in Progress
HTML4 - Nearly done
are as apt as they once were. Things have come on a long way since
then.
HTTP Auth. is still marked as "In progress". Is it not complete now?
Also, HTTPS says "Nearly done - Doesn't handle invalid certificates
well". That's complete now, isn't it?
I think frames can be changed from "In progress" to "Complete" with
the few remaining issues mentioned in the Notes column.
Lists can be changed to "Nearly done" or maybe "Complete". I'm not
quite sure how much list stuff is unfinished.
Position can be changed so the notes say Fixed positioning is
unimplemented and stacking order is incorrect.
Best regards,
--
Michael Drake (tlsa)
http://www.smoothartist.com/
17 years
- 3
- 3
netsurf-browser.org domain
by Rob Kendrick
Dan's bought this domain, and it's currently pointing at
pike.pepperfish.net.
Also, any visit to www.netsurf-browser.org/foo gets automatically
redirected to netsurf.sourceforge.net/foo
Do we want to keep the domain on Pepperfish's servers? I think myself
and Dan are happy to host the website and its downloads if that's what
people want.
We can also easily set up DNS records, like svn.netsurf-browser.org to
point to svn.semichome.net, of course.
I can also set up some automatic virtual web servers, such that all
that's needed to create a website for foo.netsurf-browser.org is to
create a directory called "foo" in the right place and fill it with
content, so no faffage with the web server is needed and this sort of
thing can "just happen" out of svn.
We've also set up a UNIX shell account and an account on our web-based
config system specifically for NetSurf to separate it all out if things
want to stay this way.
B.
17 years
- 1
- 0
- ← Newer
- 1
- Older →