[TYPO3-core] make class.t3lib_db.php usable for backend modules

[Holzinger Franz]

Hello Ingmar,

>Holzinger Franz wrote:
>  
>
>>This list module should not exist at all. However it has not been 
>>possible to use the t3lib_db because its class is instantiated directly 
>>in the file.
>>    
>>
>
>Please take a rest and make sure the class you are talking about is 
>really called t3lib_db!
>
>The subject of this thread is "make class.t3lib_db.php usable for 
>backend modules" which sounds just confusing because t3lib_db is already 
>usable for backend modules as $GLOBALS['TYPO3_DB'].
>
>Is it db_list you are talking about?
>
>  
>
All the code from class SC_db_list { (in db_list.php)
has been totally copied into
class tx_graytree_db_list { (in modfunc_list_list of Graytree Library 
next version not in TER yet)
And then some lines have been added and small modifications have been made.


class recordList (in typo3/class.db_list.inc) and class localRecordList 
extends recordList { (in typo3/class.db_list_extra.inc) are totally used 
from
class graytreeRecordList extends localRecordList { (in 
ext/graytree/modfunc_list_list not in TER yet)

Only the methods where modifications have been necessary have been 
copied to that class.

So I am really talking about db_list.php. We from the Commerce 
development team want this to be incorporated into db_list.php.
E.g.
class SC_db_list extends db_list_base {
}

An empty code should be here in future. All the contents of SC_db_list 
should be in the new class e.g. db_list_base. db_list_base would have 
the modifications (or better than there) of tx_graytree_db_list.

And the rest of modifications in class graytreeRecordList should be 
incorporated back into class recordList  and class localRecordList.

Greetings,

Franz