Japanese people do the general housecleaning at the end of week.
I do the cleaning of the altsys codes which are quite dirty.
I've cleaned myblocksadmin up.
And I dropped codes for XOOPS2.2 and common/spaw as trash.
Newly, altsys supports ImpressCMS.
It makes all "D3 Modules" can work fine with ImpressCMS.
Though I don't have time to test XOOPS 2.3, altsys perhaps works fine if XOOPS 2.3 is structurally identical with ImpressCMS.
And altsys starts to support common/fckeditor (fckxoops) for custom block's WYSIWYG editing.
And so on..
Since the new myblocksadmin is fully scratched, it might includes some bugs.
I'll be appreciated if you report bugs.
But this Block Procedure Class is very useful when developping XCL (not X2 :-p).
More developper may use this class. So. I write it now.
http://xoopscube.wiki.sourceforge.net/Legacy_Module_Development_Block_XCL_Style%3Bja
GIJOE wrotes:
To confirm it, tell me the module using cl::blocks other than Xethna modules, please.
I cannot test Xethna modules no more...
So, I hope that BlocksAdmin will be available in XCL Block Edit Form using cl:: blocks..
I add below code at
xoops_trust_path/libs/altsys/class/MyBlocksAdmin.class.php:: in line 758.it works. (in HD SVN .^^; )if (altsys_get_core_type() == ALTSYS_CORE_TYPE_XC21L){ $legacy_block =& Legacy_Utils::createBlockProcedure($block); $block_data['cell_options'] = $legacy_block->getOptionForm(); } else { $block_data['cell_options'] = $block->getOptions(); }
if (altsys_get_core_type() == ALTSYS_CORE_TYPE_XC21L){
$legacy_block =& Legacy_Utils::createBlockProcedure($block);
$block_data['cell_options'] = $legacy_block->getOptionForm();
} else {
$block_data['cell_options'] = $block->getOptions();
}