Hi
I think working on making the framework "core" more css agnostic seems like
a good direction, allowing things to move forward without having to try and
pick (and maintain) the correct bootstrap version (or other css framework
version/flavor). There is a pretty good chance that whatever is selec
Another 👍👍 up.
Btw, could you share the link to the github repo here? Thanks.
On Fri, Feb 15, 2019 at 7:03 PM Jens Breitenstein
wrote:
> Thanks for you positive feedback. I suggest the following now:
>
> 1) I will use git hub to create a new T5 Fork based on Thiagos
> 5.5.0-beta-1 and remove al
Thiago,
Template overriding would only work for those Tapestry-supplied components
that use templates, right? But most currently don't, which could be changed
and is part of what I was suggesting here:
https://markmail.org/message/m5g3icg3jsxi7nc5
On Mon, Feb 18, 2019, 2:04 PM Thiago H. de Paula
I know it's not the most future-proven way of doing this, but couldn't a
simple solution would be to have a separate JAR which subclasses the
components using Bootstrap, do nothing but change the template and then
contribute the components to ComponentOverride?
On Fri, Feb 15, 2019 at 10:03 AM Jen
Thanks for you positive feedback. I suggest the following now:
1) I will use git hub to create a new T5 Fork based on Thiagos
5.5.0-beta-1 and remove all bootstrap dependencies. As soon this
compiles we will have a T5.5 version looking like websites in the good
old early 80ies.
2) I will try
