You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A number of tests have shown that Cherrytree saves images in PNG format, each time recompiling. That is, even if you give an optimized png image as input, it will still make its own unoptimized png from it. I consider this a problem. As the size of the database grows, the speed of the autosave function decreases, and hence the speed of the program as a whole. I suggest adding a module that will also optimize the image via optipng if present on the system.
Also, I don't like that I can't save a small image with indexed colors (for example 10 colors and its size is 10 KB). Instead, Cherrytree converts to full rgb (for example, with a size of 60 KB). I voiced this idea only as an extra reason to think about optimizing the approach to storing and using images
A number of tests have shown that Cherrytree saves images in PNG format, each time recompiling. That is, even if you give an optimized png image as input, it will still make its own unoptimized png from it. I consider this a problem. As the size of the database grows, the speed of the autosave function decreases, and hence the speed of the program as a whole. I suggest adding a module that will also optimize the image via optipng if present on the system.
http://optipng.sourceforge.net
The text was updated successfully, but these errors were encountered: