...
There are two internal representations of a user's layout in the DLM world. One The first is the Integrated Layout Fragment or ILF and represents the layout viewed by the user in the browser including UI elements merged in from other layouts. The other is known as the Personal Layout Fragment or PLF and contains the layout for a user as found in the database tables. The second is the Integrated Layout Fragment or ILF and represents the layout viewed by the user in the browser including UI elements merged in from other layouts. When changes are made by a user to their layout, ie: the ILF since that is what they are viewing, the system determines if these were changes to a user-owned node or an incorporated node and will then make modifications necessary to the PLF to reflect that change the next time that this user logs in. Then the PLF is persisted to the database.
| Anchor | ||||
|---|---|---|---|---|
|
Integrated Layout Fragment (ILF)
The ILF model is rather simple. It looks just like a traditional nested table model. The only real difference is that the IDs of some nodes have an extended format to represent a system-wide unique node ID. Such nodes were incorporated from another layout and their IDs are morphed at merge time in a way to provide traceability back to the original node in the original layout fragment and elliminate ID collisions with nodes owned by the current user of the layout fragment. Since the ILF is identical to the nested table DOM it works as is in the portal with only minor changes to the structure and theme transformations.
| Anchor | ||||
|---|---|---|---|---|
|
Personal Layout Fragment (PLF)
The PLD PLF model contains three categories of nodes. Categories in this discussion do not map to some attribute on the nodes. It is only a term used for this discussion.
...
For example It also contains to by this user.Anchor
...