openframeworks / ofBook

openFrameworks community book
705 stars 201 forks source link

For groups talking about classes, comparing languages #7

Closed Onna-no-hito closed 9 years ago

Onna-no-hito commented 10 years ago

A couple chapters discuss how classes work: JTNimoy (C++ Basics), Rui (OOPs)

and several chapters give mention to C++ versus other langauges: JTNimoy (C++ Basics), Rui (OOPs), Lukasz (iOS), Arturo (Android--java)

just wanted you guys to check-in with each other to possibly save yourselves time and not repeat the same explanations.

some questions: is it more fitting for Rui to talk about classes when explaining OOP? should the OOP chapter come before the C++ chapter?

Josh-- do you cover differences between Obj.C and Java? obviously Lukasz and Arturo-- you get more in-depth as far as use case but for the basics differences of the languages maybe Josh has that covered?

ruxrux commented 10 years ago

Hey Onna-no-hito

Thanks for sending this! We def should discuss this, My idea is that the OOP's chapter would take a more hands on approach -OF based examples on what classes/objects are in a practical setting - for beginners = a little concept talk but mostly a pragmatic usage of them. It seems Josh's is pure C++ ( non-OF ) based. Josh? What do u say? Should we integrate ? Keep it separate?

Looking forward Rui

sent while moving >>

On Feb 4, 2014, at 10:32 AM, Onna-no-hito notifications@github.com wrote:

A couple chapters discuss how classes work: JTNimoy (C++ Basics), Rui (OOPs)

and several chapters give mention to C++ versus other langauges: JTNimoy (C++ Basics), Rui (OOPs), Lukasz (iOS), Arturo (Android--java)

just wanted you guys to check-in with each other to possibly save yourselves time and not repeat the same explanations.

some questions: is it more fitting for Rui to talk about classes when explaining OOP? should the OOP chapter come before the C++ chapter?

Josh-- do you cover differences between Obj.C and Java? obviously Lukasz and Arturo-- you get more in-depth as far as use case but for the basics differences of the languages maybe Josh has that covered?

— Reply to this email directly or view it on GitHub.

arturoc commented 10 years ago

i will just mention how to interface from java <-> c++ in android so there shouldn't be anything already said in other chapters

On 02/04/2014 04:40 PM, ruxrux wrote:

Hey Onna-no-hito

Thanks for sending this! We def should discuss this, My idea is that the OOP's chapter would take a more hands on approach -OF based examples on what classes/objects are in a practical setting - for beginners = a little concept talk but mostly a pragmatic usage of them. It seems Josh's is pure C++ ( non-OF ) based. Josh? What do u say? Should we integrate ? Keep it separate?

Looking forward Rui

sent while moving >>

On Feb 4, 2014, at 10:32 AM, Onna-no-hito notifications@github.com wrote:

A couple chapters discuss how classes work: JTNimoy (C++ Basics), Rui (OOPs)

and several chapters give mention to C++ versus other langauges: JTNimoy (C++ Basics), Rui (OOPs), Lukasz (iOS), Arturo (Android--java)

just wanted you guys to check-in with each other to possibly save yourselves time and not repeat the same explanations.

some questions: is it more fitting for Rui to talk about classes when explaining OOP? should the OOP chapter come before the C++ chapter?

Josh-- do you cover differences between Obj.C and Java? obviously Lukasz and Arturo-- you get more in-depth as far as use case but for the basics differences of the languages maybe Josh has that covered?

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/openframeworks/ofBook/issues/7#issuecomment-34071908.

roymacdonald commented 10 years ago

hey rui, I'll also talk a bit about classes and OOP in my chapter while explainig h and cpp files, so we shoul defenitely be in sync. best

Roy Macdonald +569 8248 8478

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

i will just mention how to interface from java <-> c++ in android so there shouldn't be anything already said in other chapters

On 02/04/2014 04:40 PM, ruxrux wrote:

Hey Onna-no-hito

Thanks for sending this! We def should discuss this, My idea is that the OOP's chapter would take a more hands on approach -OF based examples on what classes/objects are in a practical setting - for beginners = a little concept talk but mostly a pragmatic usage of them. It seems Josh's is pure C++ ( non-OF ) based. Josh? What do u say? Should we integrate ? Keep it separate?

Looking forward Rui

sent while moving >>

On Feb 4, 2014, at 10:32 AM, Onna-no-hito notifications@github.com wrote:

A couple chapters discuss how classes work: JTNimoy (C++ Basics), Rui (OOPs)

and several chapters give mention to C++ versus other langauges: JTNimoy (C++ Basics), Rui (OOPs), Lukasz (iOS), Arturo (Android--java)

just wanted you guys to check-in with each other to possibly save yourselves time and not repeat the same explanations.

some questions: is it more fitting for Rui to talk about classes when explaining OOP? should the OOP chapter come before the C++ chapter?

Josh-- do you cover differences between Obj.C and Java? obviously Lukasz and Arturo-- you get more in-depth as far as use case but for the basics differences of the languages maybe Josh has that covered?

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub https://github.com/openframeworks/ofBook/issues/7#issuecomment-34071908.

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

julapy commented 10 years ago

thanks for bringing this up @Onna-no-hito, glad theres a master brain out there steering all these streams of thought.

i can always drop or shorten the C++ and Obj-C section based on what has been covered in previous chapters, no biggie. but also, even if two people cross over a little on the same topic, it can't hurt as its always good to hear how another person's perspective on the same topic.

jtnimoy commented 10 years ago

@all On the greater subject of overlapping writing, I think that is perfectly okay in so many ways. I say as a teacher that there is nothing like diversified repetition to get important subjects into the student's mind, in case they missed it. Having said that, we should be both aware that the overlaps exist, and be reviewing one another's approaches on the same thing so that we can provide a coordinated "multiple perspective" on the same thing, as well as refer back to one another's different perspectives.

@Onna-no-hito yes i will compare objective-C, Java, and C# in just a few sentences, and will point the reader directly to Lukasz's chapter. Thanks again, btw for overseeing these potential redundancies.

I will not talk about interfacing between those systems as arturo mentioned. "bridging" is an advanced topic.

@all

I do not go far into OOP, i'm only intro'ing it then advertising Rui's chapter. You'll notice in my writing that I make use of std::cout which is an object, then I gracefully skip over the depth of that, and just tell the reader "it prints some text into the console", nothing more.

The difference between my chapter and others is that I'm attempting to get the reader up to speed in a very fundamental way so that we can get them into OF as soon as possible, and so they'll be able to find their way around the basic template without feeling like it's the first of the C++ language that they've ever seen.

My preference in teaching is to demonstrate any and all of these concepts graphically, using graphics calls and not printf(). That is why I would suggest Rui's chapter on OOP be moved until after the reader has compiled and run SimpleExample.

In the meantime, I plan on keeping my basic OOP intro with the intention of merely preparing the reader to recognize what the testApp:: means in void testApp::setup(), and what the :public ofBaseApp means in class testApp : public ofBaseApp. My explanations of these things intend to be heart-warming birds eye views of the general concept, with a big arrow pointing to Rui's chapter for anyone who cannot wait ;) They will not be super wordy, and they will not go into great detail at all. It's more like "you'll see this when you go into OF. Ask Rui."

@roy please help me out and tell me which chapter you have so I can check out what angle you are taking when you introduce H and CPP files. I am willing to cover H and CPP files in basics of C++ language as provided in my outline, so let's see if there's a possible merge here.

On Tue, Feb 4, 2014 at 5:04 PM, lukasz karluk notifications@github.comwrote:

thanks for bringing this up @Onna-no-hitohttps://github.com/Onna-no-hito , glad theres a master brain out there steering all these streams of thought.

i can always drop or shorten the C++ and Obj-C section based on what has been covered in previous chapters, no biggie. but also, even if two people cross over a little on the same topic, it can't hurt as its always good to hear how another person's perspective on the same topic.

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

roymacdonald commented 10 years ago

Hey Josh, I totally agree with you.

My chapter is 03_setup_and_project_structure

I have to go throug the h and cpp files to explain the OF structure. I just wanted to explain OOP in a very simple way, so I could do that and then point to rui's chapter for a thorough explanation.

@ofZach I see that you also mention the h and cpp files in the intro chapter. How shall we deal with it?

best

arturoc commented 10 years ago

yes i also agree we shouldn't care that much about overlapping, as long as we don't write the same chapter twice :) i also think that different point of views on the same topic can help a lot understanding things

tpltnt commented 9 years ago

Do you people think this is still an issue? If not I suggest to close this issue. @Onna-no-hito could you do that?

tpltnt commented 9 years ago

This thread seems to be stale since over a year. It also does not have an actionable outcome (anymore). Hence I close it.