Re: [K-3D dev] K-3D news!

[Ben Campbell]

P. Christeas wrote:
> In principle the idea is that such a piece of software is split into two 
> parts: an engine (3d processing) and the frontend. There is a wide range of 
> reasons to do so (I also know the reasons not to).

From my brief digging around in the K3D codebase:
The front end/GUI stuff all seems reasonably well abstracted already - I 
 don't think the split you talk about requires a major rewrite, just 
lots of small refactoring operations.

Ben.