Andrew Smith

Right, good point...well, conceivably we could use `crossbeam` to create a scope that would allow us to spawn threads and ensure that the stack slice lives until all the threads...

I'm not sure what you mean by this. Do you mean a mac menu bar sort of menu? I'm sure that's probably possible, somehow.

Okay, sounds good. Could you point me to the graphics doc? For now, I'll package anything that doesn't ship with OSX (like Chicago) in the Resources folder.

How's this look for a list? (Mac system 7.0.1 fonts, from [https://web.archive.org/web/20020619184832/http://docs.info.apple.com/article.html?artnum=18078](https://web.archive.org/web/20020619184832/http://docs.info.apple.com/article.html?artnum=18078)) Chicago Courier/Courier Bold Geneva Helvetica/Helvetica Bold Monaco Symbol Times/Times Bold Times Italic/Times Bold Italic New York

That sounds great to me. Thanks!

@giuliomoro for an idiomatic API, we should actually eliminate global variables altogether. Mutable global variables are unsafe in Rust (and, technically, in general) since they're both mutable and shared. Basically,...

Thanks for the quick reply! That does not work. It changes the last error to "Cannot find component: 'PerformanceRow.jsx'" but otherwise it's the same. I also tried running `PerformanceRow.jsx` through...

Yep – here's my Chrome console: ``` window.componentRequireContext("./PerformanceRow.jsx").default // -> function PerformanceRow() { // _classCallCheck(this, PerformanceRow); // [... more babel-compiled code...] ```

Oh, however, I do have to add the extension to get `window.componentRequireContext` to work. The original error message from the helper is `Cannot find module './PerformanceRow'.`, and when I try...

I think requiring `react_component "MyComponent.jsx"` instead of just `react_component "MyComponent"` could run into confusion (thinking about people copy-pasting from tutorials, stackoverflow, etc), and probably will breed lots of little spammy...