-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Eben Eliason wrote: > I think that the addition of a new property in the activity.info file > would be logical here. Make it an integer indicating the maximum > number of supported participants.
OK, but as an Activity author I might like to specify that cap at runtime, depending on many things, such as the size of the document. I might even want to let the initiator choose the number of participants. I think we should also have a runtime API, so that the cap that can be varied at any time. In fact, it might be nice to have a a generic solution for defining config variables that can be controlled either statically or at runtime. We have mentioned a wide variety of such variables, including things like whether screen rotation is supported. > Scott (CC'd) has already come up with some really nice proposals for > adding VNC as an alternate colaboration mechanism for all activities. > In my mind, this would work perfectly with the above scheme, whereby > any activity that already has max_participants in it could be viewed > in that manner. I don't see why any Activity should be excluded from such VNC sharing, regardless of max_participants. - --Ben -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmHkNIACgkQUJT6e6HFtqQBlQCdF4AhUy+NWkwYqVR/qMyl/m2H UpAAniXtXxWRQuM8o8iqtiyJ0uB4o05Z =BI5d -----END PGP SIGNATURE----- _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel