On Jan 17, 2008 3:55 AM, Felipe Sanches <felipe.sanches@...400...> wrote:

I started coding it. Though it is not working yet.

How does inkscape knows that my Class handles a specific tag? I mean... how will i have 4 different tags (<feFuncR>, <feFuncG>, <feFuncB> and <feFuncA> be handled by my SPFeFuncNode class ?)

I supose that you are more confortable with this than me, so, if possible, could you take my patch and complete it? I have spent hours trying to figure out how to do it and now I wish to focus on implementing the render method.

I would also ask for nicholas to help us to adapt the UI

Hoppefully we can have this filter implemented before 0.46 release. Then the only ones that would be out are feImage and feTile

On Jan 16, 2008 5:57 PM, Niko Kiirala <niko@...1267...> wrote:
Wed, 16 Jan 2008 12:45:15 -0200
"Felipe Sanches" <felipe.sanches@...400...> kirjoitti:

> can you help me? I am not sure how do we deal with nested tags . How
> do I read their attributes?

I belive, the best way to set this up is to create SP-classes for those
tags, that can be children. Then implement child_added, remove_child and
order_changed callbacks in the parent class. These callbacks are not
strictly required, but following modifications is often useful.

With these, in the parent class you can access this_object->children,
this_object->children->next etc. (this_object here is a pointer to
object of the parent class type) Then, you may need suitable accessors
in the cild classes, that give you the information you need.

See sp-fespecularlighting.cpp for an example. The child classes in this
case are in sp-fespotlight.cpp, sp-fedistantlight.cpp and
sp-fepointlight.cpp

--
Niko Kiirala
niko@...1267...