[Typo3-dev] cObj FORM: Make form-name globally available

David Bruehlmeier typo3 at bruehlmeier.com
Tue Jun 8 23:15:39 CEST 2004


Martin T. Kutschker wrote:
> >
> > I guess you did so by also modifying the source of the cObj FORM?
>
> Of course.
>
>  > That would
> > correspond to my proposed solution 2b. I do not see any way around this,
but
> > I guess I cannot publish an extension that requires people to modify the
> > standard of TYPO3.
>
> Well, you could write an extension that makes use of the XCLASS
> mechanism. But that may clash with some other extensions. tslib_content
> has been extended modified by quite a few of them.

Mmmh, I don't think I will go into XCLASSing... I'd rather wait to publish
the extension until there is a good way in the standard where I can get my
stuff running.

>
> Best apporach is IMHO to create a solution that Kasper is willing to
> intergate into the Core. But since this will be only available for 3.7
> and later, you create then (after the apporoval) an XCLASS extension for
> 3.5 and 3.6 (so you can use your extension now).
>
> I have some modfications of tslib_content. Time to dig them up.
>
> Masi
>

Agreed! I will now formulate a feature request for 3.7, probably geared at a
couple of well-placed hooks as they should be easy for Kasper to implement
and offer the most of flexibility at the same time.

Thanks for your advice.
Dave.






More information about the TYPO3-dev mailing list