how to switch between layers using animations to make it look like you are changing screens… we will be using a ViewFlipper widget in the layout XML.
1. Create a new Android project, unless you already have one
2. Create a new Activity class that extends android.app.Activity.
create an Activity, and to switch to another Activity (think of it as another screen) on the click of a button.
1. Create a new Android project – or you might already have one created.
2. Add a new Class that extends android.app.Activity. You need a total of two classes that extend Activity. You will switch from one Activity to another.
The main criteria of this post is to help you add a cool effect called the “cover flow/open flow” effect to any of your iphone apps. This is cool in two ways actually. One it adds animation kind of effect to your app and the other, its very easy to build too.
I got to learn about this effect when I was working on my “pianos” app where in i’ll have bunch of animals to select which would be displayed as a menu using this “cover flow” effect. Once a particular animal is selected your piano view for that animal comes up. My piano app will be out soon and you can check that out. The source for this post is the link displayed below.
“http://fajkowski.com/blog/2009/08/02/openflow-a-coverflow-api-replacement-for-the-iphone/”
Based on his post I have simplified things further. He uses “flicker API” for the images in his “cover flow” but in my version I would just use my own library of images so that this post would target the beginners. To begin with we should work with Photoshop a bit to generate your images. If your not acquainted with photoshop, never mind not a problem at all. This particular task with the photoshop just wants you to scale the images you use in your library to size “225 * 225″ applying “Free Transformation”. That’s all what you got to do. Once you got your images then your ready to go.
Creating the project
Firstly Create a new “view based” project with project name like “CoverFlow”.
Once you create a new project you would arrive at a screen shown below with predefined classes already generated for you.
One of the most powerful aspects of any mobile application for a 3G phone is that it can connect to the Internet. By connecting to the Internet the application can offer much more value to the user since it becomes an interface for a web-based component, e.g. using Twitter’s API to create a Twitter application so that you can get your Twitter updates without having to open the mobile browser. The most common way of interfacing with a web-based component is by using web services in XML format.
While trying to developer my own app which reads a web service from my own server, I ran into a lot of difficulties in implementing the client that consumes the web service. Android does not have libraries for XPath handling of XML documents, so it makes deciphering XML data a little bit more difficult. From what I’ve read online the Android team is currently working on including such libraries in future versions.
After some digging around I found an amazing link that shows different methods for consuming an XML file in Android and parsing through it without the use of XPaths. The link is this: Working with XML on Android. To start off, this link is an absolute must-read. Everything that I am going to write in my post here relates to this link. The code offered on that webpage uses polymorphism to show you 4 different methods of working with XML data. It provides a fully-functional Android application and all the source code for it. The source code can be found here: AndroidXML.zip.
My post today will concentrate on how to customize the code from the application in the above link, in order to read and parse your own XML data. If you are a Java pro, you might not need this post. My Java is a little rusty, so I needed some time to figure out exactly what I had to change and where in order to get this to work with my own web service XML. Now that I’ve figured it out, I thought I’d share it. In my next post I will give the simplified version of this code – where there is no polymorphism, and thus there are only the minimum number of classes needed to implement this XML-reading solution.
Context.getAssets (). Open ("sample.txt")
WebView.loadUrl ("file: / / / android_asset / sample.html");
Step 1:
Start Xcode and make a New Project – Select View-based Application – I call it AirPrinting.
Each iPhone or iPod Touch has a Unique Device Identifier (UDID),
which is a sequence of 40 letters and numbers that is specific to your
device. It’s like a serial number but much harder to guess. It
will look something like this:
2b6f0cc904d137be2e1730235f5664094b831186.
Your iPhone can only install programs that are approved by Apple.
Applications in the App Store have been approved by Apple for general
distribution, but beta customers get to try the app before it’s in the
store. We register your UDID with Apple so they can approve our
application especially for your iPhone.
You can copy/paste your UDID from iTunes or email it directly from
your device by using a free app from the App Store.
With web services-based SOA now being deployed across Global 2000
enterprises, transmitting attachments such as MRI Scans, X-Rays, Design
Documents and Business Contracts using SOAP messages has become a
common practice. SOAP Message Transmission Optimization Mechanism (MTOM),
is a W3C Recommendation designed for optimizing the electronic
transmission of attachments. Through electronic transmission of
documents, corporations can realize significant cost savings and better
service levels by eliminating the use of postal mail. Paper-based
manual tasks can be replaced with simple and efficient electronic
processes where binary data can be transmitted between organizations
through standards such as MTOM.
MTOM provides an elegant mechanism of efficiently transmitting
binary data, such as images, PDF files, MS Word documents, between
systems. The Figure below shows the steps involved in transmitting data
between a Consumer and Producer using MTOM.
The Consumer application begins by sending a SOAP Message that contains complex data in Base64Binary encoded format. Base64Binary data type represents arbitrary data (e.g., Images, PDF files, Word
Docs) in 65 textual characters that can be displayed as part of a SOAP
Message element. For the Send SOAP Message Step 1 in the Figure above, a sample SOAP Body with Base64Binary encoded element <tns:data> is as follows:
@interface RootViewController : UITableViewController{
NSMutableArray* drinks;
}
@property (nonatomic, retain) NSMutableArray* drinks;
@end(RootViewController.m)@synthesize drinks;
-(void)dealloc{
[drinks release];
[super dealloc];
}
to do the same thing, but not add them to your iPhoto library. 
@interface ScrollViewExampleViewController : UIViewController {
IBOutlet UIScrollView *scrollview;
IBOutlet UITextField *textField1;
IBOutlet UITextField *textField2;
BOOL displayKeyboard;
CGPoint offset;
UITextField *Field;
}
@property(nonatomic,retain) IBOutlet UIScrollView *scrollview;
@property(nonatomic,retain) IBOutlet UITextField *textField1;
@property(nonatomic,retain) IBOutlet UITextField *textField2;
Step 3: Now you add MediaPlayer.framework in your framework folder.Only shows up in the iPhone SDK frameworks folder, at /Developer/platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS2.0.sdk/System/Library/Frameworks.#import <MediaPlayer/MediaPlayer.h>#import <UIKit/UIKit.h> @interface Tabbar1ViewController : UIViewController { MPMoviePlayerController *moviePlayer; NSURL *movieURL; }
@interface WebBrowserTutorialAppDelegate : NSObject {What we have done is to make the main AppDelegate a delegate for the UIWebView as well.
webView.delegate = self;
curl http://kernel.org/pub/software/scm/git/git-1.7.1.tar.gz -O tar xzvf git-1.7.1.tar.gz cd git-1.7.1 make configure ./configure --prefix=/usr/local NO_MSGFMT=yes make prefix=/usr/local all sudo make install
Git should be installed on your OS-X now, which you can verify by issuing:
git --version command in Terminal. However, it’s a good idea to also pre-configure the default username and e-mail for your Git installation:git config --global user.name "Your Firstname Lastname" git config --global user.email "username@example.com" git config --global --list
I personally, also like to set:
git config --global color.ui "auto"
EditorController.h:@interface EditorController : UIViewController {
UITextView *messageTextView;
}
@property (nonatomic, retain) UITextView *messageTextView;
@end- (id) init {
if (self = [super init]) {
// define the area and location for the UITextView
CGRect tfFrame = CGRectMake(10, 10, 300, 100);
messageTextView = [[UITextView alloc] initWithFrame:tfFrame];
// make sure that it is editable
messageTextView.editable = YES;
// add the controller as the delegate
messageTextView.delegate = self;
}- (BOOL)textView:(UITextView *)textView shouldChangeTextInRange:(NSRange)range
replacementText:(NSString *)text
{
// Any new character added is passed in as the "text" parameter
if ([text isEqualToString:@"\n"]) {
// Be sure to test for equality using the "isEqualToString" message
[textView resignFirstResponder];
// Return FALSE so that the final '\n' character doesn't get added
return FALSE;
}
// For any other character return TRUE so that the text gets added to the view
return TRUE;
}typedef enum {
UIKeyboardTypeDefault,
UIKeyboardTypeASCIICapable,
UIKeyboardTypeNumbersAndPunctuation,
UIKeyboardTypeURL,
UIKeyboardTypeNumberPad,
UIKeyboardTypePhonePad,
UIKeyboardTypeNamePhonePad,
UIKeyboardTypeEmailAddress,
UIKeyboardTypeAlphabet = UIKeyboardTypeASCIICapable
} UIKeyboardType;Good grief. Seven distinct keyboard types? Bah. (Yes, 9 appear in the list, but UIKeyboardTypeDefault and UIKeyboardTypeAlphabet are just aliases for other types. Quiet you.) Some choices were obvious — my email address field will probably use UIKeyboardTypeEmailAddress, for instance — but some other choices are kind of head-scratchers. One of the fields wants a quantity, for example. Which keyboard should I use for that bad boy? UIKeyboardTypeNumberPad? But what if I need units, like “cups”? Can I get an alphabetic keyboard from UIKeyboardTypeNumberPad? I didn’t know, and tragically neither does Google; there aren’t any good breakdowns of iPhone keyboard types on the first few pages. Hitting up some blogs finally pointed me to some more Apple documentation, but even that still didn’t answer all my questions.
NSString *string = [NSString stringWithFormat:@"%@ %@", @"Hello", @"World"];
NSLog(@"%@", string);
or
NSString *string1 = @”Hello”;
NSString *string2 = @”World”;
string1 = [string1 stringByAppendingString:string2];
stringForKey:@"SBFormattedPhoneNumber"]; NSLog(@"Phone Number: %@", phoneNumber);
- (void)applicationDidFinishLaunching:
(UIApplication *)application {
UINavigationController *navController =
[[UINavigationController alloc] initWithRootViewController:viewController];
// Override point for customization after app launch
[window addSubview:navController.view];
[window makeKeyAndVisible];
}2. Open the SimpleTable code(you can grab it from here). Right click on classes folder in Xcode and select ‘Add > New File…’.
/Developer/Applications/Xcode:
Base64 is an encoding for transferring binary data in 7-bit text. Originally used in email, it is also used for binary encoding data in HTML files. Another common use for Base64 is in HTTP Basic Access Authentication where it is used to transfer login details (which might not be printable characters).
The key library for handling Base64 on the Mac is normally libcrypto (the OpenSSL library), so it's a little disappointing that libcrypto isn't available on the iPhone.
On the Mac, you can handle simple encoding tasks like base64 encoding with OpenSSL on the command line:
echo "Base64 encode this text." | openssl enc -base64
gives the encoding result:
QmFzZTY0IGVuY29kZSB0aGlzIHRleHQuCg==
The reverse is handled in the following manner:
echo "QmFzZTY0IGVuY29kZSB0aGlzIHRleHQuCg==" | openssl enc -d -base64
giving
Base64 encode this text.
As you'd expect, doing the same work in code takes a little more typing. First, we're using a library, so we need to include it (in your Project's Build Settings under Other Linker Flags add the flag -lcrypto). Once that's done, you should be able to use the following method in a category on NSData:
#include#include - (NSString *)base64EncodedString { // Construct an OpenSSL context BIO *context = BIO_new(BIO_s_mem()); // Tell the context to encode base64 BIO *command = BIO_new(BIO_f_base64()); context = BIO_push(command, context);
Step 1. Open up our alertview project.. if you haven’t done that yet please watch the tutorial on that and then comeback
Alertview Tutorial:CLICK HERE
Step 2. Navigate to the (***ViewController.m)- the stars just represent the name
Step 3. Navigate to the alertview action (where the code is) it should look something like this
-(IBAction)pushAlert {
UIAlertView *alert = [[UIAlertView alloc] initWithTitle:@”This is a alert view” message:@”Watever” delegate:nil cancelButtonTitle:@”Cancel” otherButtonTitles:nil];
[alert show];
[alert release];
}
In the header file (***ViewController.h)
-(IBAction)pushAlert;
In the (***ViewController.m)
-(IBAction)pushAlert {
UIAlertView *alert = [[UIAlertView alloc] initWithTitle:@”This is a alert view” message:@”Hi my name is bob. I like to code random projects for the iPhone” delegate:nil cancelButtonTitle:@”Cancel” otherButtonTitles:nil];
[alert show];
[alert release];
}
1) Open up XCode > New Project > View Based Application
2) Call it SwitchViews and hit Save If you look under your resources folder, you can see Xcode already gives you new NIB (.xib) files, and already interconnects them
3) Now we need to add another NIB file, but first lets add the class files first. Click File > New File UIViewController subclass. Call it NextView.m and hit Save. (check the box that says create .h too)
4) It will be added under your classes folder. Now, under your Classes folder, click on SwitchViewsViewController.h to open up the header file.
5. Type this -(IBAction)next:(id)sender;
6) Double click on SwitchViewsViewController.xib
Finally think about branding/skinning/white labeling. I have seen so many projects add this late on in the project. It’s far easier to incorporate this from the start rather than add later.
