I think this could work quite well within the context of the editor. One problem that needs to be discussed/solved before it can be added has to do with "raster resolution":
the original idea of the editor was to enable pure procedural texture editing (i.e. that the image function can be evaluated at any point and is independent of the output resolution which is already violated by the bitmap pattern). For SVG patterns to work one needs to specify some kind of resolution prior to rendering the texture.
I think the easiest solution would probably be to use and cache the resolution used for the current target output (i.e. when exporting to 512x512 use also 512x512 for the SVG). One problem with this solution is, that filters like for example the warp can magnify/minify almost arbitrarily the input data which leads to artifacts.
As a solution a user parameter that overwrites this resolution heuristic could be provided.
Another thing that needs to be addressed is aliasing/antialiasing when for example using repeats or zooms on the input data.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think this could work quite well within the context of the editor. One problem that needs to be discussed/solved before it can be added has to do with "raster resolution":
the original idea of the editor was to enable pure procedural texture editing (i.e. that the image function can be evaluated at any point and is independent of the output resolution which is already violated by the bitmap pattern). For SVG patterns to work one needs to specify some kind of resolution prior to rendering the texture.
I think the easiest solution would probably be to use and cache the resolution used for the current target output (i.e. when exporting to 512x512 use also 512x512 for the SVG). One problem with this solution is, that filters like for example the warp can magnify/minify almost arbitrarily the input data which leads to artifacts.
As a solution a user parameter that overwrites this resolution heuristic could be provided.
Another thing that needs to be addressed is aliasing/antialiasing when for example using repeats or zooms on the input data.