What about "CompoundPath"?
Didn't know this beforehand, but try googling for compound path: apparently this name is being used in Illustrator too.
Diederik
On Wed, Jun 25, 2014 at 8:49 PM, Johan Engelen <jbc.engelen@...2592...> wrote:
On 25-6-2014 20:19, Krzysztof Kosiński wrote:
2014-06-25 17:41 GMT+02:00 Josh Andler <scislac@...400...>:
Hey Krzysztof,
Thank you for the update. After playing with that cgal toy here, it is indeed disappointing... definitely a shame their implementation wasn't
more
robust. Given that the first half of GSoC has had a lot of unexpected
time
eaten up by University stuff, in addition to API related tasks you've designated, would you be willing to put forth an estimated timeline for
what
you would expect to accomplish in the second half?
In the next two days, I want to complete some of the path API rewrite. I want to do at least some of the following:
- Rename Path to SubPath,
- Rename PathVector to Path,
I agree that PathVector is a poor name (plus I am not sure if inheriting from std::vector is allowed..., definitely needs improvement as you've planned). But I think we should not rename Path. I think it is a better name than SubPath, which could be taken to mean a part of a contiguous path, instead of its intent "contiguous path". It would be strange for a user that only works with contiguous paths to use SubPath instead of Path, I think. (let's not make 2Geom too SVG-biased in naming) So let's come up with a better name for PathVector. Some names that come to mind: MultiPath PathSet
anyone?
regards, Johan
Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel