Table of Contents
README for OmNext-Demo application
This is an Om.Next application inspired by Ken Rimple's React presentation for the LibertyJS group.
A number of changes have been introduced.
-
Instead of fetching the video information from the Vimeo catalog for the
chariotsolutionsuser, the data is hard-coded inomnext-demo.video-catalog. It should be possible to update thevimeo-remoteoperation to fetch the data directly. -
Ken Rimple's original architecture created separate React components for container and component elements. This was derived from a source I don't remember at the moment, and was motivated by a desire to separate the management of state (by the container) and the display of state (by the visual component). Since in an Om Next app the state is managed through
transact!calls, this separation did not seem helpful, and the containers and components have been consolidated. (This sometimes left a lot ofdivelements: sorry.) -
The
MediaItemelements have gone through several evolutions:- first, they changed visual state when selected;
- next, they displayed related videos (in order to test deeply-nested queries);
- now, they fill rows horizontally, showing a thumbnail of the video.
-
The default build uses Bruce Hauman's
devcards, which gave me a framework for quickly checking out how components work (or didn't, as they often did when things got complex. See his Literate interactive coding: Devcards video.By the way, I probably used Devcards in a naive way: I should have had a separate module for each component I used. Maybe later.
And it looks (from the video) that I should have used Ŝablono in my devcards. Sigh. Later.
-
The same video also demonstrates the value of Hauman's Figwheel, which is awesome beyond measure.
I believe that most other changes come from adapting the code to Om Next, or a irresistible desire to tinker with what I had running.