![]() As you perhaps know, there is no single obvious choice for developing apps on Windows. Lee and Tiho use Qt to develop the Windows version. On top of that, from that point on we'd have to spend time communicating and liaising with that person to ensure all work was coordinated (more difficult when we are spread across the world). Trying to bring anyone else on board would only slow things down, because we'd have to spend our time training and teaching them, and they would have to familiarise themselves with a massive codebase. ![]() There's Brian, too, who works part-time keeping the Windows bug-tracking up to date for us. :) ) But we also have Jennifer, whose main job, along with heading Windows support, is to constantly test the Windows version and point out where it is missing features or minor points of integration that exist in the Mac version and might otherwise be missed (Jennifer being one of the team members who know Scrivener the most intimately). I have to do my best to communicate all of the changes in the Mac version as they happen so that they can be translated to the Windows version (and I'm sure Lee and Tiho would have a thing or two to say about how I do on that score. They work together to build the codebase and get the Windows version working and looking as it should. We have Lee, the lead developer and head Windows bod, and he has Tiho, a hugely talented coder. To this end, the Windows version is a constant back-and-forth. They have to know all of the things that most users will never notice. For a developer to do a good job, they need to know not just what the different features are, but how they are integrated. It's a large app with a big codebase, with huge amounts of code just dedicated, for instance, to the rich text system, or Compiling to so many different formats (the ebook, FDX and Fountain exporters are written from scratch on both platforms on Windows, they also had to write their own RTF converters from scratch). One of the biggest factors, as has been mentioned upthread, is that it is no simple matter to train someone to understand the ins-and-outs of Scrivener so that they know it well enough to code it. There are in fact several factors that slow down development on Windows and which also don't make it feasible to throw more men at it, but these none of these factors is cash. Via a thread their forum, in which it was suggested Lit & Latte could accelerate Windows' development if they launched a Kickstarter to pay for more manpower and whatnot:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |