Open alexander-welshtein opened 6 months ago
@alexander-welshtein Thanks for these suggestions! I think improving SVGSpace would be the best approach, but it's a bigger effect and currently my time for maintaining this project is very limited.
Happy to review smaller PRs like the text paragraph issue in #2. I agree that getting the text contents can be useful. The paragraphBox
function can potentially return an array of text instead of this
.
@alexander-welshtein Thanks for these suggestions! I think improving SVGSpace would be the best approach, but it's a bigger effect and currently my time for maintaining this project is very limited.
Happy to review smaller PRs like the text paragraph issue in #2. I agree that getting the text contents can be useful. The
paragraphBox
function can potentially return an array of text instead ofthis
.
Great! Then I will consider adding this small PR that will allow us to remove borrowings from our solution. And I’ll see how the SVGSpace works as time permits. Possible changes can be discussed.
I continue the section of those things that we have developed while working with this tool. In our tasks, each shape must be exported as a separate SVG. At the same time, we keep working with shapes within CanvasSpace. We export to SVG manually, including the text paragraph (by overriding the functionality of the
Canvas/paragraphBox
andCanvas/_textTruncate
methods). Based on this, two points that can be considered as improvements to the library:In this case, I can prepare a PR if the development is approved. Or need more information?
P.S. Also, perhaps these things could be solved by a more developed SVGSpace/SVGForm compatible with CanvasSpace/CanvasForm