> Hi Jack,
>
> I'm kind of slogging through a stressful day today with some other stuff
> hanging over my head.  If the patches are intended to go into the main
> line,
> I'd love to have Tim take a pass at reviewing them.  For a quick hack you
> could just do a traditional "diff -c" sort of patch if you wanted to share
> the changes and let other people try them or take a look at the code.
>
Ok, let me try that.

The goal is to move them into the main line at some point and a review is
definitely in order. In the near term, a quicky would work

ATM slogging through the code to understand how shaders work.  The edge
blending will be a shader program, most likely a fragment shader at the
pixel level. But having a tough time getting my head around how to include
the shader in the code as part of the scene graph.  The Docs help, but
more info than what is needed ( at least that's my impression ).  Just
need to understand how to incorporate, say, an "edgeblend.frag" chunk of
GLSL code into the scenegraph, It's pretty much a static set of functions
with zero options, no fancy animation, techniques, quality-levels, or
other predicates.

The code will test the pixels in the overlap region, adjust the RGB values
based on position and then apply a gamma correction.

Any thoughts or examples from the community of a basic template and a
howto for adding a fragment shader would help.

Thanks
Jack

> Curt.
>
>
> On Mon, May 16, 2011 at 11:45 PM, <cas...@mminternet.com> wrote:
>
>> Hi Curt,
>>
>>  A while back Tim Moore offered to post the image warping code onto the
>> GIT site. Since then I've not heard from him and emails have gone
>> unanswered --  no idea as to why... :-(
>>
>> At any rate, tried to setup a GIT library myself and nothing but
>> frustration and zero success in setting up a branch or whatever to make
>> the code public.
>>
>> Might you have a moment to help me get it posted?  Would tomorrow be a
>> good time? And best time and number to call if you have the patience to
>> walk me through the process. Or if you're too busy, no problem -- sooner
>> or later I'll get it figured out.....  is there a good howto somewhere
>> that would do the trick?
>>
>> Regards
>> Jack
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Achieve unprecedented app performance and reliability
>> What every C/C++ and Fortran developer should know.
>> Learn how Intel has extended the reach of its next-generation tools
>> to help boost performance applications - inlcuding clusters.
>> http://p.sf.net/sfu/intel-dev2devmay
>> _______________________________________________
>> Flightgear-devel mailing list
>> Flightgear-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>>
>
>
>
> --
> Curtis Olson:
> http://www.atiak.com - http://aem.umn.edu/~uav/
> http://www.flightgear.org - http://gallinazo.flightgear.org
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay_______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>



------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to