The biggest question I have now is if I should rewrite TinLayer to extend Layer
instead of just implementing Layerable. For the life of me I can't figure out
how to access non-Layer Layerables from a PlugInContext. This is necessary
functionality that I need in order to implement TIN analysis functions (ie
contour lines, watersheds, etc). It might be easier to slightly change the JUMP
core to allow access to Layerables through PlugInContext than to rewrite
TinLayer to extend Layer, but then I still have to deal with all the display
code that expects Layers. The biggest problem with rewriting TinLayer is that
I'll have to fake the existence of Features and their Geometries.
Any hints?
--Christopher
--- On Wed, 7/23/08, Sunburned Surveyor <[EMAIL PROTECTED]> wrote:
> From: Sunburned Surveyor <[EMAIL PROTECTED]>
> Subject: Re: [JPP-Devel] Bunch of questions (mostly UI based)
> To: "OpenJump develop and use" <jump-pilot-devel@lists.sourceforge.net>
> Date: Wednesday, July 23, 2008, 7:13 AM
> Christopher,
>
> I agree with Michael's answers. Do you still have
> questions after
> reading his e-mail?
>
> I believe the class that manages the display of layers is
> LayerNamePanel.
>
> The Sunburned Surveyor
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
