Dan, Maybe I mis-read something out of context... On http://winehq.org/site/contributing#port_app, under the section "Porting Your Windows Application to Wine" it suggests this.
I wrote uCon (a win32 application) and I would really like it to work with Wine. The majority of it does now. The GUI appears to be good; however, character throughput is not messed up. Kinda like a 1960 Corvette on the outside with a Corvair engine under the hood!!! :-(
Anyway, if it makes more sense for me to just report problems that I have with uCon when running it on wine, that's fine with me. Bottom line is I will do whatever is most appropriate/helpful/efficient to get it running and that includes doing some wine code if necessary.
I also have no problem with changing things in uCon to make it work better with wine. Whichever works best. I'm open for suggestions.
Thanks Ed
Dan Kegel wrote:
Ed wrote:
I'm brand new to the list and would like to get a Windows application that I wrote (uCon) to work with wine/winelib. I've submitted it to the application database. I've tried it on Wine and it *almost* works, so I'd like to pursue this further by building uCon with Winelib (as is recommended somewhere in the documentation).
Egads. Where does it recommend that? Using winelib is a terrible idea unless you really need it (e.g. on non-x86 platforms, it's your only option). The downside is that your app suddenly becomes very fragile with respect to user updates of wine; they need a synchronized version of your app that matches their version of Wine. I've seen this happen, and it's not pretty. Also, this means double the QA and release trouble.
The Right Thing To Do IMHO is just make your app and wine work better together, not use winelib. So your next move is to file bugs in http://bugs.winehq.org describing how your app doesn't work with wine, and work with us to solve them.
- Dan