In essence, the Lightworks code is now split in two-the OS independent code (eg. Once this was complete, we were then able to begin work on a Linux implementation of that same layer. Instead, we decided to move it to a new operating system dependent layer which we engineered to have an OS independent interface. Our solution was to avoid rewriting the Windows-specific code at all (it was, after all, tried, tested and optimized). How do you keep shipping Windows builds whilst the work is underway?.How do you rewrite that much code in a sensible timeframe.When we started the move to make it cross-platform 18 months ago, we were faced with a number of challenges, including: The Lightworks codebase is quite large-close to a million lines of code altogether-and some of it has been in existence for nearly twenty years. When did you decide to make the majority of Lightworks' code OS independent and what was your approach to doing this? It remains a no-cost option for cross-platform video editing, but for open source video editing options, read our state of video editing report. Lead Developer Rob Fearnside answered questions from Red Shark News about how it got to this stage.Įditor's note: The intent for Lightworks to go open source seems to have been abandoned. Lightworks, a high-end non-linear video editor, was approaching its public testing phase for its Linux release.
0 kommentar(er)
