Re: [OpenMap Users] MRGS layer? Azimuthal layer?

Hi Don,

----- Original Message -----
From: "Don Dietrick" <dietrick@bbn.com>
To: "Piotr Kaminski" <Piotr.Kaminski@ctm.gdynia.pl>
Cc: <openmap-users@bbn.com>
Sent: Sunday, May 16, 2004 3:24 AM
Subject: Re: [OpenMap Users] MRGS layer? Azimuthal layer?

> Hi Piotr,
>
> On May 15, 2004, at 7:36 AM, Piotr Kaminski wrote:
>
> > Hi,
> >
> > If layer are now preffered over plugins (see message below)
> > maybe we should rewrite UTMPlugin as UTMLayer?
>
> I didn't mean to say that layers are unilaterally preferred over
> plugins, to a point where you would rewrite your plugins into layers.
> PlugIns can be used as data access components without actually adding
> them to a PlugInLayer, depending on what your application needs are.
> They aren't Swing components, but they do provide OMGraphics. So
> that's something in their favor.
>
> The thing you have to ask is, what would you gain from converting the
> PlugIn to a Layer. Probably not much, in this case.
>
> > I've seen MRGSPoint class but no MRGSLayer. Maybe someone
> > has such layer already implemented and could send its source code?
> > If not I'm going to make MRGS layer implementation based on
> > UTMPlugin as a code template (so my question about rewritting UTMPlugin
> > as layer).
>
> UTMPlugIn renders MRGS rectangles when configured to. I don't know
> what else a MRGSLayer would do.

I didn't know that. I will try to configure it. If it will work the same way
as for UTM
grid it is enough for me.

>
> > Another qustion is for AzimuthalLayer. Has someone already write such
> > layer
> > and could send source code to be added to OpenMap's codebase?
>
> What would an AzimuthalLayer render?

Maybe I used wrong name for that layer. It is simple translation of Polish
name for that
kind of grid. I expect drawing of concentrical rings with additional 'ticks'
for azimuth
values from 0 to 360 degrees. Such layer is often used in our applications
on a ship or aircraft.
The grid is anchored in the center of displayed map. Map center is
periodicaly moved while ship
is moving (sometimes map is also rotated to match current course of vessel).
Rings are used to determine ranges to other objects on map. Ticks helps to
determine bearing.

>
> BTW, in case you hadn't noticed, I checked in the ProjectionLoader
> stuff for runtime addition of projections. Check the CHANGELOG for
> details, I'd appreciate comments.

That is feature I was waiting for! I will try to use it soon and let you
know my thoughts.

Regards,
Piotr

>
> - Don
>
> > ----- Original Message -----
> > From: "Don Dietrick" <dietrick@bbn.com>
> > To: <MNewcomb@tacintel.com>
> > Cc: <openmap-users@bbn.com>
> > Sent: Saturday, May 15, 2004 3:36 AM
> > Subject: Re: [OpenMap Users] Layer vs. Plugin?
> >
> >
> >> Hi Michael,
> >>
> >> This is actually a very good question.
> >>
> >> On May 14, 2004, at 4:24 PM, MNewcomb@tacintel.com wrote:
> >>
> >>> UTMGridPlugin vs. GraticuleLayer
> >>>
> >>> Why was one built as a plugin and the other as a layer?
> >>
> >> The GraticuleLayer was one of the first layers ever written, before
> >> plugins were conceived. Plugins were invented to abstract some of the
> >> data access and OMGraphic creation away from layer management, so that
> >> the OMGraphics could be created in an object that could be used in a
> >> client or a server.
> >>
> >> The addition of OMGraphicHandlerLayer in 4.6 has made it pretty easy
> >> to
> >> create a Layer, even easier than a PlugIn.
> >>
> >>> Can you give me some differences between the two?
> >>
> >> A Layer is a Swing component. A PlugIn is an OMGraphic factory that
> >> can be used by a Layer.
> >>
> >>> When should I use Plugin/Layer?
> >>
> >> You should use a PlugIn if you think you may want to reuse the
> >> OMGraphic creation code in a server. Although I should point out
> >> there
> >> isn't any PlugIn server code, nor a client that could talk to one.
> >>
> >> I almost always write layers now that inherit from
> >> OMGraphicHandlerLayer. I put any code used to get to a data source to
> >> create OMGraphics in the com.bbn.openmap.dataAccess package tree, and
> >> then have a simple OMGraphicHandlerLayer use those components. The
> >> OMGraphicHandlerLayer
> >> has a bunch of new MouseEvent handling code in it that makes it really
> >> easy to react to mouse events in a common way, and that hasn't been
> >> translated into PlugIn yet.
> >>
> >> Hope this helps,
> >>
> >> Don
> >>
> >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> >> Don Dietrick, dietrick@bbn.com
> >> BBN Technologies, Cambridge, MA
> >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> >>
> >> --
> >> [To unsubscribe to this list send an email to "majdart@bbn.com"
> >> with the following text in the BODY of the message "unsubscribe
> > openmap-users"]
> >>
> >
> > --
> > [To unsubscribe to this list send an email to "majdart@bbn.com"
> > with the following text in the BODY of the message "unsubscribe
> > openmap-users"]
> >
> >
>
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Don Dietrick, dietrick@bbn.com
> BBN Technologies, Cambridge, MA
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> --
> [To unsubscribe to this list send an email to "majdart@bbn.com"
> with the following text in the BODY of the message "unsubscribe
openmap-users"]
>

--
[To unsubscribe to this list send an email to "majdart@bbn.com"
with the following text in the BODY of the message "unsubscribe openmap-users"]