Changes

The easiest way to implement step-1 would be to check which mime types exist on the server side in the etc/cups/mime.types file with a simple python method (getAllowableMIMETypes) and make it available on the server's web folder, and access it with a c program during the xo's boot and append the list to our client side mime.types. So anything non-existent here will have its corresponding activities print button disabled  

The easiest way to implement step-1 would be to check which mime types exist on the server side in the etc/cups/mime.types file with a simple python method (getAllowableMIMETypes) and make it available on the server's web folder, and access it with a c program during the xo's boot and append the list to our client side mime.types. So anything non-existent here will have its corresponding activities print button disabled  

As an Alternative, CUPS print function returns a python -1/ C 0 when a non-supported MIME type is used, so we can take advantage of that display a non supported format error.

As an Alternative, CUPS print function returns a python -1/ C 0 when a non-supported MIME type is used, so we can take advantage of that and display a non supported format error.

The xo already comes with a nice save feature which saves files to the journal and categorizes them under the activity name. I will use a similar implementation for the print button in activities (which is activated from step-1) and have it save files under a 'To Print' category/tag in the journal.

The xo already comes with a nice save feature which saves files to the journal and categorizes them under the activity name. I will use a similar implementation for the print button in activities (which is activated from step-1) and have it save files under a 'To Print' category/tag in the journal.

   printf("error printing file, unsupported format");

   printf("error printing file, unsupported format");

for printing  

for printing

====You and the community====

====You and the community====