Hi Jacque,
Le 2 août 07 à 05:24, J. Landman Gay a écrit :
You can put info in custom properties and password-protect the
stack, which makes the properties unreadable and encrypted.
Unfortunately (and this would be a nice to have), custom properties
can be accessed as usual in a password
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
Eric Chatonet wrote:
Hi Jacque,
Le 2 août 07 à 05:24, J. Landman Gay a écrit :
You can put info in custom properties and password-protect the stack,
which makes the properties unreadable and encrypted.
Unfortunately (and this would be a nice to have), custom properties can
be accessed as
Josh Mellicker wrote:
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
Thanks for your illumination on this topic.
On Aug 2, 2007, at 9:29 AM, Richard Gaskin wrote:
If I'm reading your posts correctly it sounds to my ear like you've
already decided. If it works, why change?
I was just wondering if there was any case in which someone would
store such a
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
I know stacks are a nice way to save a lot of data because it can be
organized by custom property and custom property set.
But what about a simple list of data consisting of name, URL, and a
couple other fields, that needs to be downloaded from a server- would
you save the data in:
A. a
Josh Mellicker wrote:
I know stacks are a nice way to save a lot of data because it can be
organized by custom property and custom property set.
But what about a simple list of data consisting of name, URL, and a
couple other fields, that needs to be downloaded from a server- would
you
there are so many ways and so many different solutions... all good.
No method is inherently 'easier'. You have to focus on what's best
for your user. Will this be used by many or just one person? Does it
need to travel with the app or does there need to be prefs for
multiple users?
Text
One other consideration is how the data is to be used. Even though
the data maybe simple, if you were going to load it into an array in
your app, then saving it as a customPopertySet in a stack file might
be easier.
from a text file to an array goes from
put URL file:someFile.txt into
Josh Mellicker wrote:
I know stacks are a nice way to save a lot of data because it can be
organized by custom property and custom property set.
But what about a simple list of data consisting of name, URL, and a
couple other fields, that needs to be downloaded from a server- would
you save
11 matches
Mail list logo
