Writing Speaking Text Editor Part 1

Loading...

En provenance du cours de University of California, Irvine

Toward the Future of iOS Development with Swift

74 notes

University of California, Irvine

Toward the Future of iOS Development with Swift

74 notes

Cours 5 sur 6 dans Specialization iOS Development for Creative Entrepreneurs

An introduction to the Swift programming language. This will prepare you for more extensive iOS app development and build a foundation for advanced iOS development topics. Upon completing this course, you will be able to: 1. Associate the relationship of Swift and Objective-C and their use in iOS and Mac (OS X) programming 2. Develop the ability to read and write Swift code 3. Distinguish how both programming languages can be used together in applications 4. Demonstrate how to write applications entirely in Swift with the help from several iOS programming samples 5. Determine how Swift can be used for development on new platforms such as Apple Watch and Apple TV 6. Create a working client-server iPhone application with location services that you can add to your portfolio.

À partir de la leçon

From Programmer to Developer

This week, you will take steps into really developing their first, simple iPhone project with Swift. This will introduce some topics not limited to Swift itself, but also really start looking into bigger topics for iOS application development to prepare you to write a more complex application in Week 4.

Cocoa Application Speaking Text Editor Sample11:05

Writing Speaking Text Editor Part 110:36

Writing Speaking Text Editor Part 211:02

Writing Speaking Text Editor Part 35:49

Event Driven Applications with Swift and XCode Part 110:20

Event Driven Applications with Swift and XCode Part 26:43

Event Driven Applications with Swift and XCode Part 35:43

Rencontrer les enseignants

Justin-Nicholas Toyama
UCI Extension Instructor
Lead iOS Developer at Smilefish Corporation
Frank Ayars
UCI Extension Instructor
CTO and Director of Software Development at Smilefish Corporation
Ralf Brockhaus
UCI Extension Instructor
Founder and CEO at Smilefish Corporation

[MUSIC]

So now let's write that whole application from scratch.

The first thing which we do is we open Xcode.

In Xcode we say we want to create a new Xcode project.

You create a new Xcode project.

Then you can see here all the different capabilities, right?

So we can write an Xcode application for iOS, right?

So this is an area where we'd select an iOS application.

We can write applications for the watch OS, we can write applications for the TV.

We can write applications for OS X, which is the desktop, right.

And what I want to do is here I want to write an application for

the desktop from this sample here.

So then I select I want to write a Cuckoo operation.

Remember, Cuckoo is the framework which allows us

to handle all the user interaction and

that framework is written in Objective-C and we are bridging into it.

So I say next, and I need to give it a name.

So I call that Speaking Text Editor,

let's give it a number, three.

So Ralf Brockhaus, come Smilefish, Swift.

So in programming language you can select here.

I select Swift.

I want to use storyboards, which I will explain in a minute.

And I want to create a document-based application.

By selecting that I want to create a document-based application,

I get a lot of this functionality out of the box, right?

So my sample,

or my initial template application will already have a lot of the plumbing,

a lot of the capabilities to actually read and write to the file system.

To handle multiple views from multiple documents, all that is built

already in that template, all right, so that's a great place to start.

So by sending next, it wants me to store that, I create this application,

and I bring Xcode here in to full-screen mode, right.

So next thing which we see here,

inside the application we have a few things actually out of the box, right?

So every application has an application delegate.

What happens with the application delegate is

when you select an icon of an application, whatever form,

tell the operating system to launch a certain application.

Then the operating system will launch the application, and then afterwards it will

handle all the events coming from the application, from the operating system,

going to the application, will be handled in the AppDelegate.

So it's an NSApplicationDelegate as a base class,

with a protocol which implement here and vice versa.

And then we have two functions here, application has finished launching.

So if we wanted to do something specific in that moment we could insert that

code here, or before the application terminates,

we could enter some code here which would actually then store information, right?

So that's the application delegate.

If we wanted to handle geopositioning or

anything then we would add that here to this code.

The next thing we want to look at here is the document Swift.

So because I selected that I wanted to have a document based application

the Xcode environment already created a document class here for me.

Document class inherits form NS document.

And it has a couple of functions actually already built in.

There's an initializer here, there's a function to make the window controllers,

like this function here will actually be called in the moment when I say okay,

I want to add another window, I want to open a window.

And then it will want to make a window controller for me, and

add that to our application, right, so our running application.

So this code would be executed in that moment.

Also later when I write here the code to load the data from a file or

to write the data out, then these two functions will become essential.

But we don't need to start there.

So the next thing what you want to look at is actually our view controller.

And so in our view controller, we have a function viewDidLoad,

and we have a function represented object.

I leave those functions in place for the moment.

What I want to add here is a few things.

So the first thing which I want is in our application,

we need a field where we can enter the text, right?

So somebody can either enter the text or display the text, right.

Remember we're talking about the view, we need a view component, right?

So the view component we used here,

IBOutlet, that's another thing I need to explain in a second.

So we have a variable and call this TextView and

our text views of type NSTextView.

So is that in the introduction, the beginning.

That's one more thing, and return.

So when we write the user interface, then we use actually the Interface Builder.

A tool called Interface Builder originally,

meanwhile that tool is built into Xcode, but the pre-compiler directives IBOutlet,

the IB stands for Interface Builder, they still exist, right?

And I have a variable here, and my textView is of NSTextView type, right?

And when I later write the user interface in the Interface Builder,

then I need to link up the user interface component in the view

with the user interface component in my controller.

And that's what this little dot means here.

So we have an IBOutlet to connect the interface with the controller.

And we have, this is not filled, this cycle.

Which means it has not connected at this moment, which is fine.

The next thing which I want to write is two little functions.

And those functions are functions which I want to trigger when I hit the speak

button or the stop button, right?

And so the way how I do that is,

I create an IB action, a function in this case.

SpeakButtonClicked is my function, and

the sender is a button in this casem right, an NS button.

So this is my function which is being called when somebody speaks,

when somebody wants to press the speak button.

Now, what I can do here is very quick is I can say a print, and

in this case it's like kind of something like Speak button,

Click to say something like

testView.textstring.

That's kind of tricky.

Sometimes you need to know the name of the variables, right, so in this case, and

then we need to close this and close that, and then there should be no errors.

Right, so what happens here, if somebody presses the Speak button,

then we will actually print a string.

And what we will do is we will ask our text view to give us

the string which is currently in the text view.

So the class we are working, writing is the viewController.

Right, it's that the model, the view, and the controller.

So in the view we will have the text box, and

we will have the button Speak and the button Stop.

In the controller we will have all the business logic, right.

And so if you press a button in the view, the view handles the press itself, but

then the call is being sent to the controller, and

the controller does everything that needs to be done then.

Controller does the action.

In this case the controller will ask the view, give me the text view, and

from the text view give me the string which is currently displayed, and

then I will just print it here to the console.

Now the other function which I need is

an IBAction function.

Something like StopButtonClicked,

and the sender Is also an NSButton.

and what I want to do here is

I just print stop button clicked, right?

So this is now the very initial code, right?

So find was our very initial code.

We cannot do very much, right, so we need to write our user interface.

So if I go here into our main storyboard,

there's a couple of things which happen here in our application, right.

The first thing is if I look here at how our project is set up.

Then inside our project properties, so I can do that by selecting here,

our project file itself.

Then I can see here that the menu's interface is in the file main, and so

that's the main storyboard.

In the initial scene for

the storyboard here, I have on the very top, the main menu.

So, when I created this project as a document-based project,

then it already provided me here with quite a few things.

So, given the name of the application, sub menu, the file sub menu, the edit,

the format, so this is the main menu inside my application,

I can expand that, but that's beyond this class.

I have a window controller and

the window controller controls basically all the different windows for this file.

And so each time when I open a new file, I basically call the window controller from

the storyboard and the window controller then brings up my view controller.

And in my view controller it currently just says, your document contents go here.

So what I will do is I will take this field and just delete that, right.

And now we will start to build our user interface for our application.

[MUSIC]

Explorer notre catalogue

Rejoignez-nous gratuitement et obtenez des recommendations, des mises à jour et des offres personnalisées.

Coursera propose un accès universel à la meilleure formation au monde, en partenariat avec des universités et des organisations du plus haut niveau, pour proposer des cours en ligne.

© 2019 Coursera Inc. Tous droits réservés.

Télécharger dans l'App Store

Disponible sur Google Play