[Feature request]: Consider SVG as native backend format.

[Evidlo]

I'd just like to open discussion on the feasibility of using SVG as a native notebook format as an alternative to .bfly Zip/JSON format. Adopting SVG would confer some immediate benefits:

• web native - can link/embed notebook documents directly in web pages
• interoperability with other tools - Inkscape, Krita, Blender, Penpot, etc...

Many primitives in Butterfly have direct analogs to SVG primitives, like freehand strokes (paths), shapes (rect, arc, polygon, etc.), stamps (defs), layers, pages (views), etc. and any features which do not have direct analogs (e.g. texture) can still be implemented as standard SVG elements with custom Butterfly-specific attributes thanks to the extensibility of XML.

Code of Conduct

• [x] I agree to follow this project's Code of Conduct

[CodeDoctorDE]

Good idea. I will consider this. I'm also open for contributions. For this we need to improve the svg exporter a bit. A checkbox for exporting meta information like tools you mentioned would be good here I used bfly original since zips can be encrypted and compressed and we could add assets as files which is better for performance

[phourglass]

The application is looking good but I can't find a way to export to svg or vector pdf.

I understand the need for a native format for speed or library use but without an export, investing time in notes seems risky (lock in, been there). Also many workflows may require other tools (e.g. annotate pictures with dimensions and further edit them in other software, my intended use).

Could an export be added (or made more visible) even if it is not fully functional at first?

Thanks!

[CodeDoctorDE]

There is one, on the top left corner menu, just on export -> svg. I'm not sure how I should make it more visible but I'm open for ideas.

[phourglass]

Thanks for the response. That menu is perfectly clear.

I got confused because I found the other export menu in "files" first. That one is different as it only allows the native format.

If assuming others may get confused, using the full export menu with format options in both locations would prevent that (I have noticed some functions are accessible from several locations). Otherwise it may be better to call the limited menu "save as".

Thanks for your software.

[CodeDoctorDE]

Oh yeah. Exporting to svg, png and pdf needs a document to be open to render it. Exporting with the butterfly doesnt need to since it just allows you to use the file content and transfer the file in an external folder.

But im currently thinking about adding an option to bulk export png, svg and pdf inside the file view which can also solve your previous problem.

I would say: if you as an end user does not understand the interface, its usually a design problem, not a user error. Thats why i was asking

[phourglass]

Thanks for the response. I guess a bulk export would be useful (I could use one after taking notes). Closed for me.