Language Selection

English French German Italian Portuguese Spanish

Xara LX forked to replace rendering engine

Filed under
Software

The Xara LX vector graphics editor took a big step forward last week. After months of gridlock between open source contributors to the project and its corporate owners, one of the contributors published his own fork of the code base -- and the company approved, offering to host it in the official Subversion repository.

The stalemate stemmed from Xara's decision to exclude a single library from its GPL source code release. That library, CDraw, is the rendering engine responsible for rasterizing the workspace contents and drawing it to the screen during an editing session. Xara is very proud of the speed and quality of CDraw, to the point where it cites CDraw's speed as the chief advantage of the product over its competition. But the company feared that releasing the source code to CDraw would constitute giving up its competitive advantage. Thus when it launched the open source Xara LX project, Xara bundled it with a binary-only CDraw -- but one explicitly licensed as freely redistributable.

Outside contributors expressed reluctance to invest time in the Xara LX project, citing dependency on the non-free CDraw as the reason. The project languished, each of the two camps seemingly of the opinion that the other was not holding up its end of the deal -- the coders regarding Xara's partial source code release as insufficient and Xara finding the coders' contributions insignificant.

Full Story.

More in Tux Machines

today's leftovers

Leftovers: Gaming

Leftovers: KDE Software

  • Wayland & Other Tasks Being Worked On For KDE Plasma 5.4
    Now that KDE Plasma 5.3 was released this week, KDE developers are starting to plan out and work on the new material intended for KDE Plasma 5.4.
  • Interview with Wolthera
    My name is Wolthera, I am 25, studied Game Design and currently studying Humanities, because I want to become a better game designer, and I hope to make games in the future as a job. I also draw comics, though nothing has been published yet. [...] After I played a lot with MyPaint, I heard from people that Krita 2.4 was the shit. When I went to the website at the time (which is the one before the one before the current) it just looked alien and strange, and worse: there was no Windows version, so I couldn’t even try it out. So I spent a few more years having fun with MyPaint alone, but eventually I got tired of its brush engine and wanted to try something more rough. When I checked Krita again, it had two things: a new, considerably more coherent website (the one before this one) and a Windows build. Around that time it was still super unstable and it didn’t work with my tablet. But MyPaint also had tablet problems, so I had no qualms about dual booting to Linux and trying it out there.
  • GSoC with KDE
    So, my project is titled: Better Tooling for Baloo. Let me begin by explaining what Baloo is. According to its wiki page it is "Baloo is a metadata and search framework by KDE." What exactly does it mean? Baloo is responsible for providing full text search capabilities to KDE applications. It doesn't end there it also provides searching on basis of metadata of various types of files. To acomplish this it indexes file contents and metadata using various plugins ,called extractors, to handle different types of files. It then exposes the data it has indexed with the help of various API's. So thats a very high level view of how it works. Now, my project, as the title states will provide better tools for Baloo. These tools will mainly be: