Gitweb links:
...log
http://git.netsurf-browser.org/netsurf-wiki.git/shortlog/0ba7a47505bf986f8352e6e6363c9c1c4c059f87
...commit
http://git.netsurf-browser.org/netsurf-wiki.git/commit/0ba7a47505bf986f8352e6e6363c9c1c4c059f87
...tree
http://git.netsurf-browser.org/netsurf-wiki.git/tree/0ba7a47505bf986f8352e6e6363c9c1c4c059f87
The branch, master has been updated
via 0ba7a47505bf986f8352e6e6363c9c1c4c059f87 (commit)
from 8fc4263abc997f5b4ec91068fbb8270f73d3362f (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commitdiff
http://git.netsurf-browser.org/netsurf-wiki.git/commit/?id=0ba7a47505bf986f8352e6e6363c9c1c4c059f87
commit 0ba7a47505bf986f8352e6e6363c9c1c4c059f87
Author: Daniel Silverstone <[email protected]>
Commit: Daniel Silverstone <[email protected]>
(dev-weekends): Add initial Nov 2022
Signed-off-by: Daniel Silverstone <[email protected]>
diff --git a/developer-weekend/nov-2022.mdwn b/developer-weekend/nov-2022.mdwn
new file mode 100644
index 0000000..83b5433
--- /dev/null
+++ b/developer-weekend/nov-2022.mdwn
@@ -0,0 +1,82 @@
+[[!meta title="Developer Weekend (Nov 2022)"]]
+[[!meta author="NetSurf Developers"]]
+[[!meta date="2022-11-26 09:00:00"]]
+
+[[!toc]]
+
+Attendees
+=========
+
+* Michael Drake
+* Vincent Sanders
+* Daniel Silverstone
+
+Outstanding work (from 2020)
+===========================
+
+* Calc
+
+Activity
+========
+
+Mostly individual activity here
+
+Michael
+-------
+
+* Worked with Daniel on CSS `calc()` support in LibCSS.
+
+Daniel
+------
+
+* Worked with Michael on CSS `calc()` support in LibCSS.
+
+Vince
+-----
+
+* Provided assists on `calc()` support
+* Worked on warnings etc. exposed by more modern gcc
+
+Notes
+=====
+
+Thoughts around `calc()`
+------------------------
+
+(Copied from 2020 for now)
+
+> Currently the `tlsa/calc` branch contains our work-to-date
+
+Remaining work
+
+> Thought:
+>
+> In theory we could make the calculation bytecode be stored as a lwc_string,
which means we already have mechanisms for deduplication, identity checking,
etc. in libcss.
+
+1. Maybe update generator to construct valid/invalid UNIT types for each
property as a table for use later.
+ * This would involve repeating the validation expressions present in
`LENGTH_UNIT:()` in `properties.gen` or perhaps reworking that bit too.
+ * This is probably an array, indexed by property, whose values are a
bitfield of permitted unit types.
+ * **Done**: This was done after the hack weekend in [parse: properties:
Add property-specific unit class
masks](http://source.netsurf-browser.org/libcss.git/commit/?h=tlsa/calc&id=e2b4077eed0ad778847cd7b17406e8bf8b61a4ae).
+2. Implementing the cascade
+ * Mostly in the common code.
+ * Should be able to type-check here (property-specific part).
+ * In theory type-check could happen in the parser, but once `var()` gets
involved it'll have to be in the cascade, so we may as well put it here from
the start.
+3. Reworking the computed style to have a calc section
+ * By this, we mean that the computed styles should have a representation
which means "Use calculation N" in the current packed content, and then in the
less compact struct we can have calculation bytecode for each unique
calculation needed to support the style.
+ * Also consider how this impacts computed style internment / sharing.
+4. Rework API for computed styles to support client functions so that calc can
run
+ * This is were we implement doing the calculation.
+ * May need care in the case of invalid results in calc
+ * May permit simplification of things like percentage units.
+ * Maybe the context structure should carry simple values like available
width/height viewport width/height, etc. But have a callback for things like
relative font sizes etc.
+ * Probably change so all widths emerge from libcss in px.
+5. Write selection tests involving `calc()`
+ * Will involve fixing `dump_computed.h` to the new API
+
+
+After all that, NetSurf needs updating to the new API, which should simplify
the CSS client code in NetSurf quite a bit.
+
+Next time
+=========
+
+* Undecided.
-----------------------------------------------------------------------
Summary of changes:
developer-weekend/{oct-2020.mdwn => nov-2022.mdwn} | 22 +++++++-------------
1 file changed, 8 insertions(+), 14 deletions(-)
copy developer-weekend/{oct-2020.mdwn => nov-2022.mdwn} (84%)
diff --git a/developer-weekend/oct-2020.mdwn b/developer-weekend/nov-2022.mdwn
similarity index 84%
copy from developer-weekend/oct-2020.mdwn
copy to developer-weekend/nov-2022.mdwn
index 32ddc0a..83b5433 100644
--- a/developer-weekend/oct-2020.mdwn
+++ b/developer-weekend/nov-2022.mdwn
@@ -1,6 +1,6 @@
-[[!meta title="Developer Weekend (Oct 2020)"]]
+[[!meta title="Developer Weekend (Nov 2022)"]]
[[!meta author="NetSurf Developers"]]
-[[!meta date="2020-10-22 09:00:00"]]
+[[!meta date="2022-11-26 09:00:00"]]
[[!toc]]
@@ -11,15 +11,10 @@ Attendees
* Vincent Sanders
* Daniel Silverstone
-Outstanding work (from May)
+Outstanding work (from 2020)
===========================
-* General
- - Forms cleanup.
-* Text layout
- - Continue implementing.
-
-Still outstanding after October developer weekend.
+* Calc
Activity
========
@@ -35,15 +30,12 @@ Daniel
------
* Worked with Michael on CSS `calc()` support in LibCSS.
-* Fixed GTK path plotter translation table. (Fixes svgtiny rendering offset.)
-* Fixed LibDOM fuzz testing issue.
-* Fixed various crashes from the long internet tests.
Vince
-----
-* Added support to LibSVGTiny for paths using arcs.
-* Added a chart renderer to NetSurf.
+* Provided assists on `calc()` support
+* Worked on warnings etc. exposed by more modern gcc
Notes
=====
@@ -51,6 +43,8 @@ Notes
Thoughts around `calc()`
------------------------
+(Copied from 2020 for now)
+
> Currently the `tlsa/calc` branch contains our work-to-date
Remaining work
--
NetSurf Developer Wiki Backing Store
_______________________________________________
netsurf-commits mailing list -- [email protected]
To unsubscribe send an email to [email protected]
