Sophie2 wrote:
There is no editor that writes code instead of you.
Delphi for PHP helps with writing some of the code
Sophie2 wrote:
There is no editor that writes code instead of you.
He's not developing a new version, he has left XOOPS Brasilly.
xProjects.co.uk is no longer available due to lack of time for support and the demise of Xoops. RIP xProjects
However, when the directory containing the banners were renamed from ..mysite.com/banners/ or ...mysite.com/banner/ to something else, the banners reappeared.
rabideau wrote:
For those interested in working with a community of refugees who still believe in the "essence of the old and true XOOPS" I would encourage you to spend some time with us onhttp://helpxoops.info. We welcome all current and former XOOPS players of good will who wish to work together. We support and encourage and offer help to all derivatives of the XOOPS family and modules.
So much for my cheap and blatant advertisement...
JMorris wrote:
Nobody is irreplaceable. This is Open Source, in spite of what some may think. Members, Developers, Moderators... They all come and go. Those that go are eventually replaced by someone with equal or greater skill and life goes on.
I've watched this for many years here. Even before I registered. I remember when this project was still in the 1.x branch.
Many have come, many have gone, and most of those who have gone have been replaced. All the while, this project has grown and continued to improve.
If Hervet wants to go, let him go. If he wants to return, he may return. Everyone is free to come and go as they please.
JMorris wrote:
I see it as a needed contribution to the community that cannot be implemented on xoops.org domains due to the plans for the site restructuring. I see it as a way to tie all areas of XOOPS together in one, easy to use interface.
Not everything is appropriate for a xoops.org site. As server admin, I sure as h3ll wouldn't want a site hosted on these servers with experimental modules or a site that constantly fetches rss feeds from other sites. Stop and think about it for a second. xoops.org isn't a playground. We have to keep things in perspective and use our resources in the best way possible.
I'm overseeing the server migration so that the new site structure will be fast, reliable, and secure. Some of xoops.org's biggest issues have been because the sites are not hosted on an appropriate platform that is capable of meeting the demands of the xoops.org sites.
XOOPSinfo.com and HelpXOOPS.info deal with XOOPS issues, but as stated above, these are issues that should not be dealt with on the xoops.org servers or domains.
I have thought about this extensively. After reading a lot of discussion about the site restructuring, I came to the conclusion that the new site structure was appropriate and well thought out, but didn't answer every request. This is natural and can be expected. It's impossible to give every user exactly what they want.
My motivation behind XOOPSinfo.com is to fill in a gap that is not practical for xoops.org. Pure and simple.
Until now, XOOPSinfo has pretty much been a one-man-show. I would like to move away from this model and make XOOPSinfo a true community resource. The spirit behind this site was and still is to make it as simple as possible for members to find information.
I look at the contribution to this thread by the likes of JMorris, Carnuke and Rabideau, and then Mambo...
There are many facets to a product such as Xoops, and as was read somewhere in all this was "domain names don't matter." In terms of 'dividing' the community, I don't agree. The more sites that mention XOOPS only multiplies the results in search engines and raises the core site higher in the rankings.