ayanova/devdocs/todo.txt

@@ -52,6 +52,23 @@ Continue to flesh out autocomplete picklist plan below then implement
 PICKLISTS:
 
 AUTOCOMPLETE 
+	TODO FROM PLANS:
+		- templateable selects and display format for each major object type
+			- similar to datalistview editor but without filtering ability
+			- only one template per picklist type with option to default back to default
+			- Sane default with enough stuff to make it likely they won't bother to change it unless they need to
+
+		- autocomplete / search involves all displayed template columns
+		- support Search *IN* over all joined tables in list
+		- Must be a custom control even if it's just a wrapper around a regular autocomplete for future proofing
+		- TAGS support
+			- Brainwave: include tags as an optional column they can include in template, so if it's far to the right won't intrude on view but can still search for tags right in the text you type!!
+			- this is a simple solution to tags issue
+			
+
+
+
+
 currently in v7:
 	- All picklists in v7 windows are autocomplete based on the START of the phrase typed only
 		- i.e. if you type in a Project box "pr" you will get "Project A", "Project B" but not a project called "ABC Project" as it doesn't search *in* the values
@@ -65,7 +82,35 @@ IDEAS:
 			- For example in v7 if a item was templated like Unit display format with manufacturer first, then search will start with manufacturer
 				so you couldn't search for the model number first or something, you had to start exactly at the start with the manufacturer
 
-	- DISPLAY TEMPLATE
+	- DISPLAY TEMPLATE 
+		- COMBINED WITH DATALISTVIEW or it's own thing?
+			- Potential differences between dlv and PickListView
+				- Only one default per object type, can't make many, so fixed collection of them
+				- No filtering combined with it
+				- Server has code that looks for datalist views generically to display a list of them or fetch them in a factory
+				- Client sends the template to the server to get the dlv, but a picklist is fixed though customizable for all users so client doesn't need to send it except when editing
+				- PLV need to be cached at server as they will be hit hard on nearly any form being opened
+			- Similarities between dlv and PickListView
+				- consumes a list of available fields pre-defined on a collection
+				- order and visible are settable by end user
+			
+		- NAMING: 
+			- "PickListView" 
+			- In v7 display formats are used for the following:
+				- All picklists of that type
+				- In all main grid lists where that type is a JOINED display value not the main one:
+					- e.g. for UserNameDisplayFormat template: UserList just shows fields like name as they are, but Project list shows the project overseer (User) with the templated setting
+					- PROBLEM with v7 in filtering that combined column it actually only operated on the primary column name like "name" 
+						- e.g. setting a filter on the workroderitempart list Part column of "eye" would not bring in part named "Thompson eyephones" becuase underlying it was searching only the part number field
+			- NOT IN GRIDS
+				- I think I can do away with the v7 feature of using the display format in joined tables of the main grids
+					- It didn't filter properly
+					- All JOINED table fields can be provided separately anyway for reporting and viewing and they would actually work with filtering
+			- NOT IN REPORTS
+				- Joined tables can be provided and combined in any way user wants on report so not a MUST have as it's fulfilled anyway
+				
+			- Fixed, i.e. user can't insert their own characters in the display format but has a fixed method of separating fields
+
 		- Was thinking the DataListview stuff would be enough for picklist templates but actually there is very little real overlap here
 		- Maybe a kind of similar feature but focused on picklists instead?
 			- Selection templates for each object by TYPE?