Changes

m
no edit summary
Line 1: Line 1: −
<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
+
<noinclude>{{GoogleTrans-en}}{{TOCright}}
 +
[[Category:Feature Page Incomplete]]
 +
[[Category:Feature|Host Version]]</noinclude>
    
== Summary ==
 
== Summary ==
Line 14: Line 16:     
== Detailed Description ==
 
== 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 (especially with things like the XO-1.5 that supports 3D acceleration on the horizont).
+
With 0.86 being on the horizon, 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 horizon).
    
: 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.
 
: 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 24: Line 26:  
== Benefit to Sugar ==
 
== Benefit to Sugar ==
 
* avoid user confusion as to why some activities might potentially not work on the currently installed OS.
 
* avoid user confusion as to why some activities might potentially not work on the currently installed OS.
* identify activity developres who don't know about compatibility issues and the importance of testing on specific versions of Sugar (they won't have updated their default .info file)
+
* identify activity developers who don't know about compatibility issues and the importance of testing on specific versions of Sugar (they won't have updated their default .info file)
      Line 53: Line 55:  
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]
 
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]
   −
[[Category:Feature Page Incomplete]]
  −
[[Category:Feature]]
   
----
 
----
 
''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''
 
''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''