View Single Post
chemist's Avatar
Administrator | Posts: 1,036 | Thanked: 2,019 times | Joined on Sep 2009 @ Germany
#8
Originally Posted by soeiro View Post
1) Test new software on it *without* the risk of thrashing the real N900 device;

2) Instead of warning users not to install software from extra-devel or extra-testing we could warn them to first test that software in the emulator and, why not, give some feedback;

2) Have a development environment that doesn't require the real device for testing and debugging;

3) One developer could configure the SDK + emulator on his/her home system, office and notebook. Then he/her could use git or mercurial to synchronize it all and be able to code wherever and whenever there is available time without the need to depend on the real device;

4) A larger group could contribute to porting and developing apps for the N900 device if only they could use the emulator without having to buy one real device. For instance: an upstream maintainer of some package could agree to accept some patches and even test them on the emulator.
Ad 1, SDK is in place
Ad 2, normal users wont use the emulator, that many did brick their device yet or did other stupid things by using repositories and bare .debs not ment to be for them... hints "you may brick your device" should stay as most avarage joe users are not able to test software for good and will brick their devices even with software they tested..."yeah it starts... lets install on to device... ah what should I do it doesnt boot anymore... the community sucks... why nokia doesnt fix this... n900 sucks... I want my money back..."
and this will stay

Ad 3 and 4, SDK is in place, well it is missing buttons and sensors but that could be coded for the SDK as add-ons.

if you are talking about windows SDK and a device shown in a window that you are bale to move around and press buttons and so, have fun...