Difference between revisions of "User talk:Wade/Unified Bundles"
(New page: == Making FCAs inside other activities == An interesting idea which might be relevant to this proposal is the spawning of FCAs from other activities. The general idea is that I created thi...) |
(→Yet another scheme of implementing viewers: new section) |
||
| Line 1: | Line 1: | ||
== Making FCAs inside other activities == | == Making FCAs inside other activities == | ||
An interesting idea which might be relevant to this proposal is the spawning of FCAs from other activities. The general idea is that I created this killer Etoys app and I want to share it with the world, not as a journal entry but as a activity itself. LFaraone 23:17, 6 April 2009 (UTC) | An interesting idea which might be relevant to this proposal is the spawning of FCAs from other activities. The general idea is that I created this killer Etoys app and I want to share it with the world, not as a journal entry but as a activity itself. LFaraone 23:17, 6 April 2009 (UTC) | ||
| + | |||
| + | == Yet another scheme of implementing viewers == | ||
| + | |||
| + | startup scripts(launchers) could be parts of sugar itself and contain only metadata about viewer activity. | ||
| + | |||
| + | It should mean that sugar all time has the full list of possible launchers. When user starts bundle with launcher mentioned in exec section, launcher will check if proper viewer activity is installed if it doesn't launcher will install it from ASLO, otherwise(for example in case of bad internet connection) distributor should preinstall these activities(anyway this case is only distribution specific). | ||
| + | |||
| + | In that case we have list of stable launchers(since they don't have much code) and in anytime we could download last version of viewer activity from ASLO. | ||
Revision as of 19:39, 6 April 2009
Making FCAs inside other activities
An interesting idea which might be relevant to this proposal is the spawning of FCAs from other activities. The general idea is that I created this killer Etoys app and I want to share it with the world, not as a journal entry but as a activity itself. LFaraone 23:17, 6 April 2009 (UTC)
Yet another scheme of implementing viewers
startup scripts(launchers) could be parts of sugar itself and contain only metadata about viewer activity.
It should mean that sugar all time has the full list of possible launchers. When user starts bundle with launcher mentioned in exec section, launcher will check if proper viewer activity is installed if it doesn't launcher will install it from ASLO, otherwise(for example in case of bad internet connection) distributor should preinstall these activities(anyway this case is only distribution specific).
In that case we have list of stable launchers(since they don't have much code) and in anytime we could download last version of viewer activity from ASLO.