storing Activity parameters

[Joshua Minor]

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.

-josh

On Mar 1, 2008, at 11:23 AM, Mikus Grinbergs wrote:

> There has been discussion of the use of the Journal, versus other
> places, to store information associated with an Activity.
>
> What I've noticed is that some Activities are now storing their
> parameters in the Journal.  For instance, I prefer to change the
> shape of the eyes in 'Speak'.  If I launch 'Speak' from the menu
> frame, it shows the "default" eye shape.  If I launch 'Speak' from
> the Journal, it shows the eye shape I specified earlier.
>
> Personally, I would prefer having Activities store user-specified
> overrides someplace other than in the Journal.  Then when a new
> 'instance' of the Activity gets invoked, it can come up looking the
> way the user likes it, not just with its "built-in" appearance.
>
> mikus
>
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel