Spaces:
Runtime error
Add explanation about the what the options mean
Firstly, I love this!!! It would work perfectly upstream from a task I had in mind, so excited :party_blob: ๐
In the demo;
There are a lot of options in the "Path Adding Scheduler" part.
adding some simple explanation about what they mean would be better.
"add [1, 1, 1, 1, 1] total 5 paths one by one" I get that [1, 1, 1, 1, 1]=len 5 etc but what does it mean in
a regular demo user should be able to understand how to use the demo to better understand the results; without having to refer to reading the paper details. (which I'm sure is great, and I will definitely read)
Additionally to better demonstrate the output:
image output re-rasterizes the image making the whole vectorization demonstration hard to see. can output multiple images; one per layer. (as done in paper's figures)
also maybe better to print the svg as an html element, would make it possible to see how the image got layered&vectorized using the dev tools inspect tool.
Firstly, I love this!!! It would work perfectly upstream from a task I had in mind, so excited :party_blob: ๐
In the demo;
There are a lot of options in the "Path Adding Scheduler" part.
adding some simple explanation about what they mean would be better.
"add [1, 1, 1, 1, 1] total 5 paths one by one" I get that [1, 1, 1, 1, 1]=len 5 etc but what does it mean in
a regular demo user should be able to understand how to use the demo to better understand the results; without having to refer to reading the paper details. (which I'm sure is great, and I will definitely read)
@ceyda Thanks a lot for your kind suggestions. We will update it today.
Additionally to better demonstrate the output:
image output re-rasterizes the image making the whole vectorization demonstration hard to see. can output multiple images; one per layer. (as done in paper's figures)
also maybe better to print the svg as an html element, would make it possible to see how the image got layered&vectorized using the dev tools inspect tool.
@ceyda Thanks for your kind suggestions. We also tried to have this function (output each layer result), but looks like it is hard to be implemented in space. We will try to figure it out.