Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 06 2016 21:30
    afelicioni starred friends-of-pebble/bam
  • Oct 08 2015 21:00
    matthewtole closed #3
  • Oct 08 2015 21:00
    matthewtole closed #1
  • Oct 08 2015 21:00
    matthewtole closed #2
  • Apr 20 2015 16:45
    matthewtole commented #3
  • Apr 20 2015 16:38
    cynorg commented #3
  • Apr 20 2015 12:17

    matthewtole on protocol

    Reduce number of bytes used for… (compare)

  • Apr 20 2015 12:17
    matthewtole synchronize #3
  • Apr 20 2015 12:12
    matthewtole opened #3
  • Apr 20 2015 12:12

    matthewtole on protocol

    Create message-header.md (compare)

  • Apr 20 2015 12:08

    matthewtole on protocol

    (compare)

  • Apr 19 2015 21:35
    Travis friends-of-pebble/bam-c (feature/unit-test-framework) passed (13)
  • Apr 19 2015 21:35
    Travis friends-of-pebble/bam-c#1 passed (14)
  • Apr 19 2015 21:34
    matthewtole synchronize #1
  • Apr 19 2015 21:34

    matthewtole on unit-test-framework

    Fix the Travis installation scr… (compare)

  • Apr 19 2015 21:20
    Travis friends-of-pebble/bam-c#1 errored (12)
  • Apr 19 2015 21:19
    Travis friends-of-pebble/bam-c (develop) passed (11)
  • Apr 19 2015 21:19
    matthewtole opened #1
  • Apr 19 2015 21:19

    matthewtole on develop

    (compare)

  • Apr 19 2015 21:18
    Travis friends-of-pebble/bam-c@7954ef9 (feature/unit-test-framework) errored (10)
Martin Norland
@cynorg
I'll claim some partial ownership once I contribute more than yammering
Matthew Tole
@matthewtole
:)
What’s the thoughts on what you can send through BAM. Do we just use the Pebble Dictionarys?
Martin Norland
@cynorg
I hadn't given any thought to it - were you thinking of having convenience functions for breaking out images and things?
(phone to watch, of course)
Matthew Tole
@matthewtole
Yeah, that would be ideal
For an MVP probably just using dictionaries is fine, since we can always add new functions later on.
Matthew Tole
@matthewtole
We should probably have an equivalent for all of the AppMessage methods. So you can literally just do a find and replace of app_message_ => bam_
Matthew Tole
@matthewtole
@cynorg Do you want to take lead on the C side?
Martin Norland
@cynorg
I could certainly give it a shot, though I've never done any testing within my kludgy Pebble app(s)
Matthew Tole
@matthewtole
I have a unit testing library we can use
Martin Norland
@cynorg
hahaha I just realized that Travis is unit tests and not a person
(looking at the sidebar)
Matthew Tole
@matthewtole
:)
It’s my friend Travis who sits at home all day and runs tests.
Good guy.
Kind of boring.
But decent.
Martin Norland
@cynorg
reliable, at least.
Matthew Tole
@matthewtole
Can be difficult when you first meet him
Martin Norland
@cynorg
so I presume @finebyte gets the Android side of things, and you're going to take JS
Matthew Tole
@matthewtole
Seems like a sensible division of labour
Martin Norland
@cynorg
I'm sitting here trying to decide if we need to set aside any conventions, or if everything underlying things will be just the pure/raw appmessages that users send
Matthew Tole
@matthewtole
We’ll need to come up with a protocol
Martin Norland
@cynorg
like, are we planning on adding any padding or additional options to the payloads
Matthew Tole
@matthewtole
Yeah otherwise how would we do big messages?
Martin Norland
@cynorg
forehead
cynorg @cynorg slaps his forehead
Martin Norland
@cynorg
I'm a little PKJS spoiled with my 2KB
Matthew Tole
@matthewtole
I was thinking that we’d need a few bytes at the beginning of each message:
BAM_VERSION
MESSAGE_ID
SEGMENT_ID
RETRY_COUNT?
Obviously need to keep it as small as possible.
Like a byte for each?
Also need something for the type of data we’re sending
Martin Norland
@cynorg
does the retry need to be inside the message itself? That seems, like priority, to be a local implementation detail
layering this on top of a 126 byte appmessage sure makes things thin
Matthew Tole
@matthewtole
True
Martin Norland
@cynorg
I guess if we only end up with 8 bytes or less, it's still a sizable win (hell, even if we used ~30 of the bytes, it's likely still very much worth it)
but yeah, minimizing the header/encapsulation is important, definitely minimize what goes into it where possible
Martin Norland
@cynorg
should we worry about AppSync at all, or do we think it's safe to assume that anyone using AppSync isn't ... really programming ;)
similarly (though more seriously) should C side have something for wrapping BAM messages inside datalogging
Matthew Tole
@matthewtole
Ooh that could be interesting
The second one I mean
Not MVP though
Martin Norland
@cynorg
no indeed not
I suppose, conceptually, that doesn't affect the protocol - it'd just be C function(s)
I've gotta get back to doing some actual work-related work - but I'd meant to ask, how did you seamlessly migrate your bam-* repositories to the new organization?
Matthew Tole
@matthewtole
I just changed the organisation
After renaming the organisation to hopefully not violate the Pebble trademark.
I’m hoping that “of Pebble” is as acceptable as “for Pebble” :/
I might rename it again before we launch.