I wrote a blog post describing and comparing 3 Object / Collection explorer tools, one of which was Tamar's Object and Collection Inspector (which is the one you mentioned).


http://mattslay.com/object-inspectors-and-explorers-for-foxpro/





>If you install Thor, one of the tools that comes with it is called "Object and Collection Inspector".
>
>https://vfpx.codeplex.com/wikipage?title=Thor&referringTitle=Home
>http://www.tomorrowssolutionsllc.com/Articles/Introducing%20the%20Object%20and%20Collection%20Inspector.pdf
>
>>I noticed that the debugger did not support peeking into the collection at run time - I usually like to take a look the first time I run something to see if the data looks okay. So I had to write a bit of temp code to iterate through the collection throwing each item into an object so I could take a peek. But overall, I like the concept.
>>
>>Albert
>>
>>>>Hi Thierry,
>>>>
>>>>Got it all working. Thanks for pointing me to the collections object. I see using this a whole lot more in the future.
>>>>
>>>>Albert
>>>
>>>Hi Albert,
>>>
>>>Thanks for the feedback!
>>>
>>>Another good news if ever you wish to use FoxInCloud some day: FoxInCloud supports modal forms returning collections. Though I share your preference for isolated, private datasession, FoxInCloud also supports forms working in other form's datasession and/or global datasession.
>>>
>>>Collections (aka 'associative arrays', enumerable, etc., etc.) are very common in 'modern' languages like php or JavaScript and, like you, I tend to like them more and more, except at debug time with VFP because you can't see anything in the 'locals' window.
>>>
>>>Otherwise, Collections allow you to encapsulate data and related custom methods in a single place.
>>>
>>>I plan to create a collection wrapper around an array to emulate the JavaScript methods .join(), .map(), .detect(), etc.