We need to ensure that components can easily be constructed. The current construction chain, requires that the constructor take care of some wiring, and for that it needs arguments passed to it.

I think we should avoid this as much as possible.

One of the things that is interesting running inside a web browser, but not rendering a DOM, is that we can actually use iFrames to MultiPlex running apps into a one process sandbox.

There could be many great uses for this. Such ass running multiple modules for your program inside tiny sandboxes, without increasing the need for bridge instances to run them, in a single unified app.

Each mini instance could still own a RootView, or it's possible to allow them to share view. But sharing a view would mean that there should be Navigator support, so that they don't compete for rendering space - Unless thats desired (Banner Module for example, could render to the same UI view, but execute in it's own context).

I think PostRobot would be good for this.

Implement a Stack View Control

Web Animator is not maintaining X,Y positioning when moving between animations.

Web cascades styles from parent to child. There should be some styles that a child gets from it's parent for styling.

Looking at RN, it's nice to see constantsToExport as a method call on a registered class. If the signature is available, it runs, and returns a dictionary of keys and values, that should be exported to JavaScript space.

Also Need Platform exposed to JS.

https://github.com/facebook/react-native/blob/master/React/Base/RCTPlatform.m

Need to do a scroll view component, stubbed.

should be able to push props and set them from the native layer like react native.

Would be nice to have a minimal box model implimentation with padding and margins to go with relative layout.

Need to add resume handling to the bridge. UI comes back, but things like animation are not hydrated.

Outer component is rendering a DIV as base tag. This should be changed. I think I picked this incase someone didn't add a Tag, but now I'm seeing this as a downside :) to our Functional Classes thing. lets remove this.

Need to be able to set initial props from the javascript layer.

The project has morphed a lot since the CI was setup, and we have been moving faster than we are able to keep up :) lets go back and fix CI

This happens when hot reloading a view, and it tries to notify the animator between a reload.

Doesn't like casing for interpolation, likely other places where string compare is being done case sensitive.

whhYYYYYYY

should have a syr link cli command to ✨ automagically ✨ link native modules / assets

We have hot reloading, but it currently thrashes the render/state and starts over. Would be nice to preserve this to speed up developer for deep screens.

Invoking a Native Method, and getting a Return back should be able to happen, and async.

Would be nice to have

https://facebook.github.io/react-native/docs/layout-props.html#zindex

Finish setting up Android testing for Travis.

Would like to pull out any constructor crap being done, into a setAttributes for bootstrapping props etc. This way the constructor remains pure and Super doesn't require args

JSX to Native Module paring happens with some magic. Now that native module registration is in place, lets clean up the magic found in the raster when loading classes for rendering.

For some reason stack items are not showing up unless done in pairs, and then every 2nd item "bleeds" on top of the first

Every rootView should spin up a new Bridge Instance to the Module that is being loaded.

Ensure this works correctly :)

Would be nice to have Syr take care of relative positioning on Native Platforms, much like the DOM has a natural flow. This would mimic ReactNative more closely.

Will help to have more documentation on command-lines to be used on syr-cli

Could not file an issue directly there, so filing it here in the interim. Can PR them in as I figure out how to use that tool.

• Pod Spec
• Pod Tests On Travis

Wondering if Syr should soft fail, if it knows it has too many overloads for the selector it's running.

Currently it will hard fail - but this maybe this is expected behavior.