アドバンスドLightningコンポーネント：品質の高いコンポーネント開発のためのTips
•
1 like•534 views
The document discusses forward-looking statements and associated risks in salesforce.com's SEC filings. It notes that any projections or statements regarding strategies, plans, beliefs, new products/services, or customer contracts constitute forward-looking statements that are subject to risks and uncertainties. These risks include factors that could affect salesforce.com's financial results such as developing new functionality, market conditions, litigation outcomes, mergers and acquisitions, managing growth, and other operational factors.
Report
Share
アドバンスドLightningコンポーネント：品質の高いコンポーネント開発のためのTips
- 1.
- 2. Statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward- looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
- 4. Performance Best Practices for Lightning Component Development Advanced Lightning Component
- 7.
- 8.
- 9. var action = component.get("c.getItems"); action.setStorable(); action.setCallback(this, function(response) { // handle response }); $A.enqueueAction(action);
- 10.
- 12. Component Framework Client Cache
- 13. Component Framework Client Cache
- 14. Component Framework Client Cache
- 15. <force:recordData recordId="{!v.recordId}" targetFields="{!v.contact}" fields="['Id', 'Name', 'Phone', 'Mobile']" />
- 16. Component A Component B Component C Lightning Data Service
- 17. Component A Custom Cache
- 18.
- 20.
- 21.
- 22. • • • •
- 23.
- 24. <aura:attribute name="step" type="Integer" default="1"/> <div class="{!v.step==1 ? null : 'slds-hide'}"> Step 1 </div> <div class="{!v.step==2 ? null : 'slds-hide'}"> Step 2 </div> <div class="{!v.step==3 ? null : 'slds-hide'}"> Step 3 </div>
- 25. <aura:attribute name="step" type="Integer" default="1"/> <aura:if isTrue="{!v.step==1}"> Step 1 </aura:if> <aura:if isTrue="{!v.step==2}"> Step 2 </aura:if> <aura:if isTrue="{!v.step==3}"> Step 3 </aura:if>
- 26.
- 28.
- 29. <aura:component controller="ContactController> <aura:attribute name="contacts" type="Contact[]"/> <aura:iteration items="{!v.contacts}" var="property"> <lightning:input value="{!contact.firstName}" /> </aura:iteration> </aura:component>
- 30. contact.addEventListener("change", function(event) { inputElement.value = contact.firstName; }); inputElement.addEventListener("change", function(event) { contact.firstName = inputElement.value; });
- 31. <aura:component controller="ContactController> <aura:attribute name="contacts" type="Contact[]"/> <aura:iteration items="{!v.contacts}" var="property"> <lightning:input value="{#contact.firstName}" /> </aura:iteration> </aura:component>
- 32. <aura:attribute name=“contact” type=”Contact”> <force:recordData aura:id=“service” recordId-”{!v.recordId}” targetFields=“{!v.property}” fields=“[‘Id’,’Name’]” /> /*これは動作しない */ <p>{#v.contact.Name}</p>
- 34.
- 35. • • • • •
- 36. • •
- 38.
- 39. //Child <aura:method name=“showPopup” action=“”> <aura:attribute name=“fund” type=“Fund__c” /> <aura:attribute name=“x” type=“Decimal” /> <aura:attribute name=“y” type=“Decimal” /> </aura:method> //Parent component.find(“popup”).showPopup(fund,10,20);
- 41. • • • §
- 42. • •
- 43. • • • • •
- 45.
- 46.
- 48. • • • • • • • •
- 49. Thank Y u