Afrikaans
Akan
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranรฎ)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
We're now ready to move on to step three of our design flow here, so in step number three, we want
to think about all the different ways that we're going to interact with each thing inside of our application.
The end goal, this step is to figure out the different methods that need to be added to each of our
classes and go back to the diagram that we were looking at earlier that described all the functionality
that we wanted to see in this program.
So if you look at all these steps right, here are all the things we want to do.
It's all seeming to revolve around working with a deck of cards.
None of these functions really seem to belong to a single card by itself.
In other words, you can't really shuffle a single card.
You can't really, I don't know, find a single card with a given suit.
That doesn't make a ton of sense.
So really, I think that all these different functions or pieces of functionality that we need to add
to our application are going to be tied directly to the deck class.
So in total, I think we're going to end up with a solution like this where we've got our deck class
right here with the methods like print cards and shuffle and deal and so on.
And I don't think that we're going to quite need so much over here on the individual card side.
So with that in mind, let's take a quick pause.
We're going to come back to the next section and we're going to start working with that first function
right here where we want to have the ability to create an entire deck of playing cards.
So quick break and we'll start the implementation in the next section.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.