Documented some new actions

[Jeija]

Thank you 👍 !

Just as a note: Those action subindices contain even more actions that for different specific values, e.g. 55.1.0.2 is "the day is ours". More documentation on Furby's actions is always welcome!

[beacrea]

Very interesting! I'll have to explore those as well. :D

[Jeija]

I was wondering if maybe we should document the actions in some kind of machine-readable format (JSON, XML, CSV??) to make them better searchable? Just to make sure that if you / anyone else wants to help by documenting large numbers of actions we better save some time and store them in some sane format right from the beginning.

[beacrea]

I think that's a great idea. Would JSON be the most approachable? It's obviously easy to convert between any of them, but might be the easiest format for Furby to be plugged into IoT/web.

On Wed, Jan 25, 2017, 11:58 AM Florian Euchner notifications@github.com wrote:

I was wondering if maybe we should document the actions in some kind of machine-readable format (JSON, XML, CSV??) to make them better searchable? Just to make sure that if you / anyone else wants to help by documenting large numbers of actions we better save some time and store them in some sane format right from the beginning.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Jeija/bluefluff/pull/4#issuecomment-275182915, or mute the thread https://github.com/notifications/unsubscribe-auth/ABBX7bFBKXmr3ZqOfey2nEb2R-vavE99ks5rV40vgaJpZM4Lsz-x .

--

---

Coty Beasley UX Specialist

// Contact Information p: 816.200.2689 http://tel:816-200-2689/

// Social Networks [ + Twitter http://twitter.com/beacrea ] [ + LinkedIn http://linkedin.com/in/cbeasley0 ]

[Jeija]

Yeah, I'd be fine with JSON, that should be easy to work with and also be easy to integrate into fluffd / fluffd-client at some point. Maybe something like:

{
    "<input>" : {
        "<index>" : {
            "<subindex>" : {
                "<specific>" : {
                    "audio" : {
                        "english" : "..."
                    },
                    "eyes" : "...",
                    "movement" : "...",
                    "other" : "..."
                }
            }
        }
    }
}

where maybe we could have some defined values for eyes and movement, e.g. "eyes" : "normal" for nothing special or "eyes" : "trophy" for that trophy animation. This structure might have to be adjusted for the DLC-file-dependent actions though (maybe have those actions in extra files for the specific DLC file versions).

[beacrea]

I think thats a solid strategy. It'll make scripting complex actions in sequence a lot easier.

On Wed, Jan 25, 2017 at 1:22 PM Florian Euchner notifications@github.com wrote:

Yeah, I'd be fine with JSON, that should be easy to work with and also be easy to integrate into fluffd / fluffd-client at some point. Maybe something like:

{ "" : { "" : { "" : { "" : { "audio" : { "english" : "..." }, "eyes" : "...", "movement" : "...", "other" : "..." } } } } }

where maybe we could have some defined values for eyes and movement, e.g. "eyes" : "normal" for nothing special or "eyes" : "trophy" for that trophy animation. This structure might have to be adjusted for the DLC-file-dependent actions though (maybe have those actions in extra files for the specific DLC file versions).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Jeija/bluefluff/pull/4#issuecomment-275206099, or mute the thread https://github.com/notifications/unsubscribe-auth/ABBX7SlYtImf6n0sjq5k8kosKnLkamCPks5rV6D9gaJpZM4Lsz-x .

--

---

Coty Beasley UX Specialist

// Contact Information p: 816.200.2689 http://tel:816-200-2689/

// Social Networks [ + Twitter http://twitter.com/beacrea ] [ + LinkedIn http://linkedin.com/in/cbeasley0 ]