feature request: `cameraMatrices` prop in `<Worldview />` component

Awesome library, thanks for all you do! 😺

I’d like to supply my own camera matrices to <Worldview /> instead of the cameraState object.

the idea

<Worldview 
  cameraMatrices={{ 
    view, 
    projection
  }}
>

data model

// @flow

type CameraMatrices = {|
  view: Mat4,
  projection: Mat4,
|}

new behavior

<Worldview /> component checks for valid cameraMatrices prop on mount and update, sets them in cameraStore which uses them directly with priority over cameraState

benefits

adds support for arbitrary camera parameters in a standard format, expanding use cases

drawbacks

introduces more complexity to the camera state api

what do you think about this design? i’m eager to contribute if you think it fits.

[jtbandes]

with the right docs and warnings, having a separate prop might be easier to understand

yeah, agreed if we have both docs and warnings, this should be fine.

1. Make a story on the cameraState module that allows passing matrices directly

we’ll have to see about this organization, since if the matrices are a separate prop from cameraState it doesn’t make as much sense to group them with the cameraState stories…but they are camera-related, so maybe it’s fine. You might find some opportunities to clean up the organization while you’re there.

Looking forward to your branch!

[janpaul123]

Cool, feel free to make a PR if you think it’s stable enough now. 😄