storing Activity parameters

[Tomeu Vizoso]

On Sun, Mar 2, 2008 at 1:51 PM, Gary C Martin <gary at garycmartin.com> wrote:
> I'm having some indecision about my own (very simple) activity state
>  saving. Just had a though that may add another possibility to this
>  thread. What if both journal and file-system were used to store the
>  activity state, with the journal settings overriding the file-system
>  settings. This way a new activity start-up could inherit the last used
>  activity settings, and a specific journal start-up would inherit the
>  settings used for that specific entry. So in the case of Speak I could
>  have separate favourite journal entries for '3 eyed alien' and another
>  for 'Mr square eyes', then if I also just started the activity from
>  fresh I'd pick-up whatever the last used setting were (picked up from
>  the FS).

I like this idea a lot. Thanks for sharing.

[...]

>  On 2 Mar 2008, at 01:29, Joshua Minor wrote:
>
>  > I implemented the save/load feature of Speak without fully
>  > understanding the other options.  Now that I've seen the recent
>  > discussion about data vs instance vs the journal I think it would make
>  > more sense to have Speak save its state in a different way.
>  >
>  > On the other hand, the new frame redesign makes it much easier to
>  > resume an Activity, which would mean that parameters saved to the
>  > Journal, like Speak does now, would naturally be restored when you
>  > resume the Activity.
>  >
>  > A nice "best practices" document would be very handy.

Yeah, storing some settings both in the fs and in the datastore would
be suggested by these best practices document.

Any activity author would like to start it? I'm sure many interesting
discussions will come from this effort.

Thanks,

Tomeu