okay this tells me there was/is an effort to do so but what is the latest development on it? I use a trunk installation here and as i pointed out in my initial email there is some collision still so i asume there wasnt a full rewrite possible ?
cheers Markus Am Mi., 25. Jan. 2023 um 12:36 Uhr schrieb Jun Omae <[email protected]>: > On Wed, Jan 25, 2023 at 6:08 PM Markus Rosjat <[email protected]> > wrote: > > > > Hi all. > > > > since i play around with some UI stuff in my plugin i noticed if I want > to sneak in a framework like bootstrap it works in basic but it messes some > of the basic layout in trac. This is caused by naming conflict in trac.css > and the bootstrap css. So my question is, will there be a kind of naming > convention for css classes in trac? I notices some naming ist already > prefixed with a "trac" prefix so if this is keept up for the whole css > classes i would be much easier to bring in other frameworks for styling. > > > > ... > > > > i know i could make a tailored version of bootstrap and ship it with the > plugin but i guess a cleaner solution would be to introduce a consistent > naming for css. > > See https://trac.edgewall.org/ticket/5997 > > > -- > Jun Omae <[email protected]> (大前 潤) > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/trac-users/CAEVLMaiEQkfvO_XPUVUYd4o4KeqHp%3DAwugZmb9K%3Dfb5QNGdD-w%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/CAJ4osOnvrU3CJjJh9-QSsFMg6ZUP8JPn9xULwoPc7njkNxZjrA%40mail.gmail.com.
