For the groups talking about OSC

[Onna-no-hito]

three chapters give mention to OSC--

Phoenix (Game Design) will be covering it in-depth, followed by Caitlin/Pierre (Hardware) and Eva's Project Breakdown. You guys should check in with each other, depending on your specific use-case, you can perhaps reference Phoenix's chapter/section without repeating the same text.

[evsc]

Absolutely, my plan was to wait with most code details until i see which other chapters i can reference.

On Tue, Feb 4, 2014 at 9:08 AM, Onna-no-hito notifications@github.comwrote:

three chapters give mention to OSC--

Phoenix (Game Design) will be covering it in-depth, followed by Caitlin/Pierre (Hardware) and Eva's Project Breakdown. You guys should check in with each other, depending on your specific use-case, you can perhaps reference Phoenix's chapter/section without repeating the same text.

Reply to this email directly or view it on GitHubhttps://github.com/openframeworks/ofBook/issues/6 .

[phoenixperry]

Cool. How about this. We'll cover what OSC is and how to use it with Touch OSC (we might even make a small osc app to deploy. Exploring!) We will avoid arduino and hardware networking. Sound cool? Thanks guys!

[arturoc]

perhaps we could write a chapter about network only, i wouldn't mind writing something generic explaining the difference between tcp and udp and what's osc

once that's there using the addons is pretty direct so people that use osc in the project breakdowns can point to that chapter for a more in depth explanation

[roymacdonald]

Arturo, that would be super usefull. :) I think that there should be a networking chapter, as there should be one to cover each aspect of OF.

Pheonix, you could try using the ofxGui osc sync as it is already there and it is super easy to use. There are some examples about how to use it in examples/gui.

best

Roy Macdonald +569 8248 8478

On Tue, Feb 4, 2014 at 7:37 PM, arturo notifications@github.com wrote:

perhaps we could write a chapter about network only, i wouldn't mind writing something generic explaining the difference between tcp and udp and what's osc

once that's there using the addons is pretty direct so people that use osc in the project breakdowns can point to that chapter for a more in depth explanation

Reply to this email directly or view it on GitHubhttps://github.com/openframeworks/ofBook/issues/6#issuecomment-34116065 .

[caitlinmorris]

a networking chapter would be really helpful! it would probably work well to just reference that from the hardware chapter, and expand on anything hardware-specific.

On Wed, Feb 5, 2014 at 4:54 AM, Roy Macdonald notifications@github.comwrote:

Arturo, that would be super usefull. :) I think that there should be a networking chapter, as there should be one to cover each aspect of OF.

Pheonix, you could try using the ofxGui osc sync as it is already there and it is super easy to use. There are some examples about how to use it in examples/gui.

best

Roy Macdonald +569 8248 8478

On Tue, Feb 4, 2014 at 7:37 PM, arturo notifications@github.com wrote:

perhaps we could write a chapter about network only, i wouldn't mind writing something generic explaining the difference between tcp and udp and what's osc

once that's there using the addons is pretty direct so people that use osc in the project breakdowns can point to that chapter for a more in depth explanation

Reply to this email directly or view it on GitHub< https://github.com/openframeworks/ofBook/issues/6#issuecomment-34116065>

.

Reply to this email directly or view it on GitHubhttps://github.com/openframeworks/ofBook/issues/6#issuecomment-34135541 .

[phoenixperry]

Oh good to know. I have a little make me a button now function I have been using but adding in an add on there might be fun. Will add ons have been discussed already in the book?

[pierrep]

I was thinking of a Networking chapter when I mentioned OSC, so +1 to that! I thought OSC/Networking would be useful when mentioning hardware as often you need that to hook various devices up together

[tpltnt]

Is this issue still at hand or can it be closed?

[tpltnt]

I went through the networking chapter and also improved its OSC section (see #138). I am going to give this issue a moratorium until 2015-06-01. If nobody speaks up, i am going to close this issue then.

[tpltnt]

Nobody spoke up, closing the issue according