Applications and Plug-ins Overview
Upcoming SlideShare
Loading in...5

Applications and Plug-ins Overview



An overview of applications and plug-ins and how they work in ProdigyView.

An overview of applications and plug-ins and how they work in ProdigyView.



Total Views
Views on SlideShare
Embed Views



2 Embeds 111 59 52


Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Applications and Plug-ins Overview Applications and Plug-ins Overview Presentation Transcript

  • Applications and Plugins Overview
  • What are Application in PluginsApplications and plugins are way of extending ProdigyView. Theyadd executable code to the web application. Facebook App E-commerce My App App E-commerce Extension Plugin
  • How they Differ From LibrariesEssentially application and plugins are libraries. BUT theydiffer normal libraries in that they are managed by thedatabase. Applications and plugins:1. Must be installed into the database2. Can be turn on and off with the database3. Have a single point of entry and does not include the entire directory
  • Applications Vs Plugins Now to explain how applications and plugins differ, we are going to use a diagram of a normal application flow. Like a webpage, imagine that our code has a start, body, and an end. My Web Application1. Starting pointing, ProdigyView is includedand bootstrapped. Start2. In the body is where functions areexecuted, objects are called, information is Bodyprinted out, etc.3. At then of our application, we finishrunning the script End
  • ApplicationsApplication can be called anywhere in the flow of the code. Butthey only exist when they are called and they must be objectoriented. My Web Application Start E-commerce App Call e-commerce app Body Call Facebook application Facebook App End
  • Calling An Application When an application is called, there is a small unseen process to get that application to run. It all starts with pv_exec1. pv_exec($comamnd, $params, ..etc) 2. Get application information from database3. Includes files in file system if notalready included 4. Instantiates an object if its not already instantiated New Object 5. Executes application
  • Key Points on ApplicationsWhat should have been taken away from the last slide is:1. Applications files are not included unless the application is called. This means an application does not have a performance impact on your website until its called.2. Applications, by default are only instantiated once. This is to improve the performance of your application. Applications can be instantiated multiple times but multiple instances can use more resources.
  • PluginsThe main difference between plug-ins and applications is plug-insare persistent throughout the entire execution of the program. My Web Application PVBootStrap::bootSystem Usable until end of execution Plug-ins are loaded Start Body E-commerce Extension Plugin End
  • Key Points on Plug-ins1. Do not have to be object oriented. They can be procedural code.2. Can be turned on and off by modifying attributes in the database. Great for turning on and off functionality, especially in a cms.3. Requiring too many large plug-ins can slow down the system
  • API ReferenceFor a better understanding of the applications and plugin,visit the api by clicking on the link below.PVApplicationsPVPlugins More TutorialsFor more tutorials, please visit: