On Jan 23, 2016 15:29, "Bryce Harrington" <bryce@...961...> wrote:
On Mon, Jan 11, 2016 at 11:54:45AM -0800, Krzysztof Kosiński wrote:
2016-01-10 17:52 GMT-08:00 Josh Andler <scislac@...400...>:
The application period is still a about a month out, but one of the
things
we do need to get on sooner rather than later is getting people to
volunteer
to mentor so we can get the ideas section right by the time we
actually
apply. We also need to gauge how many interested devs we might have
for
mentoring this year so if you're interested, please reply saying so.
I am interested in mentoring. I can also write up some project ideas.
I think a good student project would be to introduce Inkscape::ObjectSet as a base class of Inkscape::Selection that's not tied to the UI, and change the internal data structure from a list to a Boost Multi Index container (similar to Java's LinkedHashSet).
That does sounds like it would make a good GSoC project, I'd encourage you to write it up.
Will try to do this this week as I'll finally have Internet at home.
Do we use Boost containers elsewhere in Inkscape yet? Is the benefit over the STL list performance related or something else?
2Geom uses them in several places, Inkscape itself to a lesser extent.
I presume you have use case ideas for how the ObjectSet base class could be used beyond the UI?
For instance, as input to Boolean operation functions, as used in the spray tool. Right now it adds to the shape by manipulating the global selection.
Another idea is to write unit tests for Inkscape's object tree ("SP
tree").
Alternately this might make a good funded project.
(Did we still want to go through and rename "SP" to "Ink" or something else to move away from the sodipodi ancestry? If so, might be worth doing prior to or as part of this.)
This is somewhat low priority. I would be more interested in fixing namespace proliferation such as Inkscape::UI::View::View.
Best regards, Krzysztof