Hi, Jim!

I think it is also a VERY good idea to indicate which ones are alredy implemented in VFP8. So, in your statistics we can show how many in category were implemented, as well as add additional flag/option to wish to indicate it is implemented in VFP8.

I can help you in determining what is implemented in VFP8 (as of presented at DevCon). Contact me if you're interested.

>I have finished a "review" of the Toledo Wish List items and content as it stood at September 29, 2002.
>Right off the bat I must say that I know I skipped at least a few. My review included 822 entries.
>
>I will present some numbers that are somewhat arbitrary, caused by the following problems:
>1) "Area" and "Sub Area" are often not specified by the originator;
>2) "Area" and "Sub Area" are often confusing because of both near-duplications and because of perception differences.
>--- For instance, most of us interpret "Performance" as relating to processing speed, but some see it as 'how it performs' (compared to spec).
>3) "Area" and "Sub Area" are missing for some key categories.
>4) Many items list several wishes and I had to choose one (the first) for categorization purposes.
>5) Many wishes (39) were to fix known bugs/problems and these have been included here.
>For the above reasons I generally adopted my own categorizations but did keep the essence of the original intent.
>

>AREA            Count
>API               1
>COM               5
>Classes         185
>Data            101
>Debugging        23
>Designers        95
>Editor           65
>Help              3
>IDE              71
>Language        207
>Performance       1
>Unknown           2
>xBase            63
>

>Notes regarding the above:
>a) COM included most anything mentioning COM.
>b) I added many subareas to area "Classes".
>c) Area "Data" subarea "Engine" includes most anything that doesn't fit elsewhere, like long names in free tables, multi-threading, indexing stuff, ActiveX support, source encryption, etc.
>d) I added subarea "SQL" to area "Data" to refer to VFP SQL specifically.
>e) Area "Designers" was used when a designer was specifically mentioned. Many that may have gone here were put into "Editor" or "Language" based on their content (as interpreted by me)
>f) Area "Editor" has items that sounded applicable generally to its UI but might also have been applicable to a specific subarea of area "IDE".
>g) Area "IDE" had subarea "Project Manager" added to it.
>h) Area "Language" had several subareas added to it: Enhanced Command; Enhanced Function; New Command; New Function; New Operator; New SysVar.
>--- When a wish named a specific command or function that applied to application execution then it was included in this area.
>i) Area "Unknown" was added by me when an item was too unclear to even guess at.
>Area "xBase" subarea "Other" was used for lots of 'general' things like WinCE version, VSS integration, XP compliance, etc.
>
>A more detailed breakdown is shown below:
>

>AREA		Subarea		Count
>API		SDK Samples	        1
>COM		Debugging	        1
> 		Interfaces	        1
>Classes	All Controls	       41
>		Column		        1
>		ComboBox	        7
>		CommandButton	  6
>		Container		  8
>		Custom		        2
>		EditBox		  5
>		Form		       10
>		Grid		       48
>		Image	       	  5
>		Label		        3
>		Line		        1
>		ListBox		  6
>		New Control	       12
>		OLEBoundControl	  2
>		OLEControl	        2
>		OptionButton	        3
>		PEMs		        1
>		Page		        2
>		PageFrame	        6
>		Session		  3
>		TextBox		  8
>		ToolBar		  3
>Data		DBC Events	        1
>		Engine		       80
>		OLE DB		        1
>		SQL		       19
>Debugging	Call Stack		  1
>		Error Messages	  3
>		Locals		        1
>		Output		        3
>		Trace		       12
>		Watch		        3
>Designers	Class		        7
>		Form		       22
>		Menu		       18
>		Query		        1
>		Report		       32
>		Table		        2
>		View		       13
>Editor		Intellisense	       11
>		Syntax Coloring	  3
>		UI		       51
>Help		Content		  3
>IDE		Command Window	  4
>		Designers	       10
>		Dialogs		  7
>		Doc View		  7
>		Docking		  2
>		Find		        2
>		Project Manager	 23
>		Prop. Sheet	       11
>		ToolBars		  2
>Language	Enhance Command    100
>		Enhance Function 	 29
>		New Command	       25
>		New Function	       33
>		New Operator	        8
>		New SysVar	        1
>		Objects		  2
>		Obsolete		  1
>Performance	Engine		        1
>Unknown		Unclear	  2
>xBase		Beautify		  2
>		Builders		  5
>		Class Browser	  2
>		Coverage Profiler	  1
>		Object Browser	  1
>		Other		       45
>		Samples		  3
>		Task List		  1
>		Tools		        2
>		Wizards		  1

>I will, in another message tomorrow, make suggestions to improve the UT's wish list handling for VFP9.