save data in custom properties in a stack- or a text file?

[Stephen Barncard]

Again I say it's how you or your user use the data, and their skill 
in maintaining it without errors.
If you find yourself complaining about editing custom properties in 
the inspector, then take an hour and write a property editor that 
saves properties instead of saving as a text file. This allows you to 
control and contain the data easier.   If your users make errors 
editing text files (extra spaces, etc) then put the data entry under 
your control - verify each item before entry.


>Hi, and thanks for all your responses.
>
>>
>>>entering/reading data manually: text file way easier
>>
>>What is "manually" in this context?  What other processes in the 
>>workflow require "manual" editing?
>
>Basically I was saying typing stuff in a text file is easier than 
>altering custom properties with a property editor and the message 
>box; (mostly during development)
>
>
>What if your data was this:
>
>Revolution Coders
>2.0
>
>Richard,http://www.fourthworld.com/,http://www.fourthworld.com/rev/
>Jacqueline,http://www.hyperactivesw.com,http://www.hyperactivesw.com/Resources.html
>Andre,http://andregarzia.com/,http://www.andregarzia.com/RevOnRockets/index.html
>
>----
>
>Would you tend to store the above in a text file? Or custom props?

-- 


stephen barncard
s a n  f r a n c i s c o
- - -  - - - - - - - - -