Changes between and of Initial VersionVersion 18Ticket #3926


Ignore:
Timestamp:
07/08/2011 02:53:26 PM (3 years ago)
Author:
lvh
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3926

    • Property Owner glyph deleted
    • Property Keywords changed from review protocols gps positioning to protocols gps positioning review
    • Property Summary changed from twisted.protocols.positioning -- a better positioning frameworkjk to twisted.positioning -- a better positioning framework
  • Ticket #3926 – Description

    initial v18  
    99    3. It assumes we're using satellite navigation (well, not really, but only because there's no interface that says what it does) 
    1010 
    11 This ticket is about a proposed alternative, `twisted.protocols.positioning`, which hopefully will: 
     11This ticket is about a proposed alternative, `twisted.positioning`, which hopefully will: 
    1212 
    1313    1. deprecate the existing code 
     
    3131We should try to keep this API as general as possible (making as few assumptions about the underlying protocol as possible). 
    3232 
    33 First thing to do should probably be finalizing the IPositioningDataReceiver interface. Getting it right is extremely important and has big implementation consequences: NMEA might present data in an illogical or useless order, but this shouldn't change our interface significantly. 
     33First thing to do should probably be finalizing the `IPositioningReceiver` interface. Getting it right is extremely important and has big implementation consequences: NMEA might present data in an illogical or useless order, but this shouldn't change our interface significantly. 
    3434 
    3535This raises problems with the `fooReceived` methods, since data that is made available in chunks (`headingRecieved` doing both magnetic and true headings for example) might not have that data made available in the underlying implementation (some NMEA sentences only provide true heading, some proprietary ones only provide magnetic heading, and some sentences provide both -- it doesn't make sense to ignore the data from the first two types of sentence simply because they didn't have both kinds of heading). 
     
    3737The easy way out is to make the objects that the interface deals with as abstract as possible. With enough eyes, every problem is tiny, so your comments are much appreciated as usual. 
    3838 
    39 A fork has been created on launchpad: https://code.launchpad.net/~lvh/twisted/positioning 
    40  
    41 Discussions should preferably be either here or on IRC (my nick is 'lvh' on freenode, you can find me in #python and #twisted) :-) 
     39You can find the code on Github: http://www.github.com/lvh/twisted has a `positioning-3926` branch.