Vote: Layout vs Include

[agrosner]

When creating a layout we intend to import elsewhere (typically via an <include />) , this is to decide whether to choose: @markpragma @Lackofa7742 @dylanrjames @Mervyn-Raizlabs

1. layout_{name}
2. include_{name}

so for a FloatingActionButton:

1. layout_fab -> <include layout="@layout/layout_fab"/>
2. include_fab -> <include layout="@layout/include_fab"/>

Context: https://github.com/Raizlabs/Raizlabs-Android-Style/pull/3#discussion_r28014267

[agrosner]

2

[orionthewake]

2

[dylanrjames]

I don't really like either, but prefer 1

[agrosner]

@dylanrjames I feel layout is just too generic. include signifies that its meant to be included somewhere else.

[Mervyn-Raizlabs]

I prefer 1, a layout sounds generic but thats what its meant to be. We can choose to include them or use as is. Maybe prefix with sublayout or module?

[Lackofa7742]

We don't do layout right now. Currently for a layout that gets imported, we call it view

[Mervyn-Raizlabs]

even i like view better than layout/include

[agrosner]

@Mervyn-Raizlabs @markpragma @Lackofa7742 @dylanrjames Its a tie at layout and include. @Lackofa7742 you've go the deciding vote.

[dylanrjames]

@Lackofa7742 No, view corresponds to custom views. We've always used layout. Currently in projects we're using no prefix at all or hodgepodges.

We can't use view because it conflicts. See the context link.

[Lackofa7742]

Got it. in that case, I like 1

[dylanrjames]

Seems like we have 3 that don't like either. I could get behind sublayout like Mervyn mentioned if anyone else has strong feelings for it. Anyone feel strongly or have other suggestions?

If this stays as is by the end of the day I'll change it to layout since it's the current winner.

[agrosner]

layout it is.