Laravel session 1

Laravel session 1

• 1.
  Laravel “The PHP FrameworkFor Web Artisans” By: - Ashish Kumar
• 2.
  Why Framework? (Legacy CodeProblems) • Spaghetti Code • Limited Code Re-Use • Multiple Code Styles • Security vulnerabilities
• 3.
  What is Framework •An essential supporting structure of a building, vehicle, or object. • A basic structure underlying a system, concept, or text • Software Framework: – an abstraction in which software providing generic functionality can be selectively changed by additional user- written code, thus providing application-specific software • A software framework is 80% of your application already written for you.
• 4.
  Why Laravel ? •Taylor Otwall, a .NET developer in Arkansas (USA), was using an early version of CodeIgniter when the idea for Laravel came to him. • “I couldn't add all the features I wanted to” , he says, “without mangling the internal code of the framework”. • He wanted something leaner, simpler, and more flexible.
• 5.
  Trends of PHPFramework
• 6.
  Laravel?
• 7.
  Non-MVC Vs MVC
• 8.
  Model-View-Controller- Architecture
• 9.
  Model • it representsthe data to the user. • This level defines where the application’s data objects are stored. • The model doesn’t know anything about views and controllers. So, whenever there are changes done in the model it will automatically notify observers that the changes are made. • The model may be a single object or a structure of objects.
• 10.
  Views • A viewis a visual representation of the MVC model. • This level creates an interface to show the actual output to the user. • However, a view will not display anything itself. It is the controller or model that tells view what to display to the user. • It also handles requests from the user and informs controller.
• 11.
  Controller • Controller isa level which acts like a brain of the entire MVC system. • A controller also acts as a link between a user and the system. • The Controller is responsible for controlling the application logic and acts as the coordinator between the View and the Model. • The Controller receives an input from the users via the View, then processes the user's data with the help of Model and passes the results back to the View.
• 12.
  Benefits • Faster developmentprocess • Ability to provide multiple views • Loads Very fast • Modification does not affect the entire model • MVC model returns the data without formatting • SEO friendly Development platform
• 13.
  MVC - Laravel
• 14.
  THE EVOLUTION OFLARAVEL • Laravel 1 (6/2011) • Laravel 2 (11/2011) • Laravel 3 (2/2012) • Laravel 4 (5/2013) • Laravel 5 (2/2015) • Current Version is 5.5
• 15.
  Prerequisites
• 16.
  Course Items • LaravelFundamentals – Installing Composer – Installing Laravel – Routing – Views – Databases – Creating tables – Migrations – Models – Blade • Creating a Login/Registration Web App – Project Source Code – Setting Up New Project – Seeding and displaying books – Login Form – Logging In – Laravel Filters – User Registration
• 17.
  Composer • It’s nota package Manager • It’s a dependency manager • It deals with packages or libraries but it manage on a per-project basis. • PHP 5.3.2+ to run • To test(command): – Composer –v
• 18.
  Laravel 5.5 Installation •Server Requirement – PHP >= 7.0.0 – OpenSSL PHP Extension – PDO PHP Extension – Mbstring PHP Extension – Tokenizer PHP Extension – XML PHP Extension • Via Composer: – composer global require "laravel/installer” – laravel new blog – Composer install