TYPO3 Core

Some issues involved here have already been integrated in core.

These are the things that are affected by the cObj-XCLASSing in gsi_mailform_ext:

a) "Form prefilling for FE users (name and email plus user defined custom fields)". Not possible yet. Maybe it would be useful to add some stdWrap property to fill in defaults for certain fieldNames to the FORM object?
b) "New field type label: like comment, but with label and free text", this has been integrated into core already
c) "New TypoScript property anchor of the FORM content object: sets an HTML anchor (#) to the form action": this can be done with regular TypoScript means already (add a tt_content.mailform.15 to the COA with the needed anchor)
d) "Bug fix: correct sorting of form elements (TypoScript form data array)": This hasn't been included yet into core.

in dmc_image_alttext and sl_css_imgtext:

e) The new added possibility of the +split function in stdWrap (returnKey by Michael Stucki) makes these things possible without XCLASSing, using TypoScript. Already in 4.0beta1. This will be also be used by the integrated cron_cssstyledimgtext in css_styled_content.

in tableswithoutp:

f) This can also be solved with TypoScript already, as it being done in 4.0beta1 (t_content.table.20.innerStdWrap)

So only a) and d) has to be considered here.

It might be interesting to scan the whole TER-repository for extensions that XCLASS the cObject. Can this be done automatically?

These plugins XCLASS this file:

'kb_betterstdwrap',
'smile_categorization'
and my
'tm_contentaccess' (not however as a core feature but
just as an option).

Usually if there are some stdWrap's in the code, you won't need a hook, because TypoScript is the hook then (just use postUserFunc or similar to do your stuff).

1) kb_betterstdwrap:

adds a new getData type 'glob'. We could have a hook here where an extention could add any new 'getData' type. Comments?

2) smile_categorization

it appends some query parameters to the getWhere(), using the new TypoScript "whereCategoryIn" parameter in the 'select' function. I think this could be solved directly via TypoScript with no XCLASSing needed (using select's 'andWhere', which is already going through stdWrap, so the author could use postUserFunc here).

3) tm_contentaccess

I can't see any change being done by your code to the original cObject from 3.8.1. So maybe your changes have already been incorporated into core?

still a big +1 for me cause I need now (another) xclass for adding different classes to the fields

OK. So anyone writing the hooks where they want them to be? Since 3.8 there have been quite some hooks added to tslib_cObj.