On 3/30/02 4:35 PM, "Chris Little" <cslittle at mac dot com> wrote:
> This seems problematic since the app's code is in the data fork.
Why is that a problem? The code simply never executes the data where the
picture is stored. If you look at it, you'll realize that string literals
tend to show up in the data fork exactly as they are, and if you've ever
done assembly programming (TI-83, yeah) you learn that pictures and strings
are stored in the program's disk space, just simply not executed.
On the subject of limited writing to the file: There would have to be size
restrictions, i.e. if you include a 1k file, you can't write more than 1k
back to the file. But, given the restrictions, it's a very nice idea, and
one I hope RB implements (including the files, and limited writing to them).
--
Kevin Ballard
kevin at sb dot org
Email from Korea or China must go to <kevin dot nb at sb dot org>
http://kevin.sb.org/
|