It's all about gaining critical mass upCASE. If that requires to give a little "preferential" treatment to windows users then it is justified. Also, most linux people are used to compile and that kind of stuff, so is not like they'll miss this thing as much. Mac users will want it also, but they are by far less, so again, it is justified to focus on windows users in order to gain momentum. The rest will come by inertia.upCASE wrote:Hi!That may be true for the windows people. Sure we could do release a precompiled DLL and a lib for VC like Qt used to, but then the gcc using people would come and demand the same. What about Mac and Linux users?priyank_bolia wrote:Whatever you die hard fans say, but I believe, if there was just dll, lib, and cpp/h files to just copy into the project and a hello world wizard. It would attract atleast thousands of MFC programmer to switch to wxWidgets.
I agree with priyank, it is about time for wxWidgets to become popular, there is no toolkit that compares in terms of features, good implementation, price, support, etc. and the easy path to make something popular is to make it popular for windows users.
I think the issue here is to "get hooked" programmers. Once they get a taste of wxWidgets they can (and probably will) spend more time tweaking their configurations in order to produce lighter executables, etc. Somehow, thats why wxDevCpp has been so successful. Just look how many posts its forum section gets daily.upCASE wrote: And what if I don't want to distribute a wxWidgets dll everytime I ship an app?