Saturday, January 17, 2015

Android Game Development Help

hirparagroup.blogspot.com

Develop breaks down how to choose the right game engine for you
With the proliferation of games platforms over the last few years and the onset of the new generation of consoles with the PS4, Xbox One and Wii U, picking the right game engine can be tricky.
Luckily, Develop has put together a quick guide to 16 of the top game engines for 2014. The development platforms below span across a number of platforms and costs range from free, subscription and all the way up to the top pricing tiers.
Unreal Engine 4
Company: Epic Games
Platforms: Android, HTML5, iOS, Linux, Mac, Oculus, PC, PS4, SteamOS, Xbox One
www.unrealengine.com


Epic’s new-gen game development platform Unreal Engine 4 has officially been released to all developers, who can now get access on a $19 a month subscription with five per cent of gross revenue from any game sales going to Epic.

Devs also have access to the engine and complete C++ source code hosted on GitHub. The tech includes the Blueprint visual scripting system, the Persona animation system and Matinee timeline-based machinima and cinematic system.
Unity
Company: Unity Technologies
Platforms: Android, BlackBerry, iOS, Linux, Mac, PS3, PS4, Xbox 360, Xbox One, Windows 8 (coming soon)
www.unity3d.com


Unity 5 has just been announced for pre-order, and includes the integration of Geomerics’ Enlighten tech, Imagination Technologies’ PowerVR Ray Tracing tech, SpeedTree and revamped audio tools.

In the meantime, 4.3 features new 2D development tools and character animation tech Mecanim, and is free to Xbox One and Wii U developers. PlayStation 4 developers will also soon have the chance to get early access to the engine.
CryEngine
Company: Crytek
Platforms: Android, iOS, PC, PS3, PS4, Xbox 360, Xbox One, Wii U
www.cryengine.com


CryEngine is one of the most powerful game engines available to developers, and, with Crytek keen to welcome indies, developers can now sign up to use the engine for $10 a month, royalty-free.

Features include the engine’s recently announced physically-based shading, geometry cache and
image-based lighting. The new subscription option is set to be available from May. Devs can still access the free CryEngine SDK under its current terms despite the new model.
GameMaker
Company: YoYo Games
Platforms: Android, Browser, iOS, Mac, PC, PS3, PS4, Vita, Windows Phone
www.yoyogames.com


Developed by YoYo Games, a wealth of titles have been created through 2D development platform GameMaker, including Gunpoint, Hotline Miami, Spelunky and Super Crate Box.

Last month it was announced that GameMaker: Studio would be free for all PlayStation platforms. The tech has support for PSN features and licenced peripherals including controllers, control inputs and cameras. For those developing on other platforms, a host of licences are available.
Havok Vision Engine
Company: Havok
Platforms: Android, iOS, PS3, Vita, Wii, Wii U, Windows 8, Xbox 360
www.havok.com


this cross-platform game engine has been around for years, and provides an object-oriented C++ API. The development tech is optimised for last-gen consoles and PC.

The full game engine licence includes licences for Havok Vision, AI and Behvaior as well as Autodesk’s UI solution Scaleform illumination middleware Beast. The toolset ships with the source code and 3ds Max and Maya exporters.

As of yet the tech does not support PS4 and Xbox One.
Project Anarchy
Company: Havok
Platforms: Android, iOS, PC, Tizen
www.projectanarchy.com


Project Anarchy is a complete end-to-end game engine for mobile that comes with a free licence allowing developers to release titles to iOS, Android and Tizen.

The tech integrates Havok’s suite of game development technology including the Havok Vision Engine, collision detection and physical simulation tech Physics, Animation Studio and AI.

There are also expanded licences that come with a cost, including a PC exporter, available for developers who want more from the engine.
ShiVa
Company: ShiVa
Platforms: Android, Blackberry, iOS, Linux, Mac, PS3, SteamOS, Vita, Wii, Windows, Windows Phone 8,
Xbox 360
www.shivaengine.com


ShiVa is on the comeback trail and is gearing up for the launch of ShiVa 2 for Windows, Mac and Linux.

Version 1.9.2 is available to use now however, and features a Lua-based scripting language with debugging tools, a C++ plug-in system for custom engine extensions and a terrain editor with vegetation layers, texture painting and an ocean module. Other features include game controller support, video streaming and texture data streaming.
BigWorld
Company: Wargaming
Platforms: Browser, PC
www.bigworldtech.com


This game engine focuses on the development of sprawling MMOs such as Wargaming’s World of Tanks. In fact, such was its reliance, the developer bought the tech firm outright in 2012.

BigWorld can still be licenced by other studios creating MMOs, desktop and browser games however, and they can take advantage of the BigWorld server to help handle a single, persistent world, as well as harness terrain sculpting and painting tools, a multi-channel terrain texturing system, and its own lighting system.
Leadwerks
Company: Leadwerks
Platforms: Linux, Mac, PC
www.leadwerks.com


In its third iteration, as well as supporting PC development, Leadwerks is championing another rising platform, Linux. Last year the middleware outfit raised $42,358 to bring native development from Leadwerks to Linux, which was released last month, along with version 3.1 of the Standard Edition.

The engine includes an OpenGL 4.0 deferred renderer with a uniform lighting model, a built-in script editor with debugger, code stepping and syntax highlighting. The Leadwerks editor includes built-in level design tools, Navmesh pathfinding and a visual flowgraph. Published games include Hoodwink and My Whacky Moles.
App Game Kit
Company: The Game Creators
Platforms: Android, iOS, Mac, PC
www.appgamekit.com


This cross-platform development tool focuses on mobile, PC and Mac support. Code can be written in AGK BASIC once and then compiled to each platform without any changes being made to the source code.

Programmers can also create their apps in C++, and The Game Creators have developed a C++ library that mimics the Tier 1 BASIC script, enabling developers to write applications that compile to all compatible platforms.

The App Game Kit can be licenced for $59.99 or tested through a free trial. AGK V2, which raised £33,000 on Kickstarter, is also due for release later this year.
FPS creator Reloaded
Company: The Game Creators
Platforms: Oculus Rift, PC
www.fpscreator.thegamecreators.com


Another game engine from The Game Creators, FPS Creator Reloaded is designed as an affordable game engine for both entry-level and professional developers.

The toolset integrates AI, physics, shaders, weapon systems, real-time shadows and lighting, integrated debugging and a library of assets. Recently the firm also added virtual reality support via the Oculus Rift for the tool, while the engine has also been successfully greenlit for a release on Steam.

The game engine is currently going through a beta period, and interested developers can make various pledges of up to $100 to unlock new features.
Reach3dx
Company: Gamebase
Platforms: Android, Flash, HTML5, iOS
www.reach3dx.com


Reach3dx is a brand newcross-platform game engine from Gamebase, the creators of Gamebryo, another development platform that has been used in numerous titles such as El Shaddai and Epic Mickey 2: The Power of Two.

Unlike that engine however, Reach3dx will focus on mobile and web platforms and is based on the OpenFL framework and Haxe. The new tech is still based on the modular architecture of past engines such as the aforementioned Gamebryo.

Gamebase has said it wants to decrease development times so users can get their games to market faster. An open beta will be live throughout April.
HeroEngine
Company: Idea Fabrik
Platforms: PC
www.heroengine.com


The HeroEngine is designed for massively multiplayer and online games from any genre and has been used in titles such as EA’s ambitious Star Wars: The Old Republic.

The dev platform can be licenced for $99 a year and includes a suite of integrated middleware such as SpeedTree, FMOD, Umbra dPVS, Awesomium and FaceGen.

Devs can also use the HeroCloud to script code, sculpt terrain and create physics systems in a single online development environment, allowing team members to work remotely in real-time from any location. The tech has been licenced by companies such as EA and ZeniMax Online.
Marmalade
Company: Marmalade
Platforms: Android, BlackBerry, iOS Mac, Windows, Tizen
www.madewithmarmalade.com


Cross-platform SDK Marmalade lets devs deploy code across multiple platforms from a single code base.
The tech uses C++, but also provides alternative solutions for devs looking to use Lua, HTML or Objective-C.

Marmalade has released a host of other handy tools including Web Marmalade, enabling developers to create hybrid apps using HTML5, CSS and JavaScript, and Marmalade Quick, a RAD?tool for creating 2D games and apps.

The recent full release of Marmalade Juice to developers enables creators to take native iOS titles and deploy them to Android.
Turbulenz
Company: Turbulenz
Platforms: Browser
biz.turbulenz.com


An engine for HTML5 game development, last year Turbulenz went open-source and allowed developers to use the tech to create their games free of charge. This means games makers can develop titles, use the developer hub to test and iterate on titles, and self-publish and monetise online, all for free.

Games hosted on the Turbulenz website will be subject to a 70/30 revenue share split, but this does not affect other platforms. Among a plethora of features, the tool features physics, collision and animation systems, optimisations for multiplayer and social networking and supports up to 7.1 surround sound.
GameSalad
Company: Gamesalad
Platforms: Android, HTML5, iOS, Mac, Windows
www.gamesalad.com


GameSalad is a mobile games development platform that first debuted in 2009 and has been used to develop a plethora of games, including more than 65 titles featured in the Top 100 games on Apple’s US App Store.

How To Edit APK file Android Application Full tutorial

http://hirparagroup.blogspot.in/search/label/Android#
REQUIREMENTS :

Download and Install on your computer

1. JDK here

2. 7zip here or Winrar (recommended) here

3. Notepad++ here

4. Android SDK for patch 9.png until Zipalign the apk here

5. Apktool & baksmali/smali + Signer for all GB/ICS/JB ROM here

6. Apktool & baksmali/smali + Signer for all GB/ICS/JB ROM v2 here

7. Apktool & baksmali/smali + Signer for all GB/ICS/JB/KK ROM v3 (4.4 Kitkat support/optimized) here




Save or extract apktool to folder directory :

Windows XP : C:\Document and Settings\folder your computer name\here

Windows 7 : C:\User\folder your computer name\here






CREDITS & BIG THANKS TO :

- Brut.all for apktool
- Team Reject for Quick baksmali/smali file
- Yorzua for Sign apk file
- Rizal Lovins for support me
- pantrif13







1. How to Decompile and Recompile *.jar file or classes.dex


- Copy *.jar file to apktool folder (make sure is the same folder). for example : android.policy.jar

- Open android.policy.jar using Winrar or 7zip and extract classes.dex file

- Drag & drop classes.dex to Quick-Baksmali.cmd (decompile process)

Screenshot example for Baksmaling/decompile classes.dex using drag & drop method :



- wait and you will see a folder with the name "classout"

- now you can start editing smali file on classout folder (use Notepad++ for editing it)

- After editing is complete, Drag & drop classout folder to Quick-Smali.cmd (recompile process)

Screenshot example for Smaling/recompile classout folder using drag & drop method :



- After recompile is complete, there will be a file with a name "new-classes.dex"

- Open android.policy.jar using Winrar or 7zip

- Rename new-classes.dex to classes.dex, and Drag & drop to android.policy.jar with normal compression

- finally, push back android.policy.jar into the system your device. push manual using root explorer/similar application or make a flashable zip.



2. How to Decompile and Recompile *.apk file


a. Copy framework-res.apk to apktool folder (make sure is the same folder).
(Attention : to edit other default apk on system/app like Contacts.apk, Phone.apk. MusicPlayer.apk etc.. needed framework 2. for example : twframework-res.apk)

b. Copy other *.apk you want to edit to apktool folder. for example : GreenRockers.apk

c. Open Command Prompt.bat

d. Decompile and install framework

Code:
apktool if framework-res.apk
apktool d GreenRockers.apk
Screenshot example for installing framework and decompiling apk :


if your apk is Contacs.apk, Phone.apk, Camera.apk etc.. follow this guide :

Code:
apktool if framework-res.apk
apktool if twframework-res.apk
apktool d Settings.apk
Screenshot example for installing framework 2 and decompiling apk :



e. wait and you will see a folder with the name "GreenRockers or Settings"

f. now you can start editing png, xml, even smali file

g. After editing is complete, Now Recompile

Code:
apktool b -f -d GreenRockers
or 

Code:
apktool b -f -d Settings
Screenshot example for decompiling dan recompiling apk :


h. After recompile is complete, go to GreenRockers or Settings folder, Open dist folder and open GreenRockers.apk or Settings.apk using Winrar/7zip

i. Open Original GreenRockers.apk or Settings.apk Using Winrar/7zip

j. Drag & drop META-INF folder and android.manifest.xml (if you not edit android.manifest.xml), also lib folder if there in Original GreenRockers.apk to Modified GreenRockers.apk or Modified Settings.apk on dist folder.

Screenshot example for Drag & drop META-INF folder etc :



k. Now Sign apk, example :

Code:
java -jar SignApk.jar testkey.x509.pem testkey.pk8 GreenRockers.apk GreenRockers_signed.apk
(Attention : Sign apk is only for 3rd Party apps, you can sign apk from system/app. but not all apk on system/app support)

l. Rename GreenRockers_signed.apk to GreenRockers.apk

m. Zipalign the apk

Code:
zipalign -fv 4 GreenRockers.apk GreenRockers-new.apk
n. Rename GreenRockers-new.apk to GreenRockers.apk

o. finally, push back xxxxxx.apk into the system your device. push manual using root explorer/similar application or make a flashable zip.



3. How to Zipalign the *.apk


1. Download and Install Android SDK (if you've downloaded, do not need to download again)

2. Go to C:\Program Files\Android\android-sdk\tools

3. Search + copy zipalign.exe and draw9patch.bat then paste in the c:\windows\here

4. Open cmd and typing this code (For example : Zipalign SystemUI.apk) :

Code:
zipalign -fv 4 SystemUI.apk SystemUI-new.apk

Monday, December 15, 2014

how to hide WhatsApp last seen feature in Android ?

whatsapp tricks and tips
How to Hide WhatsApp last seen feature in Android. WhatsApp App, one of the widely used messenger which came up with newly added features i.e. to hide last seen status, after Facebook takeover it. Hiding last seen is a desirable and pleasing feature, as it will make users comfortable for not being observed as active at any given instant of time. With hiding last seen, you can also hide your profile status and photo from people who are not in your contact list. This update made a positive mark from WhatsApp group, regarding privacy and security concern. Here is way to do the same: Hide WhatsApp last seen feature in Android Hide WhatsApp last seen feature in Android Hide WhatsApp last seen feature in Android Open your WhatsApp messenger. Select option, and move to Accounts. Hide WhatsApp last seen feature in Android Hide WhatsApp last seen feature in Android In Accounts Select privacy, where you can find following three options for “who can see your personal info”: 1.) Last Seen 2.) Profile Photo 3.) Status Select your options accordingly. Hide WhatsApp last seen feature in Android Hide WhatsApp last seen feature in Android Note: This change will affect immediately. With hiding the feature from the respective group of people, you will also not be allowed to see the same for the same group of people. You can also see for other WhatsApp other feature information that one should know: Manually Hide WhatsApp last seen feature in Android: You can also hide the last seen without applying the above steps, by applying the trick given below cautiously: Disable your data packet or your WiFi network before opening whats app App. Now Open WhatsApp and Read messages if any or Send messages if you want to. Just Close WhatsApp and Enable WiFi or data packet. Hiding last seen is updated in and after the WhatsApp Version 2.11.186. Users of iphone Apple, Blackberry and Windows device can also hide last seen. Try it out and let us know your experience with the added feature of WhatsApp messenger by commenting below. Your valuable comments and suggestions are always welcome.

Start Developing iOS Apps Today

Setup Start Developing iOS Apps Today provides the perfect starting point for iOS development. On your Mac, you can create iOS apps that run on iPad, iPhone, and iPod touch. View this guide’s four short modules as a gentle introduction to building your first app—including the tools you need and the major concepts and best practices that will ease your path. image: ../Art/application_design_2x.png The first three modules each end with a tutorial, where you’ll implement what you’ve learned. At the end of the last tutorial, you’ll have created a simple to-do list app. After you’ve built your first app in this guide and are considering your next endeavor, read the fourth module. It explores the technologies and frameworks you might consider adopting in your next app. You’ll be on your way to keeping your customers engaged and looking forward to the next great thing. Even though this guide takes you through every step of building a simple app, to benefit most it helps to be acquainted with computer programming in general and with object-oriented programming in particular. Get the Tools Before you can start developing great apps, set up a development environment to work in and make sure you have the right tools. image: ../Art/install_tools_2x.png To develop iOS apps, you need: A Mac computer running OS X 10.8 (Mountain Lion) or later Xcode iOS SDK Xcode is Apple’s integrated development environment (IDE). Xcode includes a source editor, a graphical user interface editor, and many other features. The iOS SDK extends the Xcode toolset to include the tools, compilers, and frameworks you need specifically for iOS development. You can download the latest version of Xcode for free from the App Store on your Mac. (You need OS X version 10.8 to download Xcode. If you have an earlier version of OS X, you need to upgrade.) The iOS SDK is included with Xcode. To download the latest version of Xcode Open the App Store app on your Mac (by default it’s in the Dock). In the search field in the top-right corner, type Xcode and press the Return key. Click Free image: ../Art/free_2x.png. Xcode is downloaded into your /Applications directory. Tutorial: Basics This tutorial takes you through the basics of what an app is, to the process of creating a simple user interface, and on to adding the custom behavior that transforms the interface into a working app. Follow this tutorial to learn the basics of iOS app development, including: How to use Xcode to create and manage a project How to identify the key pieces of an Xcode project How to add standard user interface elements to your app How to build and run your app After you finish the tutorial, you’ll have an app that looks something like this: image: ../Art/ios_simulator_add_item_vc_2x.png To keep things simple, the tutorial project has only an iPhone interface, but you use the exact same tools and techniques to develop an iPad app. This tutorial uses Xcode 5.0 and iOS SDK 7.0. Create a New Project To get started developing your app, create a new Xcode project. Xcode includes several built-in app templates that you can use to develop common styles of iOS apps, such as games, apps with tab-based navigation, and table-view-based apps. Most of these templates have preconfigured interface and source code files for you to start working with. For this tutorial, you’ll start with the most basic template: Empty Application. Working with the Empty Application template will help you understand the basic structure of an iOS app and how content gets onscreen. After you’ve learned how everything works, you can use one of the other templates for your own app to save yourself some configuration time. To create a new empty project Open Xcode from the /Applications directory. The Xcode welcome window appears. image: ../Art/welcome_to_xcode_window.pdf If a project window appears instead of the welcome window, don’t worry—you probably created or opened a project in Xcode previously. Just use the menu item in the next step to create the project. In the welcome window, click “Create a new Xcode project” (or choose File > New > Project). Xcode opens a new window and displays a dialog in which you can choose a template. image: ../Art/project_template_window_2x.png In the iOS section at the left of the dialog, select Application. In the main area of the dialog, click Empty Application and then click Next. In the dialog that appears, name your app and choose additional options for your project. image: ../Art/new_project_window_2x.png Use the following values: Product Name: ToDoList Xcode uses the product name you entered to name your project and the app. Company Identifier: Your company identifier, if you have one. If you don’t, use com.example. Class Prefix: XYZ Xcode uses the class prefix name to name the classes it creates for you. Objective-C classes must be named uniquely within your code and across any frameworks or bundles you might be using. To keep class names unique, the convention is to use prefixes for all classes. Two-letter prefixes are reserved by Apple for use in framework classes, so use something that’s three letters or longer. Choose iPhone from the Devices pop-up menu. As already mentioned, creating an app with an iPhone interface is the simplest way to start. The techniques used are the same for an iPad or universal app. Click Next. In the dialog that appears, choose a location for your project and click Create. Xcode opens your new project in a window (called the workspace window), which should look similar to this: image: ../Art/workspace_window_2x.png Get Familiar with Xcode Xcode includes everything you need to create an app. It not only organizes the files that go into creating an app, it provides editors for code and interface elements, allows you to build and run your app, and includes a powerful integrated debugger. Take a few moments to familiarize yourself with the Xcode workspace. You’ll use the controls identified in the window below throughout the rest of this tutorial. Click different buttons to get a feel for how they work. If you want more information on part of the interface, read the help articles for it—you find them by Control-clicking an area of Xcode and choosing the article from the shortcut menu that appears. image: ../Art/xcode_overview.pdf Run iOS Simulator Because you based your project on an Xcode template, the basic app environment is automatically set up for you. Even though you haven’t written any code, you can build and run the Empty Application template without any additional configuration. To build and run your app, you can use the iOS Simulator app that’s included in Xcode. As its name implies, iOS Simulator gives you an idea of how your app would look and behave if it were running on an iOS device. iOS Simulator can model a number of different types of hardware—iPad, iPhone with different screen sizes, and so on. As a result, you can simulate your app on every device you’re developing for. In this tutorial, use the iPhone Retina (4-inch) option. To run your app in iOS Simulator Choose iPhone Retina (4-inch) from the Scheme pop-up menu in the Xcode toolbar. image: ../Art/scheme_popup.pdf Go ahead and look through the menu to see what other hardware options are available in iOS Simulator. Click the Run button, located in the top-left corner of the Xcode toolbar. image: ../Art/xcode_toolbar_full.pdf Alternatively, you can choose Product > Run (or press Command-R). If this is the first time you’re running an app, Xcode asks whether you’d like to enable developer mode on your Mac. Developer mode allows Xcode access to certain debugging features without requiring you to enter your password each time. Decide whether you’d like to enable developer mode and follow the prompts. If you choose not to enable it, you may be asked for your password later on. The tutorials assume developer mode is enabled. Watch the Xcode toolbar as the build process completes. Xcode displays messages about the build process in the activity viewer, which is in the middle of the toolbar. After Xcode finishes building your project, iOS Simulator starts automatically. It may take a few moments to start up the first time. iOS Simulator opens in iPhone mode, just as you specified. On the simulated iPhone screen, iOS Simulator opens your app. (If you see a message in the Xcode debugger at this point, don't worry—you’ll address this later in the tutorial.) image: ../Art/ios_simulator_blank_2x.png As the name Empty Application implies, the template doesn’t do much—it just displays a white screen. Other templates have more complex behavior. It’s important to understand a template’s uses before you extend it to make your own app. Running the template with no modifications is a good way to start developing that understanding. After you’ve explored the app, quit iOS Simulator by choosing iOS Simulator > Quit iOS Simulator (or pressing Command-Q). Review the Source Code The Empty Application template comes with a few existing source code files that set up the app environment. Most of the work is done by the UIApplicationMain function, which is automatically called in your project’s main.m source file. The UIApplicationMain function creates an application object that sets up the infrastructure for your app to work with the iOS system. This includes creating a run loop that delivers input events to your app. You won’t be dealing with the main.m source file directly, but it’s interesting to understand how it works. To look at the main.m source file Make sure the project navigator is open in the navigator area. The project navigator displays all the files in your project. If the project navigator isn’t open, click the leftmost button in the navigator selector bar. image: ../Art/navigator_selector_bar_2x.png Open the Supporting Files folder in the project navigator by clicking the disclosure triangle next to it. Select main.m. Xcode opens the source file in the main editor area of the window, which looks similar to this: image: ../Art/main_file.pdf If you double-clicked the file, you’ll notice that it opened in a separate window. You can choose to have a file open in the main project window by clicking it once, or you can open it in a separate window by double-clicking it. The main function in main.m calls the UIApplicationMain function within an autorelease pool. @autoreleasepool { return UIApplicationMain(argc, argv, nil, NSStringFromClass([XYZAppDelegate class])); } The @autoreleasepool statement is there to support memory management for your app. Automatic Reference Counting (ARC) makes memory management straightforward by getting the compiler to do the work of keeping track of who owns an object; @autoreleasepool is part of the memory management infrastructure. The call to UIApplicationMain creates two important initial components of your app: An instance of the UIApplication class, called the application object. The application object manages the app event loop and coordinates other high-level app behaviors. This class, defined in the UIKit framework, doesn’t require you to write any additional code to get it to do its job. An instance of the XYZAppDelegate class, called the app delegate. Xcode created this class for you as part of setting up the Empty Application template. The app delegate creates the window where your app’s content is drawn and provides a place to respond to state transitions within the app. This is where you write your custom app-level code. Like all classes, the XYZAppDelegate class is defined in two source code files in your app: in the interface file, XYZAppDelegate.h, and in the implementation file, XYZAppDelegate.m. Here’s how the application object and app delegate interact. As your app starts up, the application object calls defined methods on the app delegate to give your custom code a chance to do its job—that’s where the interesting behavior for an app is executed. To understand the role of the app delegate in more depth, view your app delegate source files, starting with the interface file. To view the app delegate interface file, select XYZAppDelegate.h in the project navigator. The app delegate interface contains a single property: window. With this property the app delegate keeps track of the window in which all of your app content is drawn. Next, view the app delegate implementation file. To do this, select XYZAppDelegate.m in the project navigator. The app delegate implementation contains “skeletons” of important methods. These predefined methods allow the application object to talk to the app delegate. During a significant runtime event—for example, app launch, low-memory warnings, and app termination—the application object calls the corresponding method in the app delegate, giving it an opportunity to respond appropriately. You don’t need to do anything special to make sure these methods get called at the correct time—the application object handles that part of the job for you. Each of these automatically implemented methods has a default behavior. If you leave the skeleton implementation empty or delete it from your XYZAppDelegate.m file, you get the default behavior whenever that method is called. Use these skeletons to put additional custom code that you want to be executed when the methods are called. For example, the first method in the XYZAppDelegate.m file contains some lines of code that set up the app window and give it the white background color you saw when you ran your app for the first time. In this tutorial, you won’t be using any custom app delegate code, so go ahead and remove the code that sets the window to have a plain white background. To configure the app delegate implementation file Find the application:didFinishLaunchingWithOptions: method in XYZAppDelegate.m. It is the first method in the file. Delete the first three lines of code from that method so it looks just like this: - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions { return YES; } Xcode automatically saves the changes. Xcode continuously tracks and saves all of your work. (You can undo your changes by choosing Edit > Undo Typing.) Create a Storyboard At this point, you’re ready to create a storyboard for your app. A storyboard is a visual representation of the app’s user interface, showing screens of content and the transitions between them. You use storyboards to lay out the flow—or story—that drives your app. To see how a storyboard fits into an app, in this tutorial you create one manually and add it to your app. Unlike the Empty Application template you started with, other Xcode templates include preconfigured storyboards providing views, view controllers, and associated source code files that set up the basic architecture for an app of that type. After you’ve configured a storyboard manually, you’ll see how the pieces fit together. Then you’ll be able to start with a project template that comes with a preconfigured storyboard, which will save you some overhead. To create a new storyboard Choose File > New > File (or press Command-N). A dialog appears that prompts you to choose a template for your new file. On the left, select User Interface under iOS. Click Storyboard, and click Next. For the Devices option, select iPhone. Click Next. A dialog appears that prompts you to choose a location and name for your new storyboard. In the Save As field, name the file Main. Make sure the file is saved in the same directory as your project. image: ../Art/save_storyboard_2x.png For the Group option, select ToDoList. For Targets, select the checkbox next to ToDoList. This option tells Xcode to include the new storyboard when it builds your app. Click Create. A new storyboard file is created and added to your project. You’ll work in this file to lay out the content of your app. Now you need to tell Xcode that you want to use this storyboard as the interface to your app. When it starts up, the application object checks whether the app has a main interface configured. If it does, the application object loads the defined storyboard when the app launches. To set the storyboard as the app’s main interface In the project navigator, select your project. In the editor area of the workspace window, Xcode displays the project editor, which allows you to view and edit details about how your app is built. Under Targets, select ToDoList. image: ../Art/select_target_2x.png If the Project and Targets lists don’t appear in the project editor, click the disclosure triangle in the top-left corner of the editor pane to reveal the lists. image: ../Art/show_projects_and_targets_2x.png Select the General tab. Under Deployment Info, find the Main Interface option. Select your storyboard, Main.storyboard. Add a Scene to Your Storyboard Now that you have a storyboard, it’s time to start adding app content. Xcode provides a library of objects that you can add to a storyboard file. Some of these are user interface elements that belong in a view, such as buttons and text fields. Others define the behavior of your app but don’t themselves appear onscreen, such as view controllers and gesture recognizers. To start, you’ll add a view controller to your storyboard. A view controller manages a corresponding view and its subviews. You’ll learn more about the roles of views and view controllers in the next chapter, App Development Process. To add a view controller to your storyboard In the project navigator, select Main.storyboard. Xcode opens the storyboard in Interface Builder—its visual interface editor—in the editor area. Because the storyboard is empty, what you see is a blank canvas. You use the canvas to add and arrange user interface elements. Open the Object library. The Object library appears at the bottom of the utility area. If you don’t see the Object library, you can click its button, which is the third button from the left in the library selector bar. (If you don’t see the utility area, you can display it by choosing View > Utilities > Show Utilities.) image: ../Art/object_library.pdf A list appears showing each object’s name, description, and visual representation. Drag a View Controller object from the list to the canvas. If you can’t find the object titled View Controller in the Object library, filter the list of objects by typing in the text field below the list. Type View Controller, and you see only view controller objects in the filtered list. At this point, the storyboard in your app contains one scene. The arrow that points to the left side of the scene on the canvas is the initial scene indicator, which means that this scene is loaded first when the app starts. Right now, the scene that you see on the canvas contains a single view that’s managed by a view controller. If you run your app in iOS Simulator, this view is what you see on the device screen. It’s useful to run your app in iOS Simulator to verify that everything is configured correctly. Before doing that, add something to the scene that you’ll be able to see when you run the app. To add a label to your scene In the Object library, find the Label object. If you entered text in the filter text field, you may need to clear its contents before you can see the Label object. You can also type Label in the filter field to find the Label object quickly. Drag a Label object from the list to your scene. image: ../Art/dragging_label_2x.png Drag the label to the center of the scene until horizontal and vertical guides appear. Stop dragging the label when you see something like this: image: ../Art/centering_text_field.pdf The guides mean that the label is now centered horizontally and vertically. (The guides are visible only when you’re dragging or resizing objects next to them, so they will disappear when you let go of the label.) Double-click the text of the label to select it for editing. Type Hello, World! and press Return. If necessary, recenter the label. Test Your Changes Running your app in iOS Simulator is a great way to periodically check that everything is working the way you expect. At this point your app should launch and load the scene you created in your main storyboard. Click the Run button in Xcode. You should see something like this: image: ../Art/ios_simulator_test_your_changes.png If you don’t see the label you added, make sure the storyboard you created is configured as the main interface for your app and make sure you’ve removed the code that creates the empty white window in the app delegate. If necessary, go back and repeat the steps for those sections. This is also a good time to experiment with what you can add to an interface. Explore Interface Builder by changing: The text of the label The font size of the label The color of the text Build the Basic Interface Now that you can put content in a scene, it’s time to build the basic interface for the scene that lets you add a new item to the to-do list. To add an item to the to-do list, you need a single piece of information: the item name. You get this information from a text field. A text field is the interface element that lets a user input a single line of text using a keyboard. But first, you need to remove the label you added earlier. To remove the label from your scene Click the label to select it. Press the Delete key. The label is removed from the scene. If this wasn’t what you wanted, you can choose Edit > Undo Delete Label. (Every editor has an Edit > Undo command to undo the last action.) Now that you again have a blank canvas, create the scene for adding a to-do item. To add a text field to your scene If necessary, open the Object library. Drag a Text Field object from the list to your scene. image: ../Art/dragging_text_field.jpg Drag the text field so that it’s positioned about two-thirds from the bottom of the screen. image: ../Art/moving_text_field.jpg If necessary, click the text field to reveal the resize handles. You resize a UI element by dragging its resize handles, which are small white squares that appear on the element’s borders. You reveal an element’s resize handles by selecting it. In this case, the text field should already be selected because you just stopped dragging it. If your text field looks like the one below, you’re ready to resize it; if it doesn’t, select it on the canvas. image: ../Art/resize_handles.pdf Resize the left and right edges of the text field until you see vertical guides appear. Stop resizing the text field when you see something like this: image: ../Art/extending_text_field.pdf Although you have the text field in your scene, there’s no instruction to the user about what to enter in the field. Use the text field’s placeholder text to prompt the user to enter the name of a new to-do item. To configure the text field’s placeholder text With the text field selected, open the Attributes inspector image: ../Art/inspector_attributes_2x.png in the utility area. The Attributes inspector appears when you select the fourth button from the left in the inspector selector bar. It lets you edit the properties of an object in your storyboard. image: ../Art/attributes_inspector.pdf In the Attributes inspector, find the field labeled Placeholder and type New to-do item. To display the new placeholder text in the text field, press Return. Checkpoint: Run your app in iOS Simulator to make sure that the scene you created looks the way you expect it to. You should be able to click inside the text field and enter a string using the keyboard. image: ../Art/ios_simulator_add_item_vc_2x.png Recap You’re now well on your way to being able to create a basic interface using storyboards. In the remaining tutorials, you’ll learn more about adding interaction to your interface and writing code to create custom behavior. The chapters between the tutorials guide you through the concepts that you’ll put into practice while working on your app.

Saturday, December 13, 2014

How To Create Android Application , Android Application developement Example

Android Application Help

Want to make an app for iPhone, iPad, Android or Windows? These app tutorials will tell you how. 

 

 

You've got a great idea but you need some help – discover how to make an app for Android, iOS or Windows with these easy-to-follow tutorials for everyone from amateurs to pros.
In a world where smartphone use is rising exponentially, the opportunities to make a name for yourself, not to mention a ton of money, by turning your app idea into reality are huge. So whether you're building for Android or iOS, there are several tutorials here to help you. We start with Android...

How to make an Android app

 

Create a Project with Android Studio


  1. In Android Studio, create a new project:
    • If you don't have a project opened, in the Welcome screen, click New Project.
    • If you have a project opened, from the File menu, select New Project.

  2. Figure 1. Configuring a new project in Android Studio.
  3. Under Configure your new project, fill in the fields as shown in figure 1 and click Next. It will probably be easier to follow these lessons if you use the same values as shown.
    • Application Name is the app name that appears to users. For this project, use "My First App."
    • Company domain provides a qualifier that will be appended to the package name; Android Studio will remember this qualifier for each new project you create.
    • Package name is the fully qualified name for the project (following the same rules as those for naming packages in the Java programming language). Your package name must be unique across all packages installed on the Android system. You can Edit this value independently from the application name or the company domain.
    • Project location is the directory on your system that holds the project files.
  4. Under Select the form factors your app will run on, check the box for Phone and Tablet.
  5. For Minimum SDK, select API 8: Android 2.2 (Froyo). The Minimum Required SDK is the earliest version of Android that your app supports, indicated using the API level. To support as many devices as possible, you should set this to the lowest version available that allows your app to provide its core feature set. If any feature of your app is possible only on newer versions of Android and it's not critical to the app's core feature set, you can enable the feature only when running on the versions that support it (as discussed in Supporting Different Platform Versions).
  6. Leave all of the other options (TV, Wear, and Glass) unchecked and click Next.
  7. Under Add an activity to your project, select Blank Activity and click Next.
  8. Under Describe the new activity for your project, leave the fields as they are and click Finish.
Your Android project is now a basic "Hello World" app that contains some default files. Take a moment to review the most important of these:
app/src/main/res/layout/activity_my.xml
This is the XML layout file for the activity you added when you created the project with Android Studio. Following the New Project workflow, Android Studio presents this file with both a text view and a preview of the screen UI. The file includes some default settings and a TextView element that displays the message, "Hello world!"
app/src/main/java/com.mycompany.myfirstapp/MyActivity.java
A tab for this file appears in Android Studio when the New Project workflow finishes. When you select the file you see the class definition for the activity you created. When you build and run the app, the Activity class starts the activity and loads the layout file that says "Hello World!"
app/src/res/AndroidManifest.xml
The manifest file describes the fundamental characteristics of the app and defines each of its components. You'll revisit this file as you follow these lessons and add more components to your app.
app/build.gradle
Android Studio uses Gradle to compile and build your app. There is a build.gradle file for each module of your project, as well as a build.gradle file for the entire project. Usually, you're only interested in the build.gradle file for the module, in this case the app or application module. This is where your app's build dependencies are set, including the defaultConfig settings:
  • compiledSdkVersion is the platform version against which you will compile your app. By default, this is set to the latest version of Android available in your SDK. (It should be Android 4.1 or greater; if you don't have such a version available, you must install one using the SDK Manager.) You can still build your app to support older versions, but setting this to the latest version allows you to enable new features and optimize your app for a great user experience on the latest devices.
  • applicationId is the fully qualified package name for your application that you specified during the New Project workflow.
  • minSdkVersion is the Minimum SDK version you specified during the New Project workflow. This is the earliest version of the Android SDK that your app supports.
  • targetSdkVersion indicates the highest version of Android with which you have tested your application. As new versions of Android become available, you should test your app on the new version and update this value to match the latest API level and thereby take advantage of new platform features. For more information, read Supporting Different Platform Versions.
See Building Your Project with Gradle for more information about Gradle.
Note also the /res subdirectories that contain the resources for your application:
drawable-hdpi/
Directory for drawable objects (such as bitmaps) that are designed for high-density (hdpi) screens. Other drawable directories contain assets designed for other screen densities. Here you'll find the ic_launcher.png that appears when you run the default app.
layout/
Directory for files that define your app's user interface like activity_my.xml, discussed above, which describes a basic layout for the MyActivity class.
values/
Directory for other XML files that contain a collection of resources, such as string and color definitions. The strings.xml file defines the "Hello world!" string that displays when you run the default app

 

Wednesday, December 10, 2014

40+ Adsense Partner Sites To Get Instant Approval


Adsence approval tricks



There are many blogger who want to get approval in Google’s lucrative adsense program and hence I am today providing you with those host-partner sites.
These are websites that have more than 100,000 daily visits so when you open an account and utilize them will obviously give you an upper edge but will also get you approved in Google Adsense.
Youtube.com
Blogger.com
Kongregate.com
Hubpages.com
Yousaytoo.com
Stockvault.com
Devilsworkshop.org
Digitaljournal.com
Shoutmeloud.com
Promojunkie.com
Flixya.com
Treadhunter.com
Bukisa.com
Techmaish.com
Docstoc.com
Freerangestock.com
Webanswers.com
Blip.tv
Dotnetspider.com
Squidoo.com
Xomba.com
Istockphoto.com
Mylot.com
Newsvine.com
Suite101.com
Expertscolumn.com
En.fotolia.com
Infobarrel.com
Funadvice.com
Ether.com
Talkshoe.com
Cafepress.co.uk
Reverbnation.com
Redbubble.com
Triond.com
Shetoldme.com
Journalhome.com
Seekyt.com
Snipsly.com
Jamendo.com
Helium.com
Epinions.com
Slicethepie.com
Submit.shutterstock.com
123rf.com
Alamy.com
Use these sites and share your experience below in comments. You can advise me if one or more sites are working or not when you use it. Feel free to provide us with your observations.

Hirpara Group





Hirpara Group   

1.My Website
2.Youtube Channel
 

Pooja Bhatt ends her 11 yrs marriage with hubby Manish Makhija

Now actor-director Pooja Bhatt's marriage with former VJ Manish Makhija has hit the rock bottom. The duo has ended their 11 year of nuptial bond by mutually parting ways. Pooja Bhatt took to a micro-blogging site and posted, "To all those who care and especially those that don't my husband Munna and Me have decided to part ways after 11 glorious years of marriage."
She further added, "Our split as some might call it is amicable and we hold each other in the highest esteem for now and forever. The reason I explain Is because we are both part of the public domain. Our friends,well wishers and foes are free to now speculate. : )"
In fact, the trouble in their paradise started to occur long back. It's only now that the couple, especially Pooja has come forth to announce about the break-up!

Blog Archive

increase adsense earning

Package
URL OR WEB ADDRESH

Live Traffic Feed