Changes

<noinclude>[[Category:Wish list]][[Category:General public]][[Category:Idea]]

<noinclude>[[Category:Wish list]]

'''Please describe new feature requests by one of the methods below:'''

'''Please describe new feature requests by one of the methods below:'''

I have read the [[Activities/Screencast| Activity Screencast page]].

I have read the [[Activities/Screencast| Activity Screencast page]].

===training for Soas/ Sugar===

===training for Soas/ Sugar===

As a teacher with a little technical background, I can say that SoaS will have a lot of trouble getting traction into the schools without a lot more training. That training could easily be generated with Screencasts by volunteers IF screencasting was _better supported_ in SoaS. If screencasting was better implemented students could show, maybe even STREAM their videos, to their teachers, parents, friends and show how SMART they are by letting them make their own movies of same...

As a teacher with a little technical background, I can say that SoaS will have a lot of trouble getting traction into the schools without a lot more training. That training could easily be generated with Screencasts by volunteers IF screencasting was _better supported_ in SoaS. If screencasting was better implemented students could show, maybe even STREAM their videos, to their teachers, parents, friends and show how SMART they are by letting them make their own movies of same...  

 

 

===better bug reports===

===better bug reports===

Furthermore, bug reports become much clearer when recorded _and_ the users knows to pull up the logs too. And the whole process of making a good bug report could be demonstrated in its entirety with a screencast... the vast numbers of users don't know a zillionth of what the devs know or need to know about the bug a user is experiencing... and as most of the users don't speak English, and most devs do, you've got a serious disconnect between what your users need to tell you... enter the 'screencast' and most of the big problem description becomes evident.

Furthermore, bug reports become much clearer when recorded _and_ the users knows to pull up the logs too. And the whole process of making a good bug report could be demonstrated in its entirety with a screencast... the vast numbers of users don't know a zillionth of what the devs know or need to know about the bug a user is experiencing... and as most of the users don't speak English, and most devs do, you've got a serious disconnect between what your users need to tell you... enter the 'screencast' and most of the big problem description becomes evident.

:Erikos's recent work on a system-wide spell-checker might be a reasonable model to base such an intervention on. --[[User:Walter|Walter]] 14:06, 20 November 2009 (UTC)

:Erikos's recent work on a system-wide spell-checker might be a reasonable model to base such an intervention on. --[[User:Walter|Walter]] 14:06, 20 November 2009 (UTC)

[[Category:General public]]

[[Category:Idea]]

[[Category:Feature]]

:This would allow sugar emulator to match screen size of hardware it is running on and always be full screen

: alternately provide a modal button on top frame of emulator window to switch to full screen and back at will.

:[[Emulator/Full Screen|how to configure full screen]].

 

 

 

The challenge that I face is that the terminal is intimidating in comparison to IOS. I think a specialized conversation bot could do wonders for making children more comfortable in the CLI

[[http://www.customwritinghelp.co.uk/assignment.php assignment writing]]

--[[User:Micheal Breathnach|MPB]] 10Dec2012

[[http://www.academic-writings.com/academic-writings.php academic-writings]]

[[http://www.perfectwriting.co.uk/assignment/assignment-help.php assignment help]]

[[http://www.perfectwriting.co.uk/assignment/assignment-writing.php assignment writing]]