>> Do you plan runtime selection of SVG library? This is not very >> user friendly. Perhaps it is better to have separate rendering >> modules for each SVG library, selected at compile time. I will >> take a detailed look at your code soon. > > Well, yes, at the moment it is selected at runtime. Once we decide > on a default rendering library we could create default hooks, so the > end user won't need to set them unless they want to plug a different > library (other than the default one). And with some modifications > we can integrate this with the build system so that the default one > can be switched at compile time.
Yes. > However, separate rendering modules is a completely different design > choice. I think separate modules is overkill. Who is ever going to use two different SVG renderers in a single program? I guess only the ftview demo programs and its siblings could need that for debugging purposes (i.e., to compare rendering results of different SVG engines). Werner _______________________________________________ Freetype-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype-devel
