- From: Ingar Arntzen via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Mar 2023 20:02:41 +0000
- To: public-webtiming@w3.org
Hi Chris. I like this. It would provide an effective way of implementing certain types of custom converters, especially skew converter and scale converter. I'm not sure how often one would need other transformations than skew and scale though. However, if you do, it would be pretty neat to be able to solve it like this. A few comments: 1. This would be a static transformation. The skew converter in timingsrc v3 supports skew to be reset dynamically, and this feature has been quite useful. This is not an argument against the suggestion though, but rather an argument to keep the the existing skew converter around too. 2. If range is defined for the timing object, this must be taken into account. Presumably, the range must be adjusted too, using the provided custom query function. This way, change events resulting from range violations would still be emitted when expected. 3. I think it would be possible to create a query function that somehow messes up some aspect of expected behavior of the timing object. For instance, a query function should probably be required to be well defined within the range and at least piece-wise continuous. -- GitHub Notification of comment by ingararntzen Please view or discuss this issue at https://github.com/webtiming/timingobject/issues/13#issuecomment-1462694964 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 March 2023 20:02:43 UTC