[TYPO3-dev] Import Extension from TER
Martin Kutschker
martin.kutschker-n0spam at no5pam-blackbox.net
Mon Apr 14 08:37:38 CEST 2008
Jeff Segars schrieb:
> Hey Francois,
> Thanks for the testing!
>
>> > This behavior was introduced in changeset 2643, which adds user
>> > function support in the Constants Editor.
>>
>> Could you outline the advantages of those user functions?
>
> In Calendar Base, we have a variety of Typoscript contants for
> specifying pages to save data to and retrieve data from. Using user
> function support inside the Constant Editor, we can add the standard
> link wizard popup from TCEForms so that a backend user doesn't have to
> figure out the PID on their own.
This is great, but if you had extended the constatnt editor with a pid
type every extension could have benefited from this.
> We also allow the backend users to pick both frontend users and groups
> that are allowed to use the frontend editing features. With user
> function support, we can render a listbox with the actual usernames and
> group names rather than making the backend user enter a comma separated
> list of UIDs.
Again this looks like a feature of general interest.
> The last example that comes to mind is choosing what extensions to use
> for locations and organizers within Calendar Base. We support a variety
> of data sources for this data (tt_address, partner, frontend users, and
> our own internal table). Adding user function support allows us to only
> display the data sources that are available on the system rather than
> showing all possible data sources and having the user define a bad
> configuration.
This really looks like custom code.
>> Why is it necessary that the extension be installed first, since the
>> source code is available anyway (as Masi already pointed out).
>
> I wasn't involved in this portion of the code orginally, but I don't
> think there's any technical limitation that says it has to be this way.
> It's a non-trivial change very late in the release process though, so I
> certainly understand Ingo's hesitation.
I original thought that only trivial encapsulated code would be
necessary to display custom fields.
I suggest to make the first two options a standard feature of TYPO3 and
to display the form immediately if no custom fields are necessary. If
they are then show a big warning that you have to come back to the
configuration once the extension is installed.
Masi
More information about the TYPO3-dev
mailing list