Component list discussion

[bmcmahen]

We can keep track of what components we feel should make the cut, here.

Elements

• [x] Base
• [x] Text
• [x] Button
• [x] Icon
• [x] Divider
• [x] Input
• [x] Image - Fade on load, circular, width & height, cover as default resizeMode
• [x] Loading
• [x] CheckMark - a with toggle on / off state.

  Views

• [x] InputGroup
• [x] TouchableRow
• [x] InputRow
• [x] InputExpandable
• [x] InputToggle
• [x] InputDatePicker
• [x] SectionHeader
• [x] TouchableInput (Rethink the difference between TouchableRow & TouchableInput)
• [x] ErrorPage
• [x] NavBar
• [x] NavTitle
• [x] NavTouchableText
• [x] NavTouchableIcon
• [x] SubNav
• [x] Card, CardHeader - a simple card, much like that provided by material design.
• [ ] Grid - Wrapper around listview to make grids easier
• [x] ButtonGroup - Deprecate VerticalButtonGroup. Allow groups of 2, or 3, with centered attributes.

  Modules

• [ ] TabView - like that provided by material design.
• [x] Popup - Generic Popup (Modal?)
• [x] PopupMenu - Pop up menu component -- similar to ActionSheet, but cross-platform.
• [ ] ProgressBar - indicates progress, alternative to loading indicator
• [ ] ImageSwiper - component that takes an array of image sources and creates a horizontal, paged swiper/carousel
• [ ] ProgressiveImage - component that renders a default image (low res, could be blurred) and smoothly transitions to the high res image once it's loaded.

[META-DREAMER]

I've built a nice tab bar component for my app, I'll integrate it into panza :)

[META-DREAMER]

One potential thing to think about is the design of these components. Right now, almost all of the components are more or less aligned with iOS design guidelines, but I can imagine android users wanting more material design oriented components.

[bmcmahen]

I think you're right. Ultimately I'd like to find a balance between providing a universal look, that works well on both android, ios and web platforms, and tailoring the ui for each platform where it makes sense such that the user doesn't need to worry about it. This is already currently done with the NavBar, where Material styles are emulated on android.

[META-DREAMER]

Awesome work so far, will check out all this next week! I notice a lot of breaking changes, I think we should follow a versioning guideline (semver.org) and keep track of all changes in a CHANGELOG.md file. Any changes we make we add to the top of the changelog under "version next" and every week or so we assign a new version number. Here's an example: https://github.com/apollostack/apollo-client/blob/master/CHANGELOG.md

As soon as we get some stable footing with all the docs and finalizing the structure and cleaning up a bit, I'll start promoting this and try to get the word out, make some posts on medium etc.

[bmcmahen]

I'm leaning towards adding an existing Swipeable Tab view that is stylized in the panza way, mostly because I tend to use this in every single app that I make, and it's annoying to have to install / style it each time.