lighnting component development
TRANSCRIPT
#MWD16
Midwest Dreamin’ Platinum Sponsors
#MWD16
#MWD16
Midwest Dreamin’ Gold Sponsors
LIGHTNING COMPONENT DEVELOPMENT AND DEBUGGING
#MWD16
Mohith ShrivastavaSalesforce MVP ,Engineer at CodeScienceCodeScience INC@msrivastav13
#MWD16
Why Lightning Components?1. Reusability(App Builder,Community
Builder,SF1 ,Visualforce,With Lightning out take components outside SFDC)
2. Responsive (fits any device)
3. Event Driven approach #MWD16
Difference between Lightning components and VisualforceVisualforce
1.Monolithic unless developers use Visualforce components and templates
2.Building SPA applications without using frameworks like angular ,react etc is tedious
Lightning Components
1.Framework enforces developers to break application into components
2.Building SPA is lot easier.Event driven approach .(Publish and Subscribe model)#MWD16
Building a Simple Sales LeaderBoard Component 1. Interfaces decide where all your
components can appear in salesforce
2. Events - Application events and Component Events
3. Use design attributes for admins #MWD16
Breaking UI into Multiple Components
#MWD16
Events - Publish and Subscribe Concept
Building a Simple Youtube search component for community builders1. Implement
ForceCommunity:availableForAllPageTypes
2. Design Tokens and Design Variables for community builder
3. Callouts via Apex #MWD16
Building Components for Record Home pages and Home page1. Implement
Flexipage:availableForRecordHome
2. Design components for Home page
#MWD16
Lightning Out 1. Mashup Visualforce and Lightning
components
2. Heroku App Demo
#MWD16
Debugging1. Chrome Lightning Inspector and Debugger
Debug Events , Performance , Component Tree ,Override Actions
Debugging
Referenceshttps://github.com/CodeScience/MidwestDreamin
https://github.com/msrivastav13/NodeLightningOut
https://developer.salesforce.com/trailhead/en
questionsMohith Shrivastava@msrivastav13
#MWD16