| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|
|
|
|
|
|
| |
This handles each instance of a recurring event as its own unique event,
which allows us to properly send it to the frontend. It's currently not
possible to submit the repeating events back, but that is probably a
underlying problem.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This sepparates popup-elements from their tabbed contents, allowing
clearer sepparations of concerns, along with easier adding and removing
of tabs to the tabset!
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously popups were driven through some CSS hacks, which used labels
with specific positioning, and z-index changes. This never really
worked, and led the rest of the tree to be unmanagable. This commit
replaces that system with a simpler one, which is being driven by
javascript.
This also allowed a much simpler tree, which allowed us to
- make the popups rezisable (with a resize anchor)
- move the window handle to above (configurable)
- Add and remove tabs without having manually reflow where all labels
are
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Previously css rules for each calendar (governing color) where handled
through CSS classes. This however had the problem that all calendar
names needed to be mapped unto valid classnames, and it brought some
problems with updating it.
This change places the calendar information in the dataset.calendar
attribute. It's still base64 encoded, so special characters don't need
escaping, and XML doesn't trip up.
|
| |
|
|
|
|
|
|
| |
It caused tests to crash, since it requires that all components have
parents (which is obviously false for root components), and that all
those parents have a NAME field.
|
|
|
|
|
|
| |
As noted in the fidd, our simple filter-sorted-stream on event-overlaps?
missbehaves in some edge cases. The new system "should" work *fingers
crossed*.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Chromium can't handle JavaScript-modules in XHTML-document [1]. The
workaround is to use a javascript bundler. Here we start depending on
browserify. I evaluated both that and webpack, and browserify seemed to
work marginally better with typescript.
Unfortunately this also makes us depend on npm, where we unfortunately
already are bloatet...
$ ls static/node_modules | wc -l
174
[1]: https://bugs.chromium.org/p/chromium/issues/detail?id=717643
|
| |
|
| |
|
|\ |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changing the error to a returnu allows a partial namespace change map,
which can sometimes be usefull (and should hopefully not lead to any
issues here).
Changing assoc-ref to assoc allows the removal of namespaces, since
assoc-ref can't differentiate between a match with #f in its cdr, and no
match.
(assoc-ref '((a . #f)) 'a) ⇒ #f
(assoc-ref '((a . #f)) 'b) ⇒ #f
|
| |
|
| |
|
|
|
|
|
|
| |
I have no idea why the byday case was commented out while implementing
xcal output. Either way it's now fixed, and should hopefully stay fixed
with some tests.
|
|
|
|
|
|
| |
Since not all zero-length events are at midnight/doesn't have a time
component, they are now placed on the correct position of each day, with
a dummy-length of 1 hour.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Like the diff mentions; appending strings leads to a huge number of
allocations and deallocations, killing performance in the GC for large
strings.
String ports on the other hand say nothing about how the work
internally, allowing Guile to have efficient C code which completely
bypasses the GC (this was briefly checked in Guile's source code, commit
118ee0c50ba90ea7ad7ff1fd2a212bbbb7a66d99 (3.0.7 + a few commits).
The approximate speed increase is at least two orders of magnitude, if
not three.
|