[interfacekit] One-thread-per-window

    With all the feature talk on the OBOS list, I've been thinking, which 
some might consider dangerous. ;) One of the biggest complaints from 
developers that I've heard is the one-thread-per-window concept and forced 
multithreading.
    How difficult would it be to provide an alternative to this but still 
keep the regular API at the same time? I mean like a couple extra classes in 
the Interface Kit which would utilize the same thread used by the 
BApplication class instead of starting their own, possibly being coupled with 
a special BApplication class. Then again, would this be a wise idea to do so?

--DW

Other related posts: