Feat: Drop jQuery and bootstrap

[kl3sk]

Hello,

I think jQuery can be dropped in favour of vanilla JS.

• Select 2 can be replaced by nice-select2
• DataTable can be replace by simple-datatables

On the other hand, Bootstrap can be dropped (but used as a separate template or leaving its classes),

last but not least, all assets could be managed by the new (I didn't test yet) Asset mapper.

This could reduce dramatically the size of the bundle to be focused on what it is meat to be "Schedule", and let the user to choose their own strategies.

Note:
Unfortunately Boostrap confirmation is not Bootstrap 5 ready (and may will not). and already use jQuery

But other alternative can be considered like

• Sweet alert
• Alertify (probably deprecated)
• Curated list

Thanks

[Chris53897]

Hi,
i just migrated a project to AssetMapper. It looks good, and i hope it will improve over time.

Idea:
This bundle could run a command to install/update the js dependencies.
php bin/console importmap:require "bootstrap@^4.6.0"

In best case with lazy load as default (Without --preload).
And load the js resource as page specific content.

The main problem that i see, is that projects can have already bootstrap in there project with a different version.

One part of the solution could be the entrypoints mentioned here. But i did not take a closer look.
symfony/symfony#51543

Greetz

[Chris53897]

I will have a look at the suggested js libs, as soon as if i have some time.
UX-Autoconplete uses Tom-Select. I migrated from Select2 to Tom-Select in a company project.

[kl3sk]

Hello,

Yes I think Tom select is better (I personally use it too). Just try to match your use cases.

UX-autocomplete is for me a good alternative.

[kl3sk]

Hi, i just migrated a project to AssetMapper. It looks good, and i hope it will improve over time.

Idea: This bundle could run a command to install/update the js dependencies. php bin/console importmap:require "bootstrap@^4.6.0"

In best case with lazy load as default (Without --preload). And load the js resource as page specific content.

The main problem that i see, is that projects can have already bootstrap in there project with a different version.

One part of the solution could be the entrypoints mentioned here. But i did not take a closer look. symfony/symfony#51543

Greetz

An other solution could be to have multiple templates (as Symfony do) for either bootstrap 4 and 5 (why not more).
I personally totally override your template to remove every thing I don't need (mostly jQuery) and extend my own "base.html.twig".

Providing a "base" template is not a good way for me. In an other hand it is easier to override 😉.

Because bootstrap confirm is not compatible with Bootstrap5 I try to write my own plugin.

[Chris53897]

Ryan Weaver works hard to improve the AssetMapper Component. I love it.
But not every user-project will use AssetMapper. And make this optional with an additional version is of course more work, than less.

I am in favour to have less dependencies. But i guess i do not have time to implement this. At least not in the near future. PR's welcome

[kl3sk]

Just to try it out, I'm trying to implement AssetMapper in this bundle. Unfortunately, I haven't mastered AssetMapper yet.

If you have any clue on how to do it I'm glad to ear you.

[Chris53897]

I have integrated it in 2 real projects. But i do not how to use AssetMapper depedencies in Bundles.
Before you start working on this, maybe @weaverryan can help if this is possible in general.

[weaverryan]

We don't have a clear path yet for bundles to rely on AssetMapper, which is a bummer. The problem is that if a bundle requires symfony/asset-mapper, then if a user doesn't use it, it'll get installed... and the user will end up with importmap.php, etc., and will also now need to run asset-map:compile during deploy. That really sucks - it would be SO handy to use AssetMapper in bundles. But we're not there yet, at least I can't think of a reasonable path yet.

[Chris53897]

Thanks for the input Ryan and all the work for the AssetMapper-Component.

@kl3sk It is way more simpler to, just add split/copy the templates. One for standalone use (this already exists), and one for integration into an existing layout. Additional some documentation needs to be written, which command are necessary to integrate the external libs with AssetMapper

[kl3sk]

@weaverryan thanks for all your work for the Symfony community.

@Chris53897 I will dive into it when I found some time. Please be patient.

I'll thanks everyone for this great community.