[TYPO3-dev] edit mm tables in backend forms with TCA

[Ernesto Baschny [cron IT]]

Jochen Rieger schrieb am 09.03.2006 09:14:

>> Then an edit pencil to open a window with the corresponding MM backend.
>> Or probably better to show the MM backend on the same page. The user
>> wants to enter the data quickly and not switch between 2 windows.

> I hope I understood everything correctly. I was also in a need of
> something like this. To store attributes that are attached to a certain
> relation between 2 data entries of 2 tables. And this can be n:n as
> well. So ... the non-typo way to do this is to just have a table storing
> the 2 (u)id's plus all the additional fields that are necessary for
> "describing" this relation.

Right, I think we all agree on that.

> So ... maybe there should be an MM-Plus-Attributes option (in the
> kickstarter) that automatically creates a sheet (or a palette) on which
> you have a select option for the foreign uid plus all the fields that
> are part of the MM-table. You get this sheet in the edit mode of both
> records that are related of cause.
> Furthermore a "create new relation" button would be needed thatextends
> the sheet / palette by another fieldset. Alternatively always one set
> more than relations found in the MM table could be rendered extending
> itself after storing data.

So you would replace the current "group" select-box with a new
sheet/pallete that looks something like that?

[ record-1 ][<browse_link>] [add-data-1.1]... [down][up][del]
[ record-2 ][<browse_link>] [add-data-2.1]... [down][up][del]
[add new record]

I think this is also a very nice idea. My way of thinking was that since
we already have most of this (record-list, browse-link, down/up/del
icons) in the group select-box, we just need to add the handling of
additional data there. Which is what I proposed.

But your idea might be more UI-friendly, as the user can see right away
which relation hold which additional data and edit them in a TYPO3-way
using the "well-known" icons (like in Web>List>).

I can already imagine using this to store caption/alt/title/longDescURL
information along with the link to DAM-records in image/textpic
tt_content records, so that we don't need the ugly "captionSplit"
anymore. We could then even have RTE capabilities for those fields (much
requested for "caption"!).


Cheers,
Ernesto