Yeah.. I definitely think it's worth taking a look at. I think that as
computer programmers, we ought to be careful that we don't get lost
abstracting, encapsulating, modulating and applying every principle of good
programming so much that some of the should be simple tasks become
ridiculously more difficult than is necessary. Programming principles
shouldn't be that potent... the concept should dictate what functionality
should be grouped together. I'm quite new to OpenMap and I hope that I can
make a reliable contribution to it one day. :) Great project, forgive me if
my comments sound a tad bit uneducated. :-D
Don Dietrick wrote:
>
> Hey JayDub,
>
> I took a look at this a while ago, and found that I still had to
> handle every type of OMGraphic even if there were similar methods so I
> didn't change anything in order to preserve backward compatibility.
> It might be worth another look before the release, at least to make
> sure that OMGraphics of the same type have similar methods.
>
> Cheers,
>
> Don
>
> On Jun 5, 2009, at 10:27 AM, JayDub wrote:
>
>>
>> Hey Don, will there be a standard way to get lat,lon coords for
>> OMGraphics in
>> OM5? I think there should.
>> LatLon getLatLon();
>> And let the different graphics interpret that differently. For a
>> point,
>> obvious results. For a polygon, probably it could return the
>> centroid, for a
>> line same thing.
>>
>> I find it difficult to believe that you can't get back a location
>> from an
>> OMGraphic. Or I just don't know how to. At any rate, if there's a
>> way I
>> think it should be clearer and easier to access and implemented in
>> OMGraphic
>> or BasicGeometry.
>>
>> :jumping:
>>
>>
>> Don Dietrick wrote:
>>>
>>> I just wanted to let everyone know I made some changes to OMGraphic,
>>> OMGraphicList and OMGeometryList for OpenMap 5, and these might
>>> affect
>>> your code.
>>>
>>> OMGraphic has been changed into a interface, and a new
>>> OMGraphicAdapter class is available to use as a base class for custom
>>> OMGraphics.
>>>
>>> There's a new com.bbn.openmap.omGraphic.OMList class that implements
>>> OMGraphic and List<? extends OMGeometry>. OMGraphicList and
>>> OMGeometryList extend OMList, and return typed values for all of
>>> their
>>> List functions. They are also iterable.
>>>
>>> So, for those keeping score:
>>>
>>> Interfaces: OMGraphic extends OMGeometry
>>>
>>> Classes: OMGraphic classes (OMPoint, OMPoly, etc) extend
>>> OMGraphicAdapter extends BasicGeometry
>>>
>>> Lists: OMGraphicList, OMGeometryList extend OMList implements
>>> OMGraphic, OMGeometry, List
>>>
>>> I figured since the API is changing anyway with this release and
>>> makes
>>> the API better, it's time.
>>>
>>> BR,
>>>
>>> - Don
>>>
>>> --
>>> [To unsubscribe to this list send an email to "majdart_at_bbn.com"
>>> with the following text in the BODY of the message "unsubscribe
>>> openmap-users"]
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Recent-updates-to-OM5-tp23856726p23889259.html
>> Sent from the OpenMap mailing list archive at Nabble.com.
>>
>> --
>> [To unsubscribe to this list send an email to "majdart_at_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_at_bbn.com"
> with the following text in the BODY of the message "unsubscribe
> openmap-users"]
>
>
--
View this message in context: http://www.nabble.com/Recent-updates-to-OM5-tp23856726p24094998.html
Sent from the OpenMap mailing list archive at Nabble.com.
--
[To unsubscribe to this list send an email to "majdart_at_bbn.com"
with the following text in the BODY of the message "unsubscribe openmap-users"]
Received on Thu Jun 18 2009 - 11:11:01 EDT