[sugar] Choosing "defaults" for the activity ring

[Tomeu Vizoso]

Ok, so the plan currently is for Sugar to keep shipping an
activities.default with the same format as the existing one.

The favorites file in the user profile will store the mtime and size
of the activities.default file that merged by last time. At startup,
the shell will check if it should merge a new one.

Activity packs will still be able to customize this defaults file.

Any comments?

Thanks,

Tomeu

On Sat, Apr 5, 2008 at 8:22 AM, Eben Eliason <eben.eliason at gmail.com> wrote:
> I'll toss in my thoughts, as I tried to introduce the problem as
>  impartially as possible.  I personally find the first option to be the
>  simplest to implement, as well as the clearest conceptually.  I, too,
>  expect that such occurrences will be few, and find it unlikely that it
>  would become a nuisance in those cases anyway.
>
>  - Eben
>
>
>
>  On Fri, Apr 4, 2008 at 8:17 PM, Benjamin M. Schwartz
>  <bmschwar at fas.harvard.edu> wrote:
>  > -----BEGIN PGP SIGNED MESSAGE-----
>  >  Hash: SHA1
>  >
>  >  Eben Eliason wrote
>  >  I prefer option (1) because it's the behavior I would want as a user. With
>  >  option (1), it's more obvious that new activity bundles have been
>  >  installed.  It's also more straightforward to implement.
>  >
>  >
>  >  | Option (2) is somewhat more complex, but ensures that the user doesn't
>  >  | have to repeatedly un-favorite activities which they don't want in
>  >  | their ring.
>  >
>  >  Where "repeatedly" means "each time a Customization Stick is inserted".  I
>  >  do not imagine this happening more often than once a semester, i.e. very
>  >  infrequently.  It does not sound very inconvenient to me.  Remember, this
>  >  is the same frequency with which we anticipate that new OS releases will
>  >  be installed.
>  >
>  >  In fact, once we have automatic network activity updates, as recently
>  >  discussed, I suspect that customization sticks will be used very little.
>  >  - --Ben
>  >  -----BEGIN PGP SIGNATURE-----
>  >  Version: GnuPG v2.0.7 (GNU/Linux)
>  >  Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>  >
>  >  iD8DBQFH9sUxUJT6e6HFtqQRAoDTAJwLvas9mWk4DBz3U/82s3u/rE/xMQCfZX0o
>  >  wCSPmarE//HK7RVRCAevjzQ=
>  >  =UWRr
>  >  -----END PGP SIGNATURE-----
>  >
>