Components need a standardized taxonomy

[loranallensmith]

Right now, component names in this library are mostly based off of the component names in PhotonKit.

Photon's styles are beautiful, but they do make for a very Mac-centric user experience. Keeping with the cross-platform spirit of Electron, it would be great to give folks a more native-looking cross-platform experience with Brightwheel's components.

This is something app developers could address by dynamically selecting a stylesheet at build time, but it would be nice to rely on more of a shared language than trying to retrofit component names from non-Mac platforms onto Photon's taxonomy.

I propose these next steps:

• Decide on an initial list of widely-used UI frameworks for Windows and Linux machines.
• Put together a table matching up comparable component types from all of these frameworks (including Photon/Brightwheel)
• For each component type, let's decide on the best name
• For components that have no analog in one or more of the frameworks, decide whether to support the component in Brightwheel or let folks create those themselves by extending existing components.

---

Frameworks/Platforms

• Cocoa/OSX
• Universal Windows Platform
• GTK (or maybe Qt?)