Quote:
I totally agree!

Thankfully, we have developers form around the world who contribute to XOOPS! Some have better know-how of English, some not, and therefore sometimes there will be mistakes! But that's why we're a worldwide community to help each other to make XOOPS the best CMS!

So if we see bugs, or missing translation, or any mistake in documentation, let's help each other and fix it. We are Open Source!!!!

Quote:

Maybe create a poll?

Quote:

Thanks kris,

Modules that run on Xoops 2.5.4 without trowing deprecated messages and that do not use functions/defines/classes marked as deprecated in the source code will run in 2.6.0.

We will be doing a step by step code refactoring. Xoops 2.6.x will trow deprecated messages for 100% of the actual Xoops modules, meaning that our blue modules will have to be refactored if they want to work on Xoops 2.7.0.
In each middle version we will drop deprecated code.

Refactoring for 2.6.0 will be small work for module developers that already have blue modules. Many of the replacements can be done with search and replace.
$GLOBALS['xoopsConfig'] becomes $xoops->config
$GLOBALS['xoopsModule'] becomes $xoops->module
$GLOBALS['xoopsUser'] becomes $xoops->user
etc, etc

And for functions, many can also be changed with search and replace:
xoops_getModuleHandler() becomes $xoops->getModuleHandler();
etc, etc

Templates from database are also not being used by the core anymore but we will maintain the tables for legacy compatibility until 2.7
Instead of using:
$GLOBALS['xoopsOption']['template'] = 'db:mytemplate';
include XOOPS_ROOT_PATH . '/header.php';

You use should use $xoops->header('mytemplate.html');

The above also works for admin side, the interface for front end and admin is the same.

Module developers can/should also remove file includes for core classes. Classes are being loaded 'automagicaly'.

We will need to document all this but we don't even have an alpha yet. Interfaces may change.

Can you create a xref of the 2.6 code? Thanks.

Quote:
Of course, and his comments were not "xenophobic", but related to the fact that the file size was "hard-coded", i.e. it was not possible to translate them into English.

TDMDownloads is a great module, used by many people, and I'll be working personally with Mage to make sure that the English translation is OK there.

But again, that's what Open Source is all about it - we help each other to make things better!

I understand that you want to calm things, but we all understood what he wrote:
Quote:

Quote:
Of course!

That's why there is no need to escalate it any further. DCrussader is committed to help in making XOOPS the easiest CMS to translate. He's been working on translations with people from all over the world, helping them to streamline the process of translations. If you read his comments from the past, you'll see that sometimes his comments are sarcastic, but I truly believe that he would be the last one who I would call "xenophobic".

We value contributions from ALL our users, regardless of the country they are from, or how well they speak English. If their English is not perfect, those of us who speak English better, we help them in translations or whatever is needed.

The most important thing for us is the willingness to contribute and making XOOPS a better CMS! English or no English should be NEVER an obstacle holding people back from contributing to XOOPS!

So let's focus on making XOOPS the best CMS that it can be!

Quote:
I would wait till we have Alpha 0 released, as till then a lot of things still can change.

BTW, for those of you who are interested in the progress of XOOPS 2.6.0, you can follow it in our SourceForge SVN.

And you can subscribe to the SVN mailing list to be notified of every commit to the SVN.

@Trabis : -> http://tutos.xoofoo.org/uploads/docs/dev_xoops_260rv8307.chm

ghost module change for 2.6.0-dev -> http://xoofoo.svn.sourceforge.net/viewvc/xoofoo?view=revision&revision=731

in a few hours I put the links to the html versions of the API documentation

@Trabis -> http://dev.xoofoo.org/xoopsphpxref/x260_rev8307/nav.html?index.html

with doxygen, coming soon

Thanks Kris :)

Good work on the ghost module.

I've noticed you did not rewrite the index.php yet´

Here is an example of how you could do it:


Nice and pretty!