<div class="gmail_quote">On Thu, Aug 13, 2009 at 6:26 AM, Laurens Van Houtven <span dir="ltr"><<a href="mailto:lvh@laurensvh.be">lvh@laurensvh.be</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Short question up front: what exactly should be in the proposed<br>
factory class? What does it take? What does it return?<br>
</blockquote><div><br>Factory class proposed by whom and for what?<br><br>If it's a thing that creates IPositionReceivers, it should return an IPositionReceiver and take some description of where the position data is coming from. The existing analogue is IProtocolFactory.buildProtocol, which is takes an IP address. I assume that the "address" object in GPS's case is something that identifies the capabilities of the position-information-providing widget and its type (GPS, skyhook, tower triangulation, etc).<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Second question: what should NMEASentence attributes look like?<br>
Properties? There are some proposed things in t.p.nmea in trunk.</blockquote><div><br>By "trunk" I hope you mean "not trunk, the branch". Maybe you meant HEAD?<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Also, progress report:<br>
- NMEAAdapters now correctly fire callbacks on receivers. There<br>
are tests that show this working for multiple sentences.<br>
- NMEA date support. You now get callbacks with date and time.<br>
</blockquote><div><br>Great!<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">New things can be found in trunk at the usual places (launchpad).</blockquote>
<div><br>... "in the branch" at the usual place ;-). <br><br></div></div>