I hope 3.0 will very perfect and thanks DJ do the greate work
but we still need listen more voice and request more developers like Catz to make XOOPS better, right?
1+
I hope 3.0 will very perfect and thanks DJ do the greate work
but we still need listen more voice and request more developers like Catz to make XOOPS better, right?
Because he is not ready yet to publish it. That's how many developers work! They work on their "intellectual baby" on their computers, till they are ready to introduce it to the world.
Problem is with point 2, 3.0 is interfering with the current branches development as DJ want us to look into forward compatibility(impossible since core developers don't have access to 3.0 yet)
It is VERY important that we can review and approve 3.0 (even if in alpha state) in order to keep developing 2.5 and eventually 2.6.
How much of your request is a simple "curiosity", and how much is a real desire to jump in and help?
I understand the frustration of some developers, and as DJ said, I've been been harassing him for the last 6 months for dates. And I want to believe that we're getting close to the end of this journey, when 3.0 Alpha will be released.
But as much as we want it "right now", we cannot forget that we are all volunteers and we're doing the development in our free/spare time.
It saddens me that we so often just "demand" things from those poor souls, regardless of what is happening in their personal lives. Do we know if somebody died in their family? If they lost their job? If a new baby was born? If they got married and got divorced? Or if they got sick?
I would hope that you would give me some credit that after almost 6 years on the project, I understand at least some of the problems here But sometimes throwing the baby with the bath is not the best solution!
I will take your recommendations and go back to working on Xoosla.
First you get furious because it has been changed to "Module Developer", so I changed it back to what you wanted, and now you don't want it anymore?
John, why this drama?
We just didn't want to leave people who are still on PHP4 with a version that had bugs, so we had 2.4.5 as a "maintenance" release. Of course, all the changes in 2.4.5 would be merged into 2.5.0.
So this is the explanation why we had 2.4.5 and 2.5.0 at the same time. A simple time overlap, while trying to be "customer driven" and taking care of our users on PHP4.
Regarding 3.0 is a different story. This will be a different architecture, while keeping compatibility as much as possible with current XOOPS modules. Since it is a major task, and kind of experimental design, DJ was working separately on this to create a proof of concept.
The idea is very simple - it's Parallel Development.
Quote:and what about the 2.5 ajax develop by xoops france team...what is xoops next plan?...
if xoops 3.0 comes out...how it will be merge with 2.5 ajax ?
We don't develop xoops 2.5 because we do not know if our work will be included or not in xoops 3.0. We do not want to work for nothing.
This approach is also based on our experience with Skalpa and his new version of XOOPS. For those of you who aren't here long enough, Skalpa, who was the lead developer in 2005, proposed a new XOOPS version called XoopSphere. A great concept, but while he was working on it, everything else stopped, and everybody waited for this new version. After a year of waiting, Skalpa was not able to finish it due to health issues. So we've ended up without the new version, and with wasted one year because we didn't work on the standard XOOPS version.
I trust DJ that he'll deliver the new version, but we couldn't take again such a risk as with Skalpa (in case DJ get sick, or get hit by a bus, etc.). So in order to avoid this kind of risk, we've continued with 2.4.x and started work on 2.5.0.
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.
Quote:But, honestly, DJ should have had something workable by now. I did Zarilia in a year on my own. Xoosla refactoring in three months, Eduardo did Exm in a shorter time and the same with Simple Xoops.
John, let's not start a "pissing contest" here. What are you trying to say? That you're smarter/better developer than DJ? Is it really needed this kind of approach?