I like this! Buuuuut... seems kinda messy for our needs. Does YAML
require the use of whitespace? Can it operate in a more compact way,
as JSON does? If so, we could just have a one line comment at the top
or bottom of the file.. # Shoes data: #{serialized data} and consider
the data to finish when the scanner finds a newline or the end of the
file is reached. This __END__ thing seems quite hacky and I worry it
would scare newbie's a bit. It scares me a bit!
I often open my .rb shoes script, see a bug, make a code change, save,
close shoes, reopen .rb file in shoes... Which could cause data
corruption or even overwrite part of the script if the length of the
file changes.
So, I'm all for storing the stuff inside of shy files, when things are
packaged in to shy. I don't like the idea of doing it to plain old .rb
files because I really do think there will be data loss involved that
will confuse and frustrate during development. Can we fall back to a
file in wherever the OS's usual place for storing app data is, when it
isn't a shy file?
Final thought: Is the packaging stuff (dmg, exe, run outputting, and
shy building) available silently to Shoes apps? Could be kind of nifty
for shoes apps to be able to generate their own offspring with
embedded data, like those apps that used to go around in the 90's
where a cute animation would happen on screen with customized text,
and then at the end you could enter your own personal message, save
out a custom exe, and email it to a friend. :)
