kraven30:
please pay attention that all modules will not worked in 2.6 now until they will be compatible with the new core.
So only modules in the core will work with xoops 2.6.0 alpha 1.
Also Mamba updated soapbox module and you can download from here:
http://xoops.svn.sourceforge.net/viewvc/xoops/XoopsModules26/soapbox/trunk/?view=tar


i found this strict issue in profile module:

My understanding is that most modules will need to be tweaked to run with 2.6. The bigger changes will likely come with alpha 3 with the new database structure.

Assuming we are still on track to use PDO as the new database structure when 2.6 gets to Beta you will likely see a LARGE number of Modules stop working but in MOST cases the changes necessary will be minimal. Should be as simple as changing a method/function call in most cases.

Between changes to the database class and the new xoops class I expect most if not all of the current modules to "break" requiring minor modifications due to what core developers have said in the past.


As to Extensions...
I understand what you are saying about their being simple modules. Eventually I would expect them to truly become extensions and they should be in a different directory and perhaps be totally treated differently than a standard module. Maybe we should come up with a proper description of the difference between a module and an extension. My expectation of an extension is it is code that extends the functionality of the core. This functionality could be used by other systems or plugged in like how PM and Profile are now. PM and Profile should be extensions if they aren't already. Another aspect is that other code depends on it being there to work. Like Rankings... There are A LOT of programs that require rankings to be in place.

One big difference in how they SHOULD work (don't know if they do or not..)
Currently a module is its own entity you access its tables with module specific code etc. My impression of an extension is that it should be included with the core classes as if it was in the core since it really is an extension of the core. The main difference here is that with an extension it gets loaded every time you load the core, a module only gets loaded when you are accessing that module directly. Again, I have not inspected the code to see if this is how it works. With Profile and PM I believe they have worked that way for a long time. Prior to loading those two modules the core has very simple variations of them. Once you install them they supplement the core code that is already in place. Not like how a normal module works.

@irmtfan

Thank you but I have tried with compatible modules otherwise I would not have written on the topic, I changed class/theme.php now it works

redheadedrod:
your post is really informative and i like it.
Quote:
good. I will think about it. generally you are right. many modules uses profile and pm functions and also rank, smilies and ...
previously some module developers also created some modules that just works as a framework: eg: smart object
Or some developers make some multi-purpose modules like Altsys which is a module and a framework.
what i said and want from core team and also others is simple: please do not play with the names. let we have something in hand then we can judge and can name it.

Quote:
actually, profile and pm extends the core abilities. for example pm module even have not any table for its own. it used the core tables.
Also profile module use the _user table and also have some tables for its own.
when you uninstall them the core related tables would not be dropped.

An application (i cannot name it now) in Xoops is needed to extend the core functions. eg: you can see many modules uses the same method to create image or upload classes. I think a system/application should be defined just like "framework" but a dynamic system. then any developer can add its code and share with all Xoops system.
Im not a coder so i cannot explain my thoughts better.

kraven30:
what is your module and what do you change in class/theme.php
thank you.

Blocks modules are leaving when editing module name




in IE8 no blocks



Control Panel (IE8)

Is a module would have his own extensions ? Tag, Social networks, "super admin" features, ...

Quote:

when i said it is confusing i imagined these kind of questions.
now users dont know what is a plugin from a module like tag for other modules and what is the newly released extensions.
actually when i sent some feature to the tracker i thought these extensions would be installed in the core to really extend the core system for all modules that needed that functionality.
example:
Font manager plugin in system module
Quote:

so any module needed a font manager can request/call from this extension.

other example:
http://sourceforge.net/tracker/?func=detail&aid=3543964&group_id=41586&atid=430843

MACTEP:
i confirmed your bug in IE 8.0
It seems a jQuery 1.8 issue.
Quote:


Also i should say something about the new form introduced in modules/system/testform.php

Everything is nice just i wish core team pay attention to requests for including jQuery UI date picker
http://xoops.svn.sourceforge.net/viewvc/xoops/XoopsCore/tags/2.6%20timgno/htdocs/class/xoopsform/formdatepicker.php?revision=10091&view=markup

feature in the tracker:
https://sourceforge.net/tracker/?func=detail&aid=3405407&group_id=41586&atid=430843

Quote:


So I did and said that the blocks are not dragged .And check on the version jquery 1.7.2
Blocks dragged , but problems remain with IE8

In IE7 the same in IE 6 horror! (IE6 and IE7 tested program IETester)

i test in local new beta core...
The moduleclasses was removed? or is only at the moment work in progress?
In this mode all modules do not work updating to 2.6