But, I'll take one quick stab at it. Here's an post I just made to http://www.jlptstudy.net/:
"KanjiSoft Systems announces the new JLPT Vocabulary Quiz Game for Android. It was created by a JLPT student (myself) who found study of the vocabulary lists to be super boring. This app makes a game out of it; it's multiple choice like the JLPT, but with a countdown timer and game levels. So it's a lot less boring. In fact it's borderline addictive.
It includes a long term memory system (think Anki), professional audio pronunciation in Japanese and English at levels 4 and 5, increasing levels of difficulty based on frequency of use, and original artwork by the talented artist Lin Golden. The first 100 words are free; and it's only $3.99 (the price of a coffee at Starbucks) for the full version.
Check out the version corresponding to your level at one of the following urls:
https://market.android.com/details?id=com.kanjisoft.jlpt5.free&feature=more_from_developer
https://market.android.com/details?id=com.kanjisoft.jlpt4.free&feature=more_from_developer
https://market.android.com/details?id=com.kanjisoft.jlpt3.free&feature=more_from_developer
https://market.android.com/details?id=com.kanjisoft.jlpt2.free&feature=more_from_developer
https://market.android.com/details?id=com.kanjisoft.jlpt1.free&feature=more_from_developer"
Not bad.
So, with no further ado, I'm going to get started on IOS.
Ok, so what first. I have the Tapworthy book, although for some reason I never seem to get to reading it. It would take say 8 hours, if I did an hour a day. But, technically, there's the issue of upgrading to Xcode 4. That's probably my first task. I also plan to try to get more incremental in my releases. Probably the first version will be for level 2; it will connect to the SQL Lite database; it will be free, probably, to start out. I will have the browse and srs mode. I dunno; we'll see. I should plan it out a bit. I'd like to get on an iterative release cycle.
The concern is that I don't include *enough* in the first release, and it gets a bum rap or being to minimal, then your reputation is lost, and you're app is cooked. But the whole lean startup methodology is based on "getting out of the building" and talking to customers.
Anyway, I think I ought to upgrade to Xcode 4. Let's try that now.
Oops. According this url, it now costs. $4.99. Sigh. Oh, maybe not - "unless you have already paid $99/yr for the iOS/Mac Developer’s package in which case XCode 4 is free". Yay! I think I'll use that money to get a latte!
So, how to I do this?
This is from http://developer.apple.com/xcode/
Download Xcode 4
Xcode 4 is the new version of Apple’s powerful integrated development environment for creating great apps for Mac, iPhone, and iPad. Xcode 4 includes the Xcode IDE, Instruments, iOS Simulator, and the latest Mac OS X and iOS SDKs.
Xcode 4 has a streamlined new interface that integrates UI design, coding, testing, and debugging, all within a single window. The embedded Apple LLVM compiler underlines coding mistakes as you type, and is even smart enough to fix the problems for you automatically."
There's more:
http://developer.apple.com/technologies/tools/whats-new.html
"What's New in XCode 4
Xcode is the complete toolset for building Mac OS X and iOS applications — and with Xcode 4, the tools have been redesigned to be faster, easier to use, and more helpful than ever before. The Xcode IDE understands your project’s every detail, identifies mistakes in both syntax and logic, and will even fix your code for you. Quite simply, Xcode 4 will help you write better code.
Xcode 4 has a brand new user interface, built upon proven technologies that Apple itself uses to build Mac OS X and iOS, and that have produced over a quarter million Mac OS X and iOS apps.
Single Window
Apple LLVM Compiler 2.0
New Debugger
Interface Builder is Built-in
Fix-it and Live Issues
Instruments for Xcode 4
Assistant
Version Editor
Single Window
As an experienced Xcode user, the first thing you will notice about Xcode 4 is that the many windows used to perform the development tasks you work on every day have been consolidated into a single window.
// That sounds good.
The Xcode 4 work area has several unique UI elements that make it easy to work on many different tasks, even multiple projects, without cluttering your work area. Your editor is always front and center.
Navigators
On the left side is a collection of navigators, including the list of files in your project, sorted symbols, a central search interface, issue tracking, debugging data with compressible stack traces, active and inactive breakpoints, and a persistent collection of logs. The unified navigator UI provides live filtering of content and search results, so you can focus on your current task.
Jump Bar
At the top of every editor pane is a path bar showing the relative location of your current file. Click any location in the path to immediately jump to any other file at that level. This is the Jump Bar, and it is so efficient you may wish to dedicate your entire desktop to source code, quickly jumping from file to file.
// Sounds good.
Interface Builder is Built-in
In Xcode 4, Interface Builder has been completely integrated within the Xcode IDE — there is no separate application.
Selecting an interface file (.nib/.xib) in your project will open the IB editor within Xcode. Opening the right-hand Utility area will show the full complement of interface inspectors, as well as the library of controls and UI objects. Drag a control from the library, and drop onto the canvas, to layout your Mac OS X or iOS application.
// Ok, that makes sense. I never understood why it was separate in the first place.
The best part: you can drag connections directly from the UI design to the source code. Xcode 4’s new split editor layout makes it easy to wire up your actions and outlets simply by dragging a connection to existing code — one gesture and you’re done. Don’t yet have the code ready to connect? Xcode will create a new outlet or action for you, just drag to an empty space in your source file and Xcode will generate the code.
// Ah the sweet connectors. I've got them down, at least.
Assistant
Whether writing code, or designing an interface, no change happens in isolation. Even the smallest edit can have a cascading effect throughout your project. You often need to see more than just your current file; you need to see related documents as well.
With the new Xcode Assistant, the two-pane editor layout in Xcode 4 becomes dramatically more powerful. When you turn on Assistant,
// maybe I should remember to turn it on.
the IDE will anticipate which other files you need to see, as you work. Editing a new derived class? The Assistant will show you the code for the class you are inheriting. Writing new implementation code? The Assistant will automatically show you the corresponding header.
// Nice.
When designing an interface, the Assistant will show you the appropriate controller, making drag-and-drop code connections extremely simple. Data model designing will bring up the classes that back your models — all automatically.
// It sounds good.
Apple LLVM Compiler 2.0
Apple LLVM is the next-generation compiler technology powering Xcode 4. Based on the vibrant open source LLVM.org project led by Apple engineers, the Apple LLVM compiler is modern thinking, tuned for iPhone, iPad, and the multi-core Mac.
// I had this turned on in Xcode 3. It's nice it's enabled by default.
Apple LLVM is fast. It compiles code twice as quickly as GCC, yet produces applications that also run faster. The compiler was built from the ground up as a set of highly optimized libraries, easy to extend, easy to optimize, and designed for today’s modern chip architectures. In Xcode 4, the full Apple LLVM compiler stack — from the front end parser, to the back end code optimizer — has great support for C, Objective-C, and C++.
Syntax highlighting, code completion, and every other index-driven feature is handled by the LLVM parser. If the compiler knows about a symbol, so does the Xcode IDE. C, C++, and Objective-C are all accurately understood at editing time, exactly as they are when building.
// Cool.
Fix-it and Live Issues
The Apple LLVM engine is constantly working in the background to understand your code. In the editor, the new Live Issues feature uses that understanding to alert you to coding mistakes as you type. Just like a word processor highlights spelling errors, Xcode 4 highlights common coding mistakes, without the need to click ‘build’ first.
Fix the problem automatically
Beyond just reporting errors, the IDE is intelligent enough to fix the problem for you. In many cases Xcode will not only report an error, it will present a solution as well. Click the error to see the available Fit-its, such as correcting an assignment to a comparison, repairing a misspelled symbol, or appending a missing semicolon. A single keyboard shortcut will instantly have the error repaired, and let you continue coding.
// Ok.
Fix-it is a great as-you-type companion to the rigorous testing performed by the Analyze feature. The Xcode static analyzer will walk through thousands of potential code paths, looking for places where code, while valid, would behave in unexpected ways, such memory allocation mistakes, never-hit case statements, or improperly constructed loops.
Together, Fix-it and the Xcode Analyze feature will find bugs long before your users
// That sounds good - especially the memory allocation issue.
Version Editor
The new Version editor in Xcode 4 makes it easy to see any two versions of your source code, side by side, in a live editor. More importantly, the Version editor is a new way to think of source control management in an IDE, because the comparison view is also a timeline. Drag the slider in the middle and you travel back in time through your project, comparing any two versions.
// Sounds cool. I like the slider idea.
The Version editor can also show you a detailed log of past events, and track blame for past check-ins. Complex SCM commands are managed for you behind the scenes. It is even possible to manage multiple projects within a single Xcode 4 workspace, one project managed in Subversion, the other in Git, all updated automatically.
// I'll have to set up something in subversion or Git.
New Debugger
Xcode 4 introduces LLDB, a brand new debugging engine contributed by Apple to the LLVM.org open source project. Like LLVM, the new LLDB engine is designed from the ground up to consume much less memory, and be a rocket when it comes to performance.
The new LLDB debugging engine is the perfect fit for the new Xcode 4 debugging interface. When your app is running, the navigator will show a stack trace you can expand or compress to show or hide stack frames as you debug. As you step through, you can even lock onto a single thread then click “continue” and follow that specific thread of execution. Multicore debugging in Xcode 4 is now as easy as multicore coding with blocks and Grand Central Dispatch.
// It's cool how you can follow a thread.
Instruments for Xcode 4
Instruments has a streamlined interface, complete with the new Jump Bar, and stack compression from Xcode 4’s UI. Using Xcode4’s new launch schemes, it is easier than ever to create a robust test harness to run your app in Instruments. That includes launching Instruments in “deferred mode”, keeping the data collection UI off screen and saving system resources for running and metering your application.
// I'll look into that.
New data collection instruments are also available, including OpenGL ES for tracking iPhone graphics performance, new memory allocation monitoring that can find unintended memory growth,
// That's important
Time Profiler on iOS for collecting samples with very low overhead, and complete System Trace for insight into how all system processes interact.
Instruments covers even more ground, has even lower overhead, and is more useful than ever before"
Ok, so it sounds like quite an overhaul. Hopefully it will make life easier!
This one looks important:
http://developer.apple.com/library/ios/#documentation/IDEs/Conceptual/Xcode4TransitionGuide/ExistingProject/ExistingProject.html
"Using an Existing Xcode 3 Project
If you’ve been working in Xcode 3 and have one or more Xcode 3 projects that you’d like to use in Xcode 4, this chapter tells you what you need to know to get started. After you’ve opened your projects, go to “Orientation to Xcode 4” to learn more about using Xcode 4.
Open Your Xcode 3 Project in Xcode 4
Xcode 4 can open an Xcode 3 project without difficulty.
You can open the project in any of the usual ways: Control-click the project and choose Open With Xcode.app (being sure you pick Xcode 4),
drag the project onto the Xcode 4 icon,
or choose File > Open to open the project.
You can have both Xcode 3 and Xcode 4 installed on your system at the same time without conflict.
// Ah, that's very good news.
Xcode 4 reads and builds projects created in Xcode 2.1 through the latest release of Xcode 3. Projects created with Xcode 4 can be opened and built on Xcode 3.2 and later.
You can open a project in either application, save it, then open it in the other application without invalidating the project or losing any data.
// That's also very good.
Changes you make to a project in Xcode 4 remain compatible with earlier versions of Xcode.
// Great.
See Your Groups and Files
Before going any further, you need to get oriented to the Xcode 4 workspace window. Figure 1-1 shows the Xcode 4 window newly opened with an Xcode 3 project.
// figure at the above url
The left side of the window is the navigation area, opened to the project navigator, which is similar to the Groups & Files list in the Xcode 3 project window. Figure 1-2 shows the contents of an Xcode 3 project as seen in Xcode 4.
What you see in this list is probably less surprising than what you don’t see. Missing from the Xcode 4 project navigator are these groups:
Targets
Executables
Find Results
Project Symbols
Bookmarks
SCM (source control repositories)
Smart groups
You’ll also notice that the detail view is missing from Xcode 4.
The Xcode 4 equivalents to these groups and user interface elements are described in “Orientation to Xcode 4.
// Ok. I didn't use any of them except the top three.
Replace Your Interface Builder Plug-ins
Xcode 4 provides limited support for Interface Builder 3 plug-ins. Specifically, you can build a project with Interface Builder plug-in dependencies, but you can’t edit the nib files. When you try to open a nib file with plug-in dependencies, Xcode 4 displays a dialog suggesting that you update the file (Figure 1-3). If you agree, Xcode converts the class of custom objects built with plug-ins to the nearest AppKit class. If the conversion isn’t possible, Xcode 4 provides a detailed error message. In that case, you must remove the plug-in dependency using Interface Builder 3 before you can edit the nib file in Xcode 4.
// I don't think I had IB plug-ins, but I'm not sure.
Keep Your Xcode 3 Preferences
Xcode 4 copies your Xcode 3 settings for the Text Editing, Fonts and Colors, Indentation, and SCM preferences. However, changes you make to these preferences in Xcode 4 are not copied back to Xcode 3.
Xcode 4 ignores your Xcode 3 General, Code Sense, Building, Distributed Builds, Debugging, Key Bindings, File Types, Source Trees, and Documentation preferences. Similar Xcode 4 features start with Xcode 4 defaults. Changing settings in Xcode 4 does not affect your settings for these preferences in Xcode 3.
// Not a biggie, I just did one project in it.
Check Out a Working Copy
If your Xcode project is in a Git or Subversion repository, you can check out your project from the repository and open it in Xcode. Use the following procedure to connect to a repository:
In the Welcome to Xcode window you see on startup (or when you choose Window > Welcome to Xcode), click Connect to a repository. Alternately, in the Repositories pane of the Organizer window (referred to hereafter as the repositories organizer), click the plus sign (+) at the bottom of the navigator pane and choose Checkout or Clone Repository.
In the Checkout or Clone dialog, enter the path to the repository you want to clone or check out.
image: ../Art/repositories_clone_1.png
// Actually, I'll be checking in. I kind of want to learn git, but going subversion will probably be faster because
// I already know it, somewhat.
Fill in the name you want to use for the repository as displayed in the Organizer window and click Clone (for Git) or Checkout (for Subversion).
image: ../Art/repositories_clone_2.png
In the Save As dialog, specify the name and location you want to use for the working copy and click Clone (for Git) or Checkout (for Subversion).
In the confirmation dialog, click Open to open the new working copy in an Xcode workspace window (for Git) or Show in Finder to see the new working copy in the Finder (Subversion).
For Git, you’re done. For Subversion, click on the name of the new repository in the repositories organizer and fill in the paths to the trunk, branches, and tags directores. If your Subversion server requires authentication, fill in the user name and password as well.
image: ../Art/repositories_config_svn.png
See “Repositories, Snapshots, and Archives” for more information about source control in Xcode 4.
Modernize Your Project
When you open a project, Xcode 4 evaluates it to see whether there are any settings that should be updated. This feature provides an easy way to make sure that your projects conform to the latest SDKs and best practices.
Open the issue navigator (Figure 1-4) to see whether anything in your project needs to be updated. You can also select the project in the project navigator and choose Editor > Check for Outdated Settings, or choose the project from the the drop-down issues menu at the right end of the jump bar.
// Ok - Editor, Check for Outdated setting.
If the issue navigator lists modernization issues, click the issue to see a dialog that explains the updates that should be made (Figure 1-5). Deselect any checkboxes for settings you don’t want to change, then click Perform Changes to update the project to optimize it for Xcode 4.
// Sounds easy enough.
After you have clicked Perform Changes, whether you choose to make all the changes or not, Xcode does not show the warning again. To rerun the check, select your project in the project navigator and choose Check for Outdated Settings from the Editor menu.
// Work with Multiple Related Projects
A major new feature of Xcode 4 is the addition of a container for multiple projects that you can use to group Xcode projects and other files that are related. This container is referred to as an Xcode workspace. All the projects in the workspace share the same build directory. Putting your related projects in the same workspace affords you several benefits.
// I'll be using this for sure, later
For example:
One project can use the products of another project while building.
If one project depends on the products of another in the same workspace, Xcode can detect this and automatically build the projects in the correct sequence.
Because all the files in one project are visible to all the other projects in the workspace, you don’t need to copy shared libraries into each project folder separately.
Indexing is done across the entire workspace, extending the scope of content-aware features such as code completion and refactoring.
// Ok.
A project can be included in more than one workspace or removed from a workspace without affecting the project. The workspace file itself merely contains pointers to the projects and other files that the workspace includes, plus a minimal amount of data such as schemes stored in the workspace (see “Select a Scheme”). The pointers to the source files, included libraries, build configurations, and other data are stored in the project files.
// Ok.
If you have two or more related projects, use the following procedure to create a workspace and add the projects to it:
If Xcode 4 is not open, start it. You can ignore or cancel the startup screen.
Choose File > New > New Workspace and name the new workspace.
In the New Workspace dialog, specify the location for the workspace file and the name of the workspace. If your projects are in the same directory, it might be convenient to put the workspace file in there as well. To avoid possible confusion with your projects, give the workspace a unique name. Click Save.
// Ok.
Drag projects from the project navigator of other Xcode 4 windows or from the Finder to the project navigator of the new workspace. When dragging from the Finder, be sure to drag the project file (
image: ../Art/drag_proj_to_wkspc.png
// I'll review this when I actually do it.
If you’ve set up your build configuration with explicit references between your projects, the build will continue to behave as it did before. If you used to build one project and then import the product into the other project before you built it, you can remove the product from the project that imports it, because Xcode 4 discovers such implicit dependencies and builds in the correct sequence. If you don’t want one project to use the product or files in another project that’s in the same workspace, you need to adjust your build settings accordingly. See “Set Build Settings for Each Target” for help in finding and understanding the build settings interface in Xcode 4.
Before you build, be sure you’ve created the scheme or schemes you need. See “Select a Scheme” and “Customize Executables.”
// Ok, I'll look into this later.
Creating a New Xcode 4 Project
If you want to start a new software development undertaking using Xcode 4, you need to first decide whether you need a single Xcode project or multiple related projects. For a simple application or utility, a single project should suffice. However, if you have several related executables that need to link against a custom library, you probably want at least a separate project for the library and another for the executables, and possibly a separate project for each executable. In that case, see “Create a New Workspace.”
// I'll probably go with creating a new workspace, because it's going to be a multiple libraries with a single executable.
// Then again, I might save it till I need it.
Orientation to Xcode 4
Once you’ve got your projects open in Xcode 4, you can start writing code. This chapter describes many of the features of Xcode 4 that are located in different places, or used somewhat differently, from the same features in Xcode 3. It also describes a couple of features that are new in Xcode 4. For information in the debugging features of Xcode 4, see “Debugging and Analyzing Your Code.” For changes in the workflow of designing user interfaces using Xcode 4, which has a fully integrated Interface Builder, see “Designing User Interfaces in Xcode 4.”
Much of Your Project’s Content Is in New Locations
The following sections tell you where in the Xcode 4 workspace window to find information that was in your Xcode 3 Groups & Files list. Bookmarks and source control repositories, along with other information, are in the Organizer window. See “Organize Projects and Devices” for more information about the Organizer window."
Ok, we're sort of at the point where we really have to have the new xcode up and running to follow this tutorial. Since it's not a problem to download it separately, let's just go ahead and do that.
Just go to this site...
http://developer.apple.com/xcode/
Enter your apple id. What is it?
Hmmm...it's throwing me onto the developer registration page. I think I have some old emails from them, it should have the correct name.
Ok, got it. Click the link...uh. Access denied. When did I join? It was this year, I should still be valid. What's the problem?
Googling ...strange - it takes me to some kind of documentation site for Apple.
Ok, here's the problem:
"https://discussions.apple.com/thread/2777854?start=0&tstart=0"
"yeah, that's a bug on their web site. You need to agree to this first before you can download:
http://developer.apple.com/membercenter/index.action#updateAgreement
PS. That's quite an agreement too. Has anyone actually read thru it?"
Ok, now it's downloading. 4.29 gig - at the panera rate, it's going to be a while! 76 KBPS = 75 * 8 = 600 Kbps, right? I get 3 meg at home.
It's up to 90 KBPs...ok, I'm going to wrap this up for now. We'll pick it up again when the download's complete.
No comments:
Post a Comment