On 07/18/2015 05:29 PM, Tom Davies wrote: > If programs plan to become cross-platform then initially writing for Linux > seems to be the optimum route.
If a programming team delivers a usable Linux product in one year, then for a second platform, it will take the same team six months to deliver it. If a programming team delivers a usable Windows product in one year, then it will take a second team that is twice the size of the first team, two years, to deliver the program on a different platform. FWIW, writing to WINE/LibWINE is equivalent to writing a program for Windows, in terms of overall productivity, and cross-platform support. Furthermore, with WINE/LibWINE, your program won't have the same look and feel as other software on the same platform. jonathon * English - detected * English * English <javascript:void(0);> <#> > Writing for Wine is a neat trick that i have not heard of before. It sounds like it neatly avoids any need for porting at all. It also means that bug fixing is an order of magnitude more difficult,because bug isolation requires looking at: * your source code; * The WINE/LibWIN library; * The OS that the bug was reported on; -- To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
