Implicit Layout-View Declarations

Now that we have seen what layouts and views are, where they are located and some samples, let's dig deeper. Let's discover the power of implicit layout/view declarations:
1
//Register Layouts
2
layouts = [
3
    { name = "login",
4
       file = "Layout.tester.cfm",
5
      views = "vwLogin,test",
6
      folders = "tags,pdf/single"
7
    }
8
];
Copied!
This layouts setting allows you to implicitly define layout to view/folder assignments without the need of programmatically doing it. This is a time saver and a nice way to pre-define how certain views will be rendered. Let's see more examples:
1
//Register Layouts
2
layouts = [
3
    { name = "Popup",
4
       file = "Layout.Popup.cfm",
5
      views = "login,test",
6
      folders = "^tags,pdf/single"
7
    },
8
    { name = "help",
9
      file = "layout.help.cfm",
10
      folders = "^help"
11
    }
12
];
Copied!
In the sample, we declare the layout named popup and points to the file Layout.Popup.cfm. We can then assign it to views or folders:
Views : The views to assign to this layout (no cfm extension)
Folders : The folders and its children to assign to this layout. (regex ok)
This is cool, we can tell the framework that some views and some folders should be rendered within a specific layout. Wow, this opens the possibility of creating nested applications that need different rendering schemas!

Layout Events

Helpers UDF's

Last modified 4yr ago

Copy link

Edit on GitHub