The current development status is in a final stage as described in this post.
XOOPS Cube Legacy consists of XOOPS Cube layer and Legacy modules. And, Legacy doesn't use all of XOOPS Cube features. Therefore, I had to develop another base module which isn't Legacy for testing the design of XOOPS Cube layer. As you know, that's Shade. I have decided main spec which the project team couldn't try in Legacy, in Shade. Those are Context, Identity, Principal, Role, Service and many changes. But, Legacy module is keeping older XOOPS Cube layer than Shade, for our test process. If XOOPS Cube layer in Legacy is updated anytime, it's very difficult to find the cause of the bug. For that, XOOPS Cube layer in Legacy is fixed for a moment. Meanwhile, XOOPS Cube layer in Shade is updated many times. In other words, the project team is going ahead with two projects which are Legacy and Shade now.
Perhaps, merging the latest Cube and Legacy will bring many problems. Therefore, we have to fix all of bugs in Legacy until Cube and Legacy will be merged.
Our active goal is Legacy 2.1.0. This version may not be able to emulate all of functions of XOOPS2. For example, we can't do preview in the custom blocks... That's no good. But, the future version of Legacy will be implemented it. In other words, none fatal problems are ToDo for the next version. Fatal problems in Legacy for us are the following:
- No run.
- No compatibility.
- No helps.