Hello all,
In spirit of codebase cleanup, I'd like to propose a simple renaming idea, to make things more clear to the developer (to me, at least :) I think, apart from C++-ifying, it would be a lot clearer when the SPObjects are renamed to either "SPObject" (the same :P) or "SVGObject". An example:
SPPath represents svg:path in the SVG. When svg:path is added to SVG, Inkscape immediately generates an SPPath for it. I therefore propose to rename it to something that reflects this aspect of SPPath: that it is directly linked to something in SVG. SPDesktop for example is *not*. SPDesktop => SPDesktop, stays the same SPPath => SVGPath, meaning it represents some element in the SVG. SPShape => SVGShape (since all its derivates are SVG elements) SP_IS_PATH => IS_SVG_PATH (I never understood why it isn't named IS_SP_PATH)
SPNamedview => SVGNamedview ? Now this one is a troublemaker. Because it is linked to sodipodi:namedview in the XML. I still think we should rename it with SVG up front, because it is linked to something in the SVG, does not matter what its name in XML is.
Please, if this above all is non-sense, slanted or incorrect in any way, let me know!
I do not know what to do with the filename. I propose to keep them sp-path and such, to avoid losing SVN history, which is absolutely unacceptable to me. (I don't know how to rename files in SVN, is that possible?) Note that we actually already have a file called svg-path...
If no (negative) comments have reached me, I'd like to start this in a week or two. I really think it clears up things. It is sort of a first step into grouping things.
Thanks, Johan