Quote:

I really can not specify a detailed release date.
My plan was to finish one more iteration on high level API refactor and started to invite a few designers and developers to work on basic components during the past weekend. I believe you read my posts in core dev mailing list about front-end frameworks and developers.

But, accidently, I had to stop X3 and pick up 2.4.5 release. Optimistically I would expect one more week on 2.4.5, means that I have to put X3 aside for two weeks.

I had let a developer to lead XOOPS 2.4 with your help, but as we have discussed many times in mailing list, we have problems in the branch.
Again, I really hope we can finish the 2.4 series, either led by you or by me, as soon as possible. Then we can focus on X3 again.

[Added]
Once 2.4.5 Final is released, I will work with X3 internal preview group to evaluate potential work for X3 to be ready for public release, then I give the X3 ETA with the preview group help. Hopefully two weeks after the 2.4.5 Final release.
Is this OK?
If not, let's talk about an practical solution.

Quote:

I would agree with trabis on this.

On the other hand, however, even X3 comes to public soon, it is still in alpha state.
And I have advised developers several times in core dev mailing list: while waiting for the next new architecture, implement new features at module level. In this way we can have desired new features without horrible compat issues, and the module level new features can also be good sandbox for future core features.

As for an ETA of X3, it has been the daily question from mamba for me. I can feel that he is more anxious than anyone of us: no concrete code from me, but more and more pressure from other developers. Sorry mamba, this won't be long.

BTW, the last question from trabis: compatibility, which has been the biggest burden for the XOOPS project.
In the past 10 months of full-time development, 50% of my effort is on compatibility, 30% is on architecture design and experiment, 10% on basic modules and components, 10% on new technology.
As you can see, once X3 goes public, we need a lot on module development.
Now, back to compat issue, as a result of so much effort, I have successfully managed to make the new X3 compat with legacy modules and new engine. For example, if you have an SEO solution for a legacy module, it will work with new architecture with new SEO solution for new modules. And of course you can switch your SEO solution to new SEO engine without changing your module backend.

Creating a logo manager is necessary.
The hard part is that the manager needs to be friend to both back end, site management or resource management, and front end, theme design.

On admin side, for administrators:
logo controller responsible for
logo upload
logo browse
logo edit, mainly for cropping and resizing


On view side, for theme designers:
We could build some widget-like plugin, which will be available in next major version:
<{logo size=84:31}>
which will be matched tohttp://img.xoops.url/images/logo/logo-84x31.png

By the way I sadly find that I have lost much of my speaking skill since I have been so deep in code for so long time.
Hope my documentation skill will be recovered soon once I move on to technical documentation.


Sorry I can not spend too much time on the subject right now.
We need to finish the 2.45 release in the weekend.
After that we will have more and more on our new version of XOOPS, for sure.

Quote:

Actually I have been working on X3 full-time since long time ago, every day and night. Even for right now, it is 12:40 in the evening for me, I am still writing code X3.
Thus I have been quiet on the forum, just discuss SVN topics with other developers in mail list.

The good thing is that after so long time hard design and development, a brand new architecture with basic services is being finalized. Actually I have started to invite other designers and developers for internal preview, especially ajax for user experience improvement.

I hope a small group of developers and designers will start to expand the X3.

When? I would say very likely in two weeks.
before that, we will have a brief architecture description and by next week.

The xo- namespace will be dropped off in X3

Please be careful with 'xoopsPreload', it is not officially supported in XOOPS 3 although there might be some compatible solutions.

Before the new API list for X3 is released, please build your new functionality at module level, not rely too much on new classes or APIs introduced in after X2.3.

But anyway, all modules for 2.4+ will be supported with some compromising way.

Quote:

+1

Yes, I am alive, together with the project.

It is painful to keep deadly quiet such a long time.

I can not tell much at this moment.
Simply speaking, I am trying to get XOOPS to catch up with new developments in PHP, MySQL while keep backward compatibility as much as possible.

We will have a new architecture with solid library for developers.