Templates: Where Should Its Elements Be? In the Template or on Another Module?
Download as PPTX, PDF0 likes128 views
The document discusses the use and organization of templates in application development, highlighting the difference between built-in and custom application templates. It details the creation process for templates, including naming conventions and module cloning, and addresses how templates work in terms of shared elements and common logins. The bottom line emphasizes that the first module of an application will be a clone of the template module, with considerations for theme and dependency management.
Templates: Where Should Its Elements Be? In the Template or on Another Module?
- 1. | Templates: Where should its elements be? In the template or on another module? Templates: Where should its elements be? In the template or on another module?
- 2. | Templates: Where should its elements be? In the template or on another module?| Templates: Where should its elements be? In the template or on another module? José Costa OutSystems MVP, Senior Trainer | ITUp @ in [email protected] /josecccosta
- 3. | Templates: Where should its elements be? In the template or on another module? Where have you seen a Template?
- 4. | Templates: Where should its elements be? In the template or on another module? What is an Application Template? â Module (Application) from which you start building your own modules â Makes development more efficient â Already contains many predefined elements â E.g., Theme, CSS, Layout Blocks and Placeholders, logic, etc.
- 5. | Templates: Where should its elements be? In the template or on another module? Types of Templates â Built-in Application Templates â Web: Side Menu, Top Menu â Mobile: Phone, Tablet, Universal â Custom Application Templates â Created by you â Installed from the Forge
- 6. | Templates: Where should its elements be? In the template or on another module? How to create one? â Create new application (web or mobile) â Create module and name it Template_<module_name> â <module_name> is the name of the new template â Insert a description and an icon in the properties of the module â Publish it
- 7. | Templates: Where should its elements be? In the template or on another module? How does it work? When you create your first* module â Clone of the template is made â Clone is renamed to the name of your module
- 8. | Templates: Where should its elements be? In the template or on another module? Bottom line Your first Web Responsive or Mobile module of your application will be a clone of your template module.
- 9. | Templates: Where should its elements be? In the template or on another module? Analysing a Template module
- 10. | Templates: Where should its elements be? In the template or on another module? TopMenu â Common with Login (and Menu) â Every app that uses this template will have it's own login screen â Theme â Based on some other theme â Organization's or department's theme â I can change the CSS and other properties of the theme directly on the module
- 11. | Templates: Where should its elements be? In the template or on another module? Theme on Another Module â Common (with login) â No theme in here â just a reference to a theme on another module â Theme related web blocks also not in here â E.g., Menu â Apps built with this template will all have the same look and feel
- 12. | Templates: Where should its elements be? In the template or on another module? "Everything" on another module â No Common in here â just a reference to the other module â Login is common to all apps â No theme in here â just a reference to a theme on another module â Apps built with this template will all have the same look and feel and same login entry point
- 13. | Templates: Where should its elements be? In the template or on another module? Other Scenarios in Template â Centralized Login logic â UI can be different â Login logic is the same â can be some external system â Sample screens â To showcase your Style Guide
- 14. | Templates: Where should its elements be? In the template or on another module? Changed Element in the Template â If Element is in Template module â Other modules based on that template will not be affected â Remember: it's a clone â If Element is a reference â May have to refresh dependencies to see change reflected in module â Normal dependency "rules" apply
- 15. | Templates: Where should its elements be? In the template or on another module? Templates... Where should its elements be? In the template or on another module? It depends!
- 16. | Tenants: A Look Behind The Scenes Thank You! @ [email protected] /josecccosta
- 17. | NextStep Denver - Final walk-through Stay for our NEO party 4:30pm - 6:30pm
Editor's Notes
- #10: Normal one with: Common (with login) Theme (based on some other theme)
- #11: Most common scenario: a good pattern is each application having a theme based on an organization's or department's theme
- #15: https://success.outsystems.com/Documentation/11/Developing_an_Application/Reuse_and_Refactor/Understand_Strong_and_Weak_Dependencies