Changes between and of Initial VersionVersion 18Ticket #3926
- Timestamp:
- 07/08/2011 04:53:26 PM (23 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #3926
- Property keywords changed from review protocols gps positioning to protocols gps positioning review
- Property owner glyph deleted
- Property summary changed from twisted.protocols.positioning -- a better positioning frameworkjk to twisted.positioning -- a better positioning framework
-
Ticket #3926 – description
initial v18 9 9 3. It assumes we're using satellite navigation (well, not really, but only because there's no interface that says what it does) 10 10 11 This ticket is about a proposed alternative, `twisted.p rotocols.positioning`, which hopefully will:11 This ticket is about a proposed alternative, `twisted.positioning`, which hopefully will: 12 12 13 13 1. deprecate the existing code … … 31 31 We should try to keep this API as general as possible (making as few assumptions about the underlying protocol as possible). 32 32 33 First thing to do should probably be finalizing the IPositioningDataReceiverinterface. 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.33 First 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. 34 34 35 35 This 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). … … 37 37 The 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. 38 38 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) :-) 39 You can find the code on Github: http://www.github.com/lvh/twisted has a `positioning-3926` branch.