Eytan Manor

This is a React Native app which uses Meteor as its back-end. It should be used as a sample boilerplate for starting a new app of your own.

While I was building Tortilla Academy’s diff page, I was also looking to have a tree view that could represent a hierarchy of files, just like Windows’ classic navigation tree.

Since it was all about showing a git-diff, I also wanted to have small annotations next to each file which will tell whether it was added, removed, or deleted. There definitely exists something like that in the ecosystem, like Storybook’s Treebeard. However, I decided to implement something that will work just the way I want, right out of the box, because who knows, maybe someone else will need it one day.

Since machine generated assets aren't very easy to maintain due to their complexity, Appfairy takes on an old-school approach where a single component is made out of a view and a controller. The view is automatically generated by Appfairy and shouldn't be changed, we treat it as a black box. The controller, however, is user-defined. Every element within the controller is a proxy to an element within the view. Controllers can then be used. This way the view can be changed without us worrying about rebinding the event listeners and props.

An in-depth explanation regarding Appfairy
Medium Blog Post
• https://medium.com/@eytanmanor/how-to-create-a-react-app-out-of-a-webflow-project-309b696a0533

An introduction to Appfairy and the motives behind it (I walk through Appfairy and an implementation of an example app.)
YouTube Video
• https://www.youtube.com/watch?v=6hJe6pZld0o

An example app that uses Appfairy
• https://github.com/DAB0mB/Appfairy/tree/master/examples/prefetch

A summary of React Browser Event Emitter's event handling:
• Top-level delegation is used to trap most native browser events. This may only occur in the main thread and is the responsibility of ReactDOMEventListener, which is injected and can, therefore, support pluggable event sources. This is the only work that occurs in the main thread.
• We normalize and de-duplicate events to account for browser quirks. This may be done in the worker thread.
• Forward these native events (with the associated top-level type used to trap it) to EventPluginHub, which in turn will ask plugins if they want to extract any synthetic events.
• The EventPluginHub will then process each event by annotating them with dispatches, a sequence of listeners and IDs that care about that event.
• The EventPluginHub then dispatches the events.