add further support for mavlink

notes:
* the protocol seems bloated for our needs
* I'm not sure about the handling of primitive types in the protocol, especially the scalajs handling of numeric types of different widths seems cumbersome

1 files changed, 0 insertions, 30 deletions

diff --git a/vfd-mavlink/src/main/scala/org/mavlink/messages/Message.scala b/vfd-mavlink/src/main/scala/org/mavlink/messages/Message.scala
deleted file mode 100644
index 7e215c6..0000000
--- a/vfd-mavlink/src/main/scala/org/mavlink/messages/Message.scala
+++ /dev/null
@@ -1,30 +0,0 @@
-package org.mavlink.messages
-
-import org.mavlink.PayloadReader
-import org.mavlink.PayloadWriter
-import org.mavlink.Packet
-
-trait Message {
-  def pack(implicit mkWriter: Array[Byte] => PayloadWriter): Array[Byte]
-}
-
-trait MessageCompanion[M <: Message] {
-  def unpack(bytes: Seq[Byte])(implicit mkReader: Seq[Byte] => PayloadReader): M
-}
-
-object Message {
-
-  def unpack(packet: Packet)(implicit mkReader: Seq[Byte] => PayloadReader) = packet.messageId match {
-    case 0 => Heartbeat.unpack(packet.payload)
-    case 109 => RadioStatus.unpack(packet.payload)
-  }
-  
-  /*
-  private val msg = Heartbeat(23,1,2,4,5,6)
-  def foo = {
-    val spec = msg.pickle.value
-    (spec.id, spec.payload.mkString("(", ",", ")"))
-  }*/
-
-}
-  
\ No newline at end of file