QUBICLE CONSTRUCTOR 2.0 DEVELOPMENT BLOG

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

Week 3: Qubicle Core

Another week of refactoring the source code. Last week I redesign the complete tool handling libraries. This time I go a level deeper: Qubicle's Core. The core libraries of Qubicle 1.x manage a flat hierachy: there's a list of matrix data somewhere in memory, you have commands to manipulate the data, some other commands to save and open it from disk and finally routines to render the voxels. As long as there are simply matrices and little more this is a fast and simple solution.

Qubicle 2 is getting more complex. And I already planned Qubicle's future features after 2.0. I figured that Qubicle 2 would somehow still work with Qubicle's 1.x Core - with plenty of workarounds - but 3.0 defintely not. So I decided to prepone rewriting the core and making it ready for the future. And there's one more thing I want to do....

Qubicle Core Open Source

Yes, I will open source parts of Qubicle because I think it's a good strategy to increase Qubicle's popularity. With Qubicle Core you will get the source code to open Qubicle's new file format, access, edit and create voxel data and of course render it. The new structure is node based offering some cool new features like instancing and paranting. All nodes can open,save and render themselves. Furthermore values like the position of a matrix are keyable so you will be able to animate.
Qubicle Core will be realeased after Qubicle 2.0.

Merry Christmas and a happy new year

That's the last post for this year. If you've got any questions about Qubicle Core please use the comment area below. See you next year! And have a nice time with your family.
Cheers, Tim