I do this to achieve the result which is quite a similar:<br>1. Open Image<br>2. Copy that layer<br>3. Blur the image with gaussian blur (let's take value 30 )<br>4. Add layer mask to blur layer layer (white - as full opacity)<br>
5. Use gradient tool to make some gradient as needed<br>6. Tadaa<br><br>Is it that?<br>My result in attachment<br><br><div class="gmail_quote">2009/1/11 Moritz Moeller <span dir="ltr"><<a href="mailto:realritz@virtualritz.com">realritz@virtualritz.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Boudewijn,<br>
<div class="Ih2E3d"><br>
> That's basically what a bumpmap filter in Krita or Gimp does, isn't it? Take a<br>
> layer (or mask, both are nodes) and use it to determine modifications in<br>
> another layer or mask. I think I already finished porting the bumpmap filter<br>
> this summer, so there's an example ready for anyone who wants to implement<br>
> such a filter.<br>
<br>
</div>I guess my comment was more meant along the lines of: this should be<br>
available on a lower level and the developer of a filter not have to<br>
care about it much.<br>
<br>
Basically, the developer should choose, for each parameter their filter<br>
exposes, if the parameter is constant or varying.<br>
In the latter case, the filter needs to call a function to obtain the<br>
resp. local value of a parameter, at each position filtered.<br>
Where this value comes from, ultimately, the developer does not need to<br>
know. This is managed by the application elsewhere.<br>
<br>
In a good system such a parameter query function would be overloaded to<br>
support feeding just the parameter's name/id, optionally position,<br>
optionally four positions (returns a filtered value of the parameter<br>
over that area) and optionally a filter type (uses that filter to filter<br>
the value).<br>
<br>
See the texture() shadeop in the RenderMan shading language.<br>
<br>
Then there should be functions to get derivatives of the parameter in x<br>
& y direction (see the du() dv() functions and the dPdu and dPdv<br>
variables in the RenderMan shading language).<br>
<br>
For bump mapping you probably needed to calculate a lot of this yourself<br>
already. It would be good to expose this in a high level API.<br>
<br>
I certainly dunno how much work the current API requires to be that<br>
"high level".<br>
If that stuff is already supported, ignore my comment. :)<br>
<br>
<br>
Beers,<br>
<font color="#888888"><br>
Moritz<br>
</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
kimageshop mailing list<br>
<a href="mailto:kimageshop@kde.org">kimageshop@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kimageshop" target="_blank">https://mail.kde.org/mailman/listinfo/kimageshop</a><br>
</div></div></blockquote></div><br>