-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for svg reading #4
Comments
First step would be probably be round trip reads to ensure we can read any svg that we write. it's not clear if we'll be able to easily support reading ANY svg, but we might be able to get quite far ... |
This issue has been mentioned on Image.sc Forum. There might be relevant details there: https://forum.image.sc/t/is-it-possible-to-load-an-svg-file-as-a-shapes-layer-in-napari/41873/3 |
Hi @sofroniewn , |
That's great @jmontoyam! I'm happy to guide you through your first contribution to napari, to make an svg readable as a shapes layer. Doing this should also require changes to this repository. To get started you should look at the overall contributing guide for napari and then set up a development version of this repository You'll also want to familiarize yourself with the plugin section of our documentation. Step 1 is going to be to add a Step 2 is going to be to create a function called Step 3 Is going to be to actually write the Hope this helps get you started!! I'm looking forward to helping you with this. |
Thank you very much @sofroniewn for all the advice and suggestions!...I will get back to you as soon as I have finished reading and understanding all the info/code you mentioned above ;). |
@jmontoyam I have some Python code I adapted for reading many (not all) SVG elements and drawing them with Turtle. Maybe it's useful as a reference? https://github.com/ctrueden/miles-python/blob/master/drawsvg.py |
Thanks for sharing that @ctrueden! That looks like a great starting point. Nice to use |
Thank you very much @ctrueden ! |
Add support for svg reading
The text was updated successfully, but these errors were encountered: