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

1. Applications and Plugins
Overview

2. What are Application in
Plugins
Applications and plugins are way of extending ProdigyView. They
add executable code to the web application.
Facebook App
E-commerce My App
App
E-commerce
Extension Plugin

3. How they Differ From
Libraries
Essentially application and plugins are libraries. BUT they
differ normal libraries in that they are managed by the
database. Applications and plugins:
1. Must be installed into the database
2. Can be turn on and off with the database
3. Have a single point of entry and does not include the
entire directory
www.prodigyview.com

4. 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 Application
1. Starting pointing, ProdigyView is included
and bootstrapped. Start
2. In the body is where functions are
executed, objects are called, information is Body
printed out, etc.
3. At then of our application, we finish
running the script
End

5. Applications
Application can be called anywhere in the flow of the code. But
they only exist when they are called and they must be object
oriented.
My Web Application
Start
E-commerce
App Call e-commerce
app
Body
Call Facebook
application
Facebook App
End
www.prodigyview.com

6. 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_exec
1. pv_exec($comamnd, $params, ..etc) 2. Get application
information from database
3. Includes files in file system if not
already included 4. Instantiates an object if its not already
instantiated
New
Object
5. Executes application

7. Key Points on Applications
What 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.
www.prodigyview.com

8. Plugins
The main difference between plug-ins and applications is plug-ins
are 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

9. Key Points on Plug-ins
1. 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
www.prodigyview.com

10. API Reference
For a better understanding of the applications and plugin,
visit the api by clicking on the link below.
PVApplications
PVPlugins
More Tutorials
For more tutorials, please visit:
http://www.prodigyview.com/tutorials
www.prodigyview.com