![]() The corresponding design resource indicates the formfactors under which the region will be present: Here’s the complete source code listing for the CMP file of the Lightning App Builder template:īackground-color: rgba(255, 255, 255, 0.3) !important Other global style overrides were added to remove some extraneous white-space as I’m trying to make use of every pixel in the phone form-factor. I also set a series of overrides to try and establish a “viewport” that occupied 100% of the width *and* height of the visible screen: ![]() In order to implement the crazy branding, I also added the following global style to hide the flexipage page header, which by default consumes a fair amount of space at the top of the page: Define the template region in the DESIGN file.Define a aura:attribute for each template region.Add an implements=”lightning:appHomeTemplate” to the tag.About the only functionality that I’ve found that the app builder template will not support is (ironically) defining DESIGN properties on the template. The template defines drop target regions for Lightning App Builder components. ![]() The first step in our branding odyssey is to create a Lightning App Builder template. Implementing Custom Branding in a Lightning App Builder Template There’s also lack of direct support for a “viewport” that would grab 100% of the visible screen, enabling developers to explicitly manage scrolling within their Lightning app. That’s why there’s no officially supported methodology (yet) for disabling the built-in “pull to refresh” feature, which can be quite convenient for refreshing web pages, but is inappropriate for single-page apps. ![]() The fundamental problem is that the platform formerly known as Salesforce1 was clearly designed to render web pages (commonly referred to as Flexipages) and not single-page apps (SPAs). “How to pull out all of your hair with maximum effort”. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |