Android Developer Days is reloading for 2013

Posted by Unknown Selasa, 26 Maret 2013 0 komentar
Android Developer Days(ADD) is now reloading for 2013. ADD 2013 will take place on June 14/15, 2013 in METU Cultural and Convention Center, Ankara, Turkey
ADD 2013 is targeted to be the one of the biggest international tech related community organization in EMEA. The first ADD was on May 21/22, 2012. There were 700 participants and more than 30 speakers.  ADD 2013,  June 14/15, 2013,  will have more participants, more fun, more networking and more inspiration. 
Take a look at the About, Call for submissions and Participation Form.

ADD is a community conference organized by:  




You can join the conference with the followings:

  • Presentations that is 15-20 minutes or 40-45 minutes long.
  • Quickie: 10 minute presentation in small rooms.
  • Poster: You can show your applications in a place dedicated for posters.
  • Workshop: Presentations with hands on coding, 40 minutes long.
Indicate your contribution in OpenConf and please indicate how much your presentation is going to take when submitting it to OpenConf Deadline of Call for Submissions is 1st May 2013.
Subjects:

  • Future Technologies
  • Mobile World
    • Future of Mobile World
    • New Generation Mobile Devices (Project Glass)
  • Android OS
    • Future Versions
    • Android in Different Architectures
    • Android in Different Areas(Industry, Defense, Home Electronics etc.)
  • Android App Development
    • New Features and Capabilities
    • App Development Best Practises
    • Android SDK Tools
    • UI(User Interface) / UX (User Experience) Design
    • App Monetization
      • Ad Integration
      • In-app Billing
    • User Statistics
  • Android NDK
  • Cross Platform App Development Frameworks
  • HTML5
  • Javascript
  • Game Development
  • Google TV
  • Google Playstore
  • Communication Solutions (NFC, Bluetooth, Wi-fi)
  • 3G, 4G Wide Band Communication
  • Cloud
    • Google Cloud Messaging for Android
    • Google App Engine
  • Augmented Reality
  • Social Media
  • Location Based Services and Maps
  • Mobile Education (Fatih Project)
  • Mobile Payment
  • Security
  • Arduino
  • Software Development Methodologies
  • Success Stories
  • GWT





Baca Selengkapnya ....

Implementing Singletons for the iOS platform

Posted by Unknown Jumat, 08 Maret 2013 0 komentar
The Singleton design pattern is one of the most frequently used design pattern when developing for the iOS platform. It is a very powerful way to share data across different parts of an iOS application without having to explicitly pass the data around manually.

Overview

Singleton classes play an important role in iOS as they exhibit an extremely useful design pattern.  Within the iOS SDK, the UIApplication class has a method called sharedApplication which when called from anywhere will return the UIApplication instance that is associated with the currently running application.

How to implement the Singleton Class

You can implement the Singleton class in Objective-C as follows:

 MyManager.h


@interface MySingletonManager : NSObject {
NSString *someProperty;
}


@property (nonatomic, retain) NSString *someProperty;

+ (id)sharedManager;

@end

MyManager.m

#import "MySingletonManager.h"

@implementation MySingletonManager

@synthesize someProperty;

#pragma mark Singleton Methods

+(id) sharedManager {
static MySingletonManager *sharedMySingletonManager = nil;
static dispatch_once_t onceToken;
dispatch_once(&onceToken, ^{
sharedMySingletonManager = [[self alloc] init];

});
return sharedMySingletonManager;
}

- (id)init {
if (self = [super init]) {
someProperty = @"Default Property";
}
return self;
}

- (void)dealloc {
// should never be called, but included here for clarity
}

@end


The above code fragment defines a static variable called sharedMySingletonManager which is then initialized once and only once in sharedManager.  The way that we ensure that it is only created once is by using the dispatch_once method from the Grand Central Dispatch (GCD).  This is thread safe and handled entirely by the OS so you do not need to worry about it at all.

If you rather not use GCD, then you can the following code fragment for sharedManager:

Non-GCD Based 

+ (id)sharedManager {
@synchronized(self) {
if (sharedMySingletonManager == nil)
sharedMySingletonManager = [[self alloc] init];
}
return sharedMySingletonManager;
} 
 
Then, you can reference the Singleton from anywhere by calling the function below:

Referencing the Singleton

MySingletonManager *sharedManager = [MySingletonManager sharedManager];
Happy Singleton'ing!   If you find this post useful, then mention me in the comments.

View more documents from tasneemsayeed.

Baca Selengkapnya ....
Trik SEO Terbaru support Online Shop Baju Wanita - Original design by Bamz | Copyright of android photography.