On Tue, 20 Jun 2006 19:19:32 -0400 "bulia byak" <buliabyak@...400...> wrote:
However, the final decision is up to the developers. Niko and Hugo, what do you think? Is there some kind of milestone after which we can merge the development in the trunk in such a way that it does not affect anything else and allows you to work on your part?
This idea of merging came up on inkscape jabber channel yesterday. It seems so, that the merge could be done just fine.
Ted has a good point about submitting our code to Google at the end of summer. Though, it seems to me that we already have gone past the point, where we could just grab a diff from the branch and submit that - the branch does contain code from two SoCers and some code from Bulia, too.
In general, I would like to see more communication from you. Can you write a brief summary of where you're at, what are your plans for the immediate future, and how it all goes in general? Please send it to the developers list, not just to me, so that others can see your progress as well.
Well, overall status is as follows: * SPFilter objects get built from svg <filter> -elements - Hugo knows more about what this includes. * SPStyle recognises filter-property in objects and fetches a SPFilter accordingly (though does not seem to pay any attention to filters defined inside style-property) * Paths, groups and texts can handle filter-property in style and set the NRFilter pointer in NRArenaItem, if the object has filter - The NRFilter set still pays no attention to SPFilter properteries, at the moment I am designing an interface for this - In other words: if an object has a filter defined for it, that information is passed on to renderer * Gaussian blur renderer works quite well. It also needs an interface for setting its parameters.
So my plans are quite clear for some time from now: first I design those two interfaces and then I start implementing the functionality provided by them.