| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
While not necessary, since both HTML and XHTML allows for direct UTF-8,
the validator fails on it.
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
XHTML is still the far supperior format. However; Chrome(-like) browsers
Lighthouse feature is worth quite a bit when it comes to ensuring a good
web page, and Lighthouse refuses to work on anything except text/html.
This is my work-around for that.
|
| |
| |
| |
| |
| |
| | |
The old sxml->html-string was always wrong, since smxl->xml doesn't
(necessarily) produce valid HTML. Now we get proper HTML or XHTML,
depending on the `html' parameter.
|
| |
| |
| |
| | |
Finally making the few previous commits worth something.
|
| |
| |
| |
| |
| |
| |
| | |
Since procedures allow direct controll of the output.
Everything worked fine for XML output, but HTML encodes apostrophes as
', which works really bad in script tags.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The doctype declaration is "required" when outputing regular HTML, and
fine when output XHTML.
Also remove the tests of xhtml-doc, since they basically just copied the
deffinition (and stoped working since a procedure can't easily be tested
for equality).
|
| |
| |
| |
| |
| |
| | |
sxml->xml already allows arbitrary strings to be included through
procedures current output port. This adds the same feature to sxml->html
for feature parity.
|
| |
| |
| |
| |
| |
| | |
See future commits for rationale.
This reverts commit 54fc8cf92e9212cc88c824f7b49549160d860657.
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The current rrule-instances requires an event, the new one works
directly on recurrence rules (and dates) meaning that it can be used
independently.
|
|
|
|
|
|
| |
The current rrule-instances requires an event, the new one works
directly on recurrence rules (and dates) meaning that it can be used
independently.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Since everything is properties the repl thread needs to be spawned AFTER
the configuration is loaded.
|
|
|
|
|
|
| |
The old ones where broken since i accidentally removed setVar, instead
of reintrocuding that, I rewrote slider-inputs as web components, which
frees us of having some hacky javascript in the html code.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The out of range exception could never occur, since I aleready limited
the interval to (n % 7) + 1.
|
| |
|
|
|
|
|
| |
Depending an the exact text of an translatable string seems like a bad
idea.
|
| |
|
| |
|
|
|
|
| |
Old sandbox approach always felt like bit of a hack.
|
| |
|
|
|
|
|
| |
Name conflicts are apparently not good. Manual fixup since it's too much
a hassle to undo the merge.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This new setup stores all configurations are parameters. This forces
everything into modules, and ensures that we can't have a module use an
unloaded config. It (unfortunatelly) also causes users to have to
specify namespaces when defining values, but ini-files (and the like)
already does that. Also, there is nothing stopping a new `set-config!'
from being defined which allows un-namespaced operation.
The commit also removes the introspection procedures. They where a bit
weird to begin with, since they only showed loaded fields. And since the
program had no way of properly serializing or deserializing them we
remove them for the time being. They would however be good to
reintroduce together with a proper menu for editing simple
configuration (see Emacs' `custom-set-variables').
|
| |
|
| |
|
|\ |
|