| Map | Action |
|---|---|
| <F1> | Causes Netrw to issue help |
| <cr> | Netrw will enter the directory or read the file |
| <del> | Netrw will attempt to remove the file/directory |
| - | Makes Netrw go up one directory |
| a | Toggles between normal display, hiding (suppress display of files matching g:netrw_list_hide) showing (display only files which match g:netrw_list_hide) |
| c | Make browsing directory the current directory |
| C | Setting the editing window |
| d | Make a directory |
Hi Nicholas,
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I lead the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can'
| // Usage: | |
| // | |
| // 1. Put this in the file that gets first loaded by RequireJS | |
| // 2. Once the page has loaded, type window.rtree.map() in the console | |
| // This will map all dependencies in the window.rtree.tree object | |
| // 3. To generate UML call window.rtree.toUml(). The output can be used | |
| // here: http://yuml.me/diagram/scruffy/class/draw | |
| requirejs.onResourceLoad = function (context, map, depMaps) { | |
| if (!window.rtree) { | |
| window.rtree = {}; |