Forum Index - Topic Index Core Development
XOOPS Cube Legacy development reports | Register To Post |
| Threaded | Newest First | Previous Topic | Next Topic | Bottom |
| Poster | Thread |
|---|---|
| minahito | Posted on: 2006/9/11 9:55 |
Home away from home ![]() ![]() Joined: 2005/10/6 From: Japan Posts: 398 |
XOOPS Cube Legacy development reports Hi guys,
I report the status of XOOPS Cube. XOOPS Cube Legacy 2.1 Alpha4-e has finished implementing most functions to emulate functions of XOOPS2. Legacy has the standard cache module which implements interface for generic cache strategy. But, this concept is too old. So the standard cache module has to be replaced with other concept which is better and high speed. 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 really bad. But, the future version of Legacy can implement it. In other words, none fatal problems are ToDo for the next version. Fatal problems for us are the following: - No run. - No compatibility. - No helps. Legacy still doesn't include interfaces of the latest version of XOOPS Cube layer. That is merged in Beta branch. Therefore, we have to remove all of bugs in alpha duration. This week is very important to fix the final version of Legacy 2.1.0. (You may read the explanation about this relationship in Ayumi's better English here )About the help documents, XOOPS Cube Legacy wants to contain both English edition and Japanese edition. I have written some documents in Japanese. But, that's no enough. I think that it's good to prepare English documents at the start. After then, we try to translate those documents. But, two editions have to be the same content any time, because those documents are official documents. Therefore, it's important the help document is simple, for translation. Wiki is good for us to write drafts together. Because the help documents are not program, we have some leeway to fix it. I think that we have to try various module in Alpha4-e, this week. See wiki page. I copied reports of Japan community about the compatibility to Wiki. Let's share results. About features of XOOPS Cube layer, I'll report at next time.
|
| minahito | Posted on: 2006/9/12 13:46 |
Home away from home ![]() ![]() Joined: 2005/10/6 From: Japan Posts: 398 |
Re: XOOPS Cube Legacy development reports
|
| minahito | Posted on: 2006/9/21 16:16 |
Home away from home ![]() ![]() Joined: 2005/10/6 From: Japan Posts: 398 |
Re: XOOPS Cube Legacy development reports The project team has some problems on the Alpha series:
1) XoopsForm::render() has HTML display directly. It's difficult for users to change design. The project team has to implement a template system to XoopsForm. 2) We can get much better cache mechanism. The project team will improve the controller and the cache module for speedy XOOPS. The project team are developing XOOPS Cube abstract layer in the other project, because nobody wants bugs by changes of an abstract layer. The team will merge the latest Legacy with the latest Cube in Beta version. For that, we have to get stable Legacy module in Alpha. Therefore, we'll release Alpha5 which isn't on the Roadmap, for these two tasks.
|
| Threaded | Newest First | Previous Topic | Next Topic | Top |
| Register To Post | |



)