[Typo3] Making extensions, which use XCLASS - some problems

[tapio]

 > I'd go for:
 >
 > class ux_ux_SC_alt_doc extends ...


Ok. Thanks - this helps a little bit and I understand the extension 
method of Typo3 better.

But there is still some problems and that doesn't work alone.
The extension, which is used in the 'extends' (in this case 
'ux_SC_alt_doc' needs for example this statement on the bottom:

// Include extension?
if (defined('TYPO3_MODE') && 
$TYPO3_CONF_VARS[TYPO3_MODE]['XCLASS']['typo3conf/ext/tm_contentaccess/class.ux_sc_alt_doc_tm.php']) 
{ 
include_once($TYPO3_CONF_VARS[TYPO3_MODE]['XCLASS']['typo3conf/ext/tm_contentaccess/class.ux_sc_alt_doc_tm.php']);
}

and the extension, which use that needs corresponding statement, in this 
case
$TYPO3_CONF_VARS[TYPO3_MODE]['XCLASS']['typo3conf/ext/tm_contentaccess/class.ux_sc_alt_doc_tm.php'] 
= t3lib_extMgm::extPath($_EXTKEY) . 'class.ux_sc_alt_doc.php';

That would not in certain situation be a problem, if dependencies are 
known and certain plugins require some other plugins, which extens the 
original 'SC_alt_doc' class.

The problem is that everything should go in correct order.

On what principle Typo3 reads ext_locallang.php files.
File, which has 'extends ux_SC_alt_doc' must be loaded *after*
the file which has 'extends SC_alt_doc'.

in my case Typo3 reads 'tm_contentaccess' *before* 'erotea_date2cal'
even if in the 'localconf.php' in '$TYPO3_CONF_VARS['EXT']['extList']'
*after* 'tm_contentaccess'. At least the extension list can't control this.

The order should be *opposite*.
If dependencies has been set, this might be controlled?
If I set that 'tm_contentaccess' requires 'erotea_date2cal' does that 
change the reading order?





It seems that ux_ux_ becomes too complicated in public extensions.