[TYPO3-UG US] OT: Forms, accessibility (was Drupal vs. TYPO3)

Christopher Torgalson bedlamhotel at gmail.com
Thu May 7 16:51:47 CEST 2009


On Thu, May 7, 2009 at 1:42 AM, JoH asenau <info at cybercraft.de> wrote:
>> Why the patronizing attitude? What does ANY of this have to do with
>> this thread?
>
> Well - on the other hand, what has the ridiculously complicated templating
> method of sr_feuser_register to do with this thread? :-) After all it's not
> TYPO3 that does it this way or forces the extension developer to do it this
> way.
> So if you compare TYPO3 and Drupal you should not include a particular TYPO3
> extension.


As I've already pointed out, there's really only one extension that
does this job for TYPO3. But the same is a core capability of Drupal.
The comparison is completely valid.


> Out of the box you can easily setup a TypoScript FORM element using the
> dataArray method and hand over the data to a userFunc that handles
> evalutation and DB actions. Of course this userFunc is not available out of
> the box but the forms are. And if developers would use this FORM element (or
> other TS cObjects as well) instead of HTML templates with thousands of lines
> and markers, many things would be much easier for the end user.
>
> I did a tutorial about that in Dallas and Zach Davis had a talk with almost
> the same topic and we both came to the conclusion that it's not a problem of
> TYPO3 itself but a lack of TypoScript knowledge among extension developers
> that makes working with many extensions so mindsplittingly complicated.


I pointed out both of these things too if you read to the end :)


-- 
Christopher Torgalson
http://www.typo3apprentice.com/


More information about the TYPO3-UG-US mailing list