From 372c11fc6388a6f817da724d702dadacb3da032d Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Thu, 9 Jan 2020 16:42:21 +0000 Subject: [PATCH] --- .../core-display-format-template-system.txt | 36 +++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 devdocs/specs/core-display-format-template-system.txt diff --git a/devdocs/specs/core-display-format-template-system.txt b/devdocs/specs/core-display-format-template-system.txt new file mode 100644 index 00000000..8a5a3165 --- /dev/null +++ b/devdocs/specs/core-display-format-template-system.txt @@ -0,0 +1,36 @@ +DISPLAY FORMAT TEMPLATE SYSTEM SPECS + +Display format (aka name display format) templates are used to customize what is shown in minimal display areas in order for a user to identify a record uniquely +for selection purposes. + +Raven will rely much more heavily on this for several reasons so it needs to be a solid integral part of Raven + +CASES + + + +REQUIREMENTS + +Client + - Main grid lists will be very narrow and in many (if not all) cases show only a single column + - Selection drop down boxes in forms for selecting other objects + - Template editor under global settings for all main list objects + +Server + - List of templates with their column selections + - For client editor + - For server to process what the query and send for lists + + - List of fields available for templates + - + + +TO BE DETERMINED + - How will it actually work + - Does the client or the server compose the field based on template? + - Bandwidth considerations + - Server load considerations + - Server latency considerations + - Client power churning through a big list considerations + - DB objects and server objects and routes + \ No newline at end of file