Translations
Info
All page names need to be in English.
en da  de  fr  it  ja  km  nl  ru  zh

Grid View Fixes and Improvements

From TYPO3Wiki
Jump to: navigation, search
This page belongs to the Core Team (category Core Team)

Current Status

Currently the bugs 25161, 25157, 24992 have been fixed already.

So the list view and the editing form already match the selected grid regarding labels, available items and available positions while moving an element.

ToDo

Commit the changes using the new tools we agreed upon during this sprint. Will happen as soon as GIT is running properly on my system.

Bugs

  • 24909 "unlimited colPos value in Grid Wizard"

Planned New Features

Features Pending in BT

New ideas for 4.6

Peter mentioned a simple approach how to get Grid View support on Content Element level. We would need just one additional field to determine the parent element and exclude the element from the usual rendering process. Then we could still use the colPos field do determine the position of this particular element within the grid of the parent.

Another approach would be to "shift" the existing "Insert Records" element to a grid layout, which would be better if you want to use the same CE within more than just one parent.

As there are plans to implement CE drag & drop in 4.6 anyway, we thought about a new part of the user interface. This new "draggable CE repository" will be positioned at the left side of the page module and can be collapsed the same way as the page tree. It will enable people to:

1. Click on one of the default elements or a custom content element to open up an editing form and position it later on 2. Drag each of these elements directly from the repository into a position of the page or CE grid to create a dummy element there, that will already include dummy texts, images, tables or whatever content is expected there 3. Move elements around between page and content grids

This new "draggable CE repository" will be positioned at the left side of the page module and can be collapsed the same way as the page tree. This way we can make use of a kind of content element wizard without actually having to leave the page module.

Lars already got some drafts for the layout and we already discussed things with Jens and found out that a similar layout for this repository bar will fit the new form element as well. Xavier as the RM for 4.6 has already been informed about these drafts.