Re: oocss / b.e.m question

[fuqlibs]

# Current Hierarchy

Each class below list requires the list object to appear in the class attribute. The reason is, List contains all the main code, like the clearfix, changing the list type, setting the padding, etc. It was setup to be DRY.

list
list–inline
list–block
menu
tabs
tabs–top
tabs–bottom
toolbar

# Bootstrap Hierarchy

Bootstrap has everything contained in one object. For example, –tabs would be a modifier.

# The problem

I know you suggested I follow the bootstrap way of doing this, but really each could be separate objects that inherit the style from list (sort of like Nicole Sullivans idea of a “skin”) The second problem is that classes like tab have their own modifiers like top and bottom.

Is my thinking correct on this? I just dont know if requiring extra classes follows the oocss and bem methodologies. But I can honestly see some of these classes getting more modifiers in the long wrong.