© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Dusan,
The explanation is in the code. Just grab it and look around.
Things started out with hardcoded math and assumptions spread all over the code base in all sorts of methods. If one has assumptions coded in to each and every function that does part of UI or editing work or such, that does take quite a bit to fix.
Among other things there *HAS* been a lot of work going on to address this. We even have a complete stand-alone math library now as part of this work. So it has not just been ignored, as you imply.
To answer specifically:
"Has the project become any simpler?"
Yes, it has. The complexity is perhaps even an order of magnitude less that it was originally.
"Will the passage of time make this any less of an issue?"
Yes, it will. See lib2geom and other work. By cleaning up hardcoded assumptions that are spread all over and instead unifying them to single locations it is getting much less of an issue to address.
"This issue will grow in complexity right along with Inkscape itself."
No, it won't. The work that will be required to specifically address this has been *reducing* in complexity as Inkscape code has matured.