Feature #67690
closed
FAL - Add managable selectfield for purpose definition
0%
Description
related #67679
It is "think about worth" to add a dropdown field to the fal items (by core) which delivers a purpose select field out of the constants or page/user ts.
That way it is possible to change the behavior per item out of the usecase perspective.
Usecases¶
- You want to place images or videos in different locations within the contentelement
- You want to have a teaserimage out of the contentelement which is not visibile in the contentelement itself
- You want to fill a imageslider and static images in the same content element
- You want to show different images depending on the viewport, template or whatever
- the latter on . . .
What do you think?
Updated by Frans Saris about 9 years ago
- Status changed from New to Needs Feedback
Have a look at ext:news. There you can set a "Show in preview views" checkbox for added media items. Do you have something like that in mind, but then instead of the checkbox a dropdown?
Updated by d.ros no-lastname-given about 9 years ago
Frans Saris wrote:
Have a look at ext:news. There you can set a
"Show in preview views"checkbox for added media items. Do you have something like that in mind, but then instead of the checkbox a dropdown?
Concept is similar but with the approach above much more flexible and powerful. So yes.
Updated by Alexander Opitz almost 9 years ago
- Status changed from Needs Feedback to New
- Target version set to 8 LTS
Updated by Riccardo De Contardi over 7 years ago
- Target version changed from 8 LTS to 9.0
Updated by Susanne Moog over 5 years ago
- Status changed from New to Rejected
FAL meta data is easy to extend to fit your use case (look at the core extension filemetadata, dropdown status for example). The decision what implications a selection has is on the programmers/integrators side anyway, so I'd rather not implement a basically "non-functional" field into the core.