Features/Host Version: Difference between revisions

Line 14:

== Detailed Description ==

With 0.86 being on the horizont, 0.84 being used on SoaS, 0.82 being widely used among the G1G1 community and some deployments and many deployment still using pre-0.82 software I think the issue of activity compatibility deserves some serious attention. Otherwise this has the potential to create _a lot of_ confusion and frustration further down the road.

With 0.86 being on the horizont, 0.84 being used on SoaS, 0.82 being widely used among the G1G1 community and some deployments and many deployment still using pre-0.82 software I think the issue of activity compatibility deserves some serious attention. Otherwise this has the potential to create _a lot of_ confusion and frustration further down the road (especially with things like the XO-1.5 that supports 3D acceleration on the horizont).

Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.

Line 21:

== Benefit to Sugar ==

Avoids user confusion as to why some activities might potentially not work on the currently installed OS.

~~''What is the benefit~~ to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''

== Scope ==

@@ Line 14: / Line 14: @@
 == Detailed Description ==
-With 0.86 being on the horizont, 0.84 being used on SoaS, 0.82 being widely used among the G1G1 community and some deployments and many deployment still using pre-0.82 software I think the issue of activity compatibility deserves some serious attention. Otherwise this has the potential to create _a lot of_ confusion and frustration further down the road.
+With 0.86 being on the horizont, 0.84 being used on SoaS, 0.82 being widely used among the G1G1 community and some deployments and many deployment still using pre-0.82 software I think the issue of activity compatibility deserves some serious attention. Otherwise this has the potential to create _a lot of_ confusion and frustration further down the road (especially with things like the XO-1.5 that supports 3D acceleration on the horizont).
 Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.
@@ Line 21: / Line 21: @@
 == Benefit to Sugar ==
+Avoids user confusion as to why some activities might potentially not work on the currently installed OS.
-''What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''
 == Scope ==