React Native Introduction

React Native         

                          

What is ReactNative?

         React native is a javascript framework for writing real,natively  create mobile application for  android and ios .It use react framework and offer large amount of inbuild component and APIs.

React native helps you to create real and exciting mobile app with the help of java script only.Which is suppor bot plateform Android and IOS.

With use of ReactNative Development time save.

React native is released by Facebook.React Native is supported by huge community today.

ReactNative is set of component for both ios and android to build a mobile application.

For creating Reactnative mobile application you just need to know about,HTML,CSS and JAVASCRIPT.

React Native is very fast in performance.reduse development time ,

also save run time ,and build a excelent UI. 

Why is the REACT Native Framework Used?

  With use of react native framework you can create both         UI Android and IOS plateform.

React native reduse develpoment time.

The first reason to use reactnative  framework is that the developer write one set of code  (Java Script code ) for enjoy the performance of react native application.

ReactNative application is a cross pralteform .

 Cross-Platform Usage: 

  Resct native initially invented for ios development  and huge success of react natiove for ios facebook provide support of android platform also.

In future Reactnative provide support for window and TvIos also.

Application Flow Chart

The following graphic illustrates how data flows throughout the system:

1. The index.php serves as the front controller, initializing the base resources needed to run CodeIgniter.
2. The Router examines the HTTP request to determine what should be done with it.
3. If a cache file exists, it is sent directly to the browser, bypassing the normal system execution.
4. Security. Before the application controller is loaded, the HTTP request and any user submitted data is filtered for security.
5. The Controller loads the model, core libraries, helpers, and any other resources needed to process the specific request.
6. The finalized View is rendered then sent to the web browser to be seen. If caching is enabled, the view is cached first so that on subsequent requests it can be served.

Android ImageSlider Or ViewPager Tutorial

Android ViewPager Or ImageSlider Tutorial

ImageSlider slides one screen to another with on slide. To implements ImageSlider we use ViewPager ,you need to inherit view pager class with PagerAdapter.

First you define the viewpager in xml file give it an id.

Then In Adapter class we need to override following methods of PagerAdapter class.

1. isViewFromObject(View, Object): This method checks the view whether it is associated with key and returned by instantiateItem().
2. instantiateItem(ViewGroup, int): This method creates the page position passed as an argument.
3. destroyItem(ViewGroup, int, Object): It removes the page from its current position from container. In this example we simply removed object using removeView().
4. getCount(): It returns the number of available views in ViewPage

Now, After this find the viewpager in main activity and set the Adapter hit the run button.

To watch our tutorial video please click on below video link-

•  Codeigniter Directory Structure:

• 
  
• As shown in the figure, whenever a request comes to CodeIgniter, it will first go to index.php page.
• In the second step, Routing will decide whether to pass this request to step-3 for caching or to pass this request to step-4 for security check.
• If the requested page is already in Caching, then Routing will pass the request to step-3 and the response will go back to the user.
• If the requested page does not exist in Caching, then Routing will pass the requested page to step-4 for Security checks.
• Before passing the request to Application Controller, the Securityof the submitted data is checked. After the Security check, the Application Controller loads necessary Models, Libraries, Helpers, Plugins and Scripts and pass it on to View.
• The View will render the page with available data and pass it on for Caching. As the requested page was not cached before so this time it will be cached in Caching, to process this page quickly for future requests.
• 
  

Directory Structure

The image given below shows the directory structure of the CodeIgniter.

CodeIgniter directory structure is divided into 3 folders −

• Application
• System
• User_guide

Application

As the name indicates the Application folder contains all the code of your application that you are building. This is the folder where you will develop your project. The Application folder contains several other folders, which are explained below −

• Cache − This folder contains all the cached pages of your application. These cached pages will increase the overall speed of accessing the pages.
• Config − This folder contains various files to configure the application. With the help of config.php file, user can configure the application. Using database.php file, user can configure the database of the application.
• Controllers − This folder holds the controllers of your application. It is the basic part of your application.
• Core − This folder will contain base class of your application.
• Helpers − In this folder, you can put helper class of your application.
• Hooks − The files in this folder provide a means to tap into and modify the inner workings of the framework without hacking the core files.
• Language − This folder contains language related files.
• Libraries − This folder contains files of the libraries developed for your application.
• Logs − This folder contains files related to the log of the system.
• Models − The database login will be placed in this folder.
• Third_party − In this folder, you can place any plugins, which will be used for your application.
• Views − Application’s HTML files will be placed in this folder.

System

This folder contains CodeIgniter core codes, libraries, helpers and other files, which help make the coding easy. These libraries and helpers are loaded and used in web app development.

This folder contains all the CodeIgniter code of consequence, organized into various folders −

• Core − This folder contains CodeIgniter’s core class. Do not modify anything here. All of your work will take place in the application folder. Even if your intent is to extend the CodeIgniter core, you have to do it with hooks, and hooks live in the application folder.
• Database − The database folder contains core database drivers and other database utilities.
• Fonts − The fonts folder contains font related information and utilities.
• Helpers − The helpers folder contains standard CodeIgniter helpers (such as date, cookie, and URL helpers).
• Language − The language folder contains language files. You can ignore it for now.
• Libraries − The libraries folder contains standard CodeIgniter libraries (to help you with e-mail, calendars, file uploads, and more). You can create your own libraries or extend (and even replace) standard ones, but those will be saved in the application/libraries directory to keep them separate from the standard CodeIgniter libraries saved in this particular folder.

User_guide

This is your user guide to CodeIgniter. It is basically, the offline version of user guide on CodeIgniter website. Using this, one can learn the functions of various libraries, helpers and classes. It is recommended to go through this user guide before building your first web app in CodeIgniter.

Beside these three folders, there is one more important file named “index.php”. In this file, we can set the application environment and error level and we can define system and application folder name. It is recommended, not to edit these settings if you do not have enough knowledge about what you are going to do.

Google Play Policy part-2

Google Play -Developer Policy Center

4.Privacy, Security, and Deception

   a.User Data

          Developer  must be transparent in how you handle user data.for example -information collected from user including device information developer need to secure all the information .if disclose information and missuse then app will be remove from google play store.

Personal and sensitive user data collection purposes directly related to providing and improving the features of the apps with user permission.

app must be disclose inside app and google play also how use to use user data.

in app must include a request for user data content.

  b. Device and Network Abuse

          Google play didnot allow that interface  with disturb ,damage or access in unauthorise manner the user's device.other device or computer,server or network.

c.Malicious Behavior

       Google play not allow apps that steal data ,secretly monitor or harm users,or otherwise malicious.

that are also not allow- Viruses, trojan horses, malware, spyware or any other malicious software.

5.Monetization and Ads

  a.Payments 

      Here are some examples of products supported by Google Play In-app Billing:

       *Virtual game products, including coins, gems, extra lives or turns, special items or equipment, characters or avatars, additional levels or playtime.

       *Some of the app functionality or content  that will be not available in free version .

      *Subscription services, such as streaming music, video, book, or other media services.

*Cloud software products, including data storage services.

b.Subscriptions and Cancellations 

If a user cancels a subscription purchased from an app on Google Play, google policy that the user will not receive a refund for the current billing period, but will continue to receive their subscription content for the remainder of the current billing period, 

c.Ads -

 Goolge play  allow ads only be displayed within the app  serving.goolge play consider ads served in your app as part of your app.

Note:- For read all the policy of google play please click blow link https://ixorainfotech.blogspot.com/2018/11/google-play-store-privacy-policy-to.html

Thankyou.

Codeigniter tutorials for beginners

what is codeigniter framework

CodeIgniter is based on the Model-View-Controller (MVC) development pattern. MVC is a software approach that separates application logic from presentation. ... A View will normally be a web page, but in CodeIgniter, a view can also be a page fragment like a header or footer.

Codigniter features

• Model-View-Controller Based System
• Extremely Light Weight
• Full Featured database classes with support for several platforms.
• Query Builder Database Support
• Form and Data Validation
• Security and XSS Filtering
• Session Management
• Email Sending Class. Supports Attachments, HTML/Text email, multiple protocols (sendmail, SMTP, and Mail) and more.
• Image Manipulation Library (cropping, resizing, rotating, etc.). Supports GD, ImageMagick, and NetPBM
• File Uploading Class
• FTP Class
• Localization
• Pagination
• Data Encryption
• Benchmarking
• Full Page Caching
• Error Logging
• Application Profiling
• Calendaring Class
• User Agent Class
• Zip Encoding Class
• Template Engine Class
• Trackback Class
• XML-RPC Library
• Unit Testing Class
• Search-engine Friendly URLs
• Flexible URI Routing
• Support for Hooks and Class Extensions
• Large library of “helper” functions

model-view-controllers

CodeIgniter is based on the Model-View-Controller development pattern. MVC is a software approach that separates application logic from presentation. In practice, it permits your web pages to contain minimal scripting since the presentation is separate from the PHP scripting.

• The Model represents your data structures. Typically your model classes will contain functions that help you retrieve, insert, and update information in your database.
• The View is the information that is being presented to a user. A View will normally be a web page, but in CodeIgniter, a view can also be a page fragment like a header or footer. It can also be an RSS page, or any other type of “page”.
• The Controller serves as an intermediary between the Model, the View, and any other resources needed to process the HTTP request and generate a web page.

How to Upload Image and File in Codeigniter 

File uploads are an essential process in many web apps. Besides having Best PHP Hosting, almost every website and web app requires an integrated file upload component. File and image upload in CodeIgniter powered app is a simple component that takes care of the upload process with little issues.

This tutorial discusses the process of creating a CodeIgniter based file upload component that could be easily used t upload images and other files with ease. You could validate and even restrict file size and type during the upload process.

Folder Creation:

The first step is the creation of two folders that form the basis of the upload process. The first folder is the destination folder that would receive the uploaded files.Next, go to the root of the CI installation and create a folder named “upload”.

Create the Controller:

The next step is the creation of a file in the controller folder.  Name the file service.php. In this file, I will load a library for initializing the Upload class through the following code.

Create the Model:

The next step is the creation of a file in the models folder.  Name the file Smodel.php.