Vangelis Katsikaros <vkatsikaros@...1244...> wrote:
Bryce Harrington wrote:
We have had one good experience with a paired project (for svg filters).
[snip]
While this can make it complex to organize, paired projects can be effective both from the standpoint of doubling the manpower on the feature, and because the students can share ideas, tips, solutions, code reviewing, and so on. But they need to be treated as distinct, independent projects for GSoC projects, and cannot be interdependent, else it makes it harder to evaluate them.
That would be fine by me! However, I don't have enough Inkscape internals experience, in order to propose a way of splitting.
Splitting is indeed an interesting alternative. However, on second thought I'm not sure if it's really worth it in this case. I guess whoever does the guidelines refactoring should simply have other possible use cases in mind. With some guidance and hints from people who have more experience with Inkscape's internals I'm sure Vangelis would do this just as well.
However, I could submit two applications:
- Guidelines
- Transformation Anchors (I have sent a seperate mail about this).
In this way, Maximilian can choose guidelines or implement an idea of his own or choose guidelines with 3d box in mind.
In all the above cases I can either do project 1) or 2).
But this would mean double work for you while making things a lot easier for me. :) I'd certainly be more than grateful for this courtesy of yours. But maybe it's best to wait for a comment from the devs on my other ideas and if none of those turns out to be feasible we can still decide how to split up guidelines and transformation anchors between the two of us (am I correct in assuming that if possible you still would prefer to do guidelines?). Otherwise you can concentrate on a single proposal, which saves you time and energy.
Best, Max