Feature #75266

Flexform: Palettes for Flexform

Added by Christian Platt about 5 years ago. Updated about 1 year ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2016-03-25
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
FLEXFORM
Complexity:
Sprint Focus:

Description

There should be a possibility to have at least 2 fields beside each other.

Think of having something like start and stop. It would be nice to have these items beside each other in column. In TCA its possible, bot not in Flexform. Because my understanding of flex form is an interpretation of TCA, it should be a must hast, not only a nice to have,

There are some experiments in the web to solve it by CSS... There are some discussions over the last years, but i guess, nobody asked for that.


Related issues

Related to TYPO3 Core - Feature #66589: Allow class for flexform sheet tabs in backend for better field formattingRejected2015-04-25

Actions
Related to TYPO3 Core - Feature #92903: Add ability to use FlexForm fields in TCA showitemsUnder Review2020-11-22

Actions
#1

Updated by Christian Kuhn about 5 years ago

From a semantic point of view, 'palettes' in tca is basically a sub-array of 'types'. But 'types' does not exist in flex at all. Also, the '--div--' thing from types in tca is done in flex on a totally different structural level, they have those 'sheets', so it is basically not possible to arrange flex fields within a form similar to how it is done in tca. That means, you'd probably have to make up a new syntax for palettes within flex form, making this stuff even more complex. Considering the fact that flex form definitions are incredible ugly to read already, this is not a path i'd follow here.

So, while it is true that flex forms have less freedom in arranging form fields compared to what plain tca provides, it is also rather ugly to implement this stuff and it would bloat this ugly construct even more.

With the refactoring of FormEngine in version 7, it is however now possible to do bigger changes on the TCA side, too. I have quite some ideas for a "tca 2.0" in my mind that could resolve the types and palettes sections (and the inline child tca overrides and the display conditions) of TCA in a much more powerful - but easier to understand and configure - way. Together with the fact that we're now able to on-the-fly-migrate TCA and flex to new syntax if we decide so, we do have the freedom to restructure bigger parts in the future.

But, this will take more time and I currently see no option to have a main TCA restructuring in v8, there is too much other stuff that is in the works already.

So, I'd be in favor of not touching those limits of flex forms at the moment, but instead handle this if we come back to a bigger rebuild of TCA structures later.

#2

Updated by Benni Mack over 4 years ago

  • Project changed from 78 to TYPO3 Core
#3

Updated by Susanne Moog about 1 year ago

  • Category set to Backend User Interface
#4

Updated by Jonas Eberle 4 months ago

  • Related to Feature #92903: Add ability to use FlexForm fields in TCA showitems added

Also available in: Atom PDF