I completely agree. We would like to move to bootstrap 4 and improve our
integration with Kendo UI in the process.
We also need to upgrade bootstrap 3 to the latest version since there
have been issues that cause it to show up as a XSS risk on application
vulnerability scans. Just yesterday
I think it’s a fabulous idea. Two thumbs up.
> On 14 Feb 2019, at 9:07 pm, Bob Harner wrote:
>
> I agree that Tapestry shouldn't be so tightly coupled to a specific CSS
> framework.
>
> For context and some alternative ideas, see this prior discussion of the
> same topic:
>
>
Hi Jens,
I am interested by your project.
Maybe we can discuss further but right now I am super busy. What’s your
strategy to injection css classes inside components ?
Best
Sent from my iPhone!
Numa Schmeder
> Le 14 févr. 2019 à 10:04, Jens Breitenstein a écrit :
>
> Hi Tapestry guys!
>
I agree that Tapestry shouldn't be so tightly coupled to a specific CSS
framework.
For context and some alternative ideas, see this prior discussion of the
same topic:
https://tapestry.markmail.org/search/?q=What+happens+when+Boootstrap+4+is+released%3F
On Thu, Feb 14, 2019, 4:52 AM Ben Weidig
Hi Jens,
I like the idea of decoupling the core and Bootstrap to make it easier to
use other versions.
Maybe the components should be updated to BS4 for T5.5, with a legacy
fallback or a component swap (can't remember the service doing it, we have
our own implementation, it's doing an advice on
Hi Tapestry guys!
I want to hear/read your opinion about getting rid of the Bootstrap
Library from T5 core.
I would like to move all BS related code (css/js) to a seperate module
like "tapestry-bootstrap3" and decouple the hardcoded BS from T5.
Furthermore I would like to see a second module
