search

cksource-archive / samples-framework

☠☠☠ This repository is no longer used ☠☠☠
Other
0 stars 0 forks source link

nagivation-a #2

Open adelura opened 9 years ago

adelura commented 9 years ago

I wonder whether it's worth to dispense navigation-a from header. Is this really such generic part, I think it's highly connected with header.

Going further - Why tree-a doesn't have navigation within it's name?

oleq commented 9 years ago

I wonder whether it's worth to dispense navigation-a from header. Is this really such generic part, I think it's highly connected with header.

But once you decide to use a header different than header-a, you are unable to use navigation-a. You need to hard-copy it. There may be multiple headers in the future and we cannot assume that this is the only case. The more component-based the better is the framework.

Going further - Why tree-a doesn't have navigation within it's name?

That's some point. We may need to discuss the naming convention for all the components.

adelura commented 9 years ago

I think that in generic directory we shoulnd use stuff like *-a. Here should be as raw and generic as possible code which just work. I suggest to introduce something like theme or components directory and there pass elements like navigation-a. For me it smells like an extra component for header which is not very generic.