Deprecate Dropzone for 2.x, remove it in 3.x

[Kocal]

For the same reasons than #2732, #2733, #2740, ...

[smnandre]

To me there really is something to offer there, but not with the current version clearly.

So let's start working on the next version? @sblondeau ? :)

[Kocal]

What do you have in mind? 👀

Because at the moment, Dropzone is legit only a FileType with an already configured placeholder attr and few opinionated Twig, JS and CSS code.

[smnandre]

cf #2642 #2704 #2747

And it's a package used.. because a decent image upload preview is something interesting.. But if this is only JS i'm still on the same position there is no added value.

But ... if this comes with other things related to back-end, I do see the point

[Kocal]

As you said in #2704 (comment), I also think providing opinionated Twig/JS/CSS code is not safe enough for us nor the user.

Maybe, instead we can provide some Twig components to let user define their own UI:

<twig:Dropzone>
    <twig:Dropzone:Preview>{# ... #}</twig:Dropzone:Preview>
    <twig:Dropzone:Upload>{# ... #}</twig:Dropzone:Upload>
</twig>

but, that also too opinionated...

When deprecating and removing this package, I had in mind to migrate it in a UX Toolkit kit, through the Recipe system:

• bin/console ux:toolkit:install-recipe Upload
• install a dedicated FormType, some Twig templates/components, a Stimulus Controller, and styles
• the files mentioned above would be fully customizable (since it uses the same behavior than installing a Component from an UX Toolkit kit)

WDYT?

[smnandre]

Seems a very good idea 🤝