Having them separated allows the flexibility to use a different style sheet if desired without needing to assign properties for everything that the stylesheet being replaced has declared for a particular class or id.
All back end components utilize both because most were developed by copying another component, not because of a decision that they _should look the same. I think Open Source Strategies CRM component testifies to that (although they may be simply using the cascading effect of css as opposed to a stylesheet replacement). Personally, I would prefer additional separation of maincss.css into the groups that are divided by comments, but it's a rather trivial distinction. --- Adrian Crum <[EMAIL PROTECTED]> wrote: > Maintaining a single css file instead of two. All > components reference both > files, so there's no sense to keep them separate. > > > Chris Howe wrote: > > > What benefit do you see in doing this? > > > > > > --- Adrian Crum <[EMAIL PROTECTED]> wrote: > > > > > >>Jacopo, > >> > >>While we're on the subject, could we also discuss > >>the possibility of combining > >>the maincss.css and tabstyles.css files into one > >>file? > >> > >> > >>Jacopo Cappellato wrote: > >> > >>>Following the great advices in > >>>https://issues.apache.org/jira/browse/OFBIZ-241 > >> > >>I've started to play > >> > >>>with the styles in maincss.css file and apply the > >> > >>mods to the > >> > >>>manufacturing application. > >>> > >>>I've noticed some minor side effects (for example > >> > >>the texts in the main > >> > >>>webtools page are smaller now) and I wanted to be > >> > >>sure that the work I'm > >> > >>>doing is correct and, most of all, if it is a > good > >> > >>moment to do this > >> > >>>work now (i.e. before a release). > >>>So please, have a look at the revisions 492187, > >> > >>492201, 492242 > >> > >>>(especially at the changes I did to the > >> > >>maincss.css file) and let me > >> > >>>know what you think. > >>> > >>>Jacopo > >>> > >> > > > > >
