You can have both; but for a VM and trying to make it as simple as possible (even for developers) is to eliminate as much of the cruft and make it simple. If their is no need for SB1 to be installed (because SB2 can handle it) then why waste the time d/l and installing it and the required dependancies.

I'll probably leave the SB1 script so that those who really want it can install it; but if I can get SB2 to work properly with QT Creator; then I'm not going to futz around trying to make QT Creator work with SB1 with all the extra overhead and issues SB1 brings to the table trying to make it work. I have thought out several ways of making SB1 work w/ QT Creator. Nothing real good for debugging though. But SB2 simplifies the whole process drastically (including debugging), and since QT/QMAKE actually supports SB2 targets, that is just an additional simplification for getting everything to work.

So, yeah on one hand it might be extreme to ditch some of the work I did, but if SB2 simplifies it by:
1. Using the native host toolchain (Lots of hd space saved)
2. Only storing the dev kit inside the SB. (lots of hd space saved)
3. Allowing host debug (easily)
4. Source Tree outside scratchbox (easily)
5. QT support for compile target in Scratchbox
6. Ability for me to run compiled apps outside of Scratchbox (meaning I can auto-start xephyr, start hildon & the app; after app is done, stop xephyr)

I'm all for a simpler QT integration setup. ;-D

Nathan.