Especially, Devexpress Wrapper for LookUpEdit.
Since I've decided to use devexpress, I want to use all of them as strataframe wrapped component.
If you or I decide to use our controls in a certain way then that is our choice and the question is really who is responsible for doing this. Personally, I would like SF to write my entire application while I take a holiday but that isn't going to happen 
I don't know much about DexExpress but as far as I can tell this control does support standard .NET databinding so a SF Business Binding Source should work. I am sorry but I don't see what a wrapper is going to give you here that a SF BBS doesn't already provide. I use similar controls in Infragistics with regular SF BBSs with no additional programming. It takes about 10 seconds to create a BBS/BO so there is no major overhead during development time.
While you are mainly looking for a wrapper for LookUpEdit, I simply don't see how SF (or any other company) is going to be able to come up with a wrapper for every single control from every third party control provider - it is a task I wouldn't want to do and the time spent doing this could only detract from moving the overall framework forward. As I have already said I don't see the point in doing it either - there is an Infragistics wrapper and I don't use it as I have no need to use it. I would fully expect that if I was using DevExpress then I wouldn't want to use a wrapper either. Now others may say they would like a wrapper but I am still waiting to hear what features a wrapper provides that isn't already available with straight forward data binding with a BBS.
If your real problem is speed as mentioned in one of your other threads then the BBS is not the cause and I doubt a wrapper is going to improve this either.
Sorry for being stupid but I simply don't see what a wrapper is going to give you and what therefore justifies the effort in SF providing a wrapper for each and every third party control on the market.
Aaron