thekenwheeler

it depends. canvas is typically much more cpu friendly. and does a way better job with text. (2d)

I remember way back when, when I first started on the web, I got paid to make Flash sites. It was a cringey time, but the capability and animation smoothness, on Windows XP, 8 years ago, was still better than you can get on the web on a Macbook Pro today.

When Jobs murdered flash I transitioned to web waiting for it to come up to parity, but it never did.

We've had incremental improvements, but IMO they have been scraps, and the priority is out of wack. Why are we adding MIDI to a platform that still can't efficiently do layout?

I recently gave a talk about building a new browser without the DOM, instead using native UI primitives driven by javascript for our sites: https://www.youtube.com/watch?v=WEQx3wz8QeY

Wherever we land, I just hope to someday get the kind of performance on the web that I got 8 years ago with Flash.

There are actually a ton of binding already defined here: https://github.com/BuckleTypes

Further, anything already typed with Flow or Typescript can be converted with this. https://github.com/rrdelaney/ReasonablyTyped

Beyond that, defining js types and interop with Reason/BS has probably been the most pleasant experience in a compile-to lang that I've used.

http://reactnext.surge.sh

This lib uses term-img internally to print generated png imagery.

out of pure curiosity , what would you prefer it be written in?

holy mackerel, this lib is dope.

i haven't but that sounds dope. you should give it a shot!

Its a work in progress. Right now the synths are single oscillators with no filter. When I get those composing with effects, it'll sound more like a real patch. Also, sample maps for the sampler with note input will make doing things like wav based piano lines a lot easier.

lol

Yeah, its severely limited compared to a DAW in almost every way. But its super fun to mess around with, and if you like React and the Web Audio API then its a cool example integration as well. My vision long term is that this will serve as a set of primitives that can be composed into instrument presets and have UI hooks so you can build something like a step sequencer UI or a drum machine.

I'm working on overriding stdout to go to the Log panel

You'll want to set the webpack config option { quiet: true }

Yes, I do. If it was OSS I would PR the feature personally.

Hmm I'll take a look. Is there any particular animation choking? Or all of them? It runs like butter on my Macbook Air in Chrome.

Thanks! I write React full time at a very large company, so we've had some time to develop some cool best practices and solve some of the challenges something like this presents.

Or actually, maybe a different idea. Thoughts on using a modifier key like shift or something to navigate without animations?

Good point. I'll split the transition prop into transistionIn and transitionOut so that you could set one direction to have no transitions. Realistically I don't even use transitions in my presentations, but folks seem to like them sooo....

That is a very strange and very valid bug. Head scratcher, but I'll get it worked out.

Done & Pushed. Great call guys.

Good call

Is there an particular set of aspect ratios this is failing at that I can test against? This is 0.0.1 so theres still a couple of loose ends.

Thats awesome. I've done a lot with swipey things in the past. The cut off should be fixed in the next patch, with height conditional scaling.

The component in question is using component local state, so that resets on mount/unmount. That said, it would be very easy to embed one that instead used flux, and state would be preserved.

Not yet, as I'm still working out some of the feature set, but I'll file an issue for addition.

Oh no! Could I trouble you for what env this occurs in? Does a refresh fix it?

I believe its due to the mount cycle of TransitionGroup. Especially if you navigate before a transition is over, then an unmount doesn't occur, and the state isn't cleared.

Hah. In my own projects I've been cameling it like var mcFly = new McFly()

I did, and it's really cool, but I felt the same way. So I wanted to bridge the gap.

The Dispatcher is helpful because, using the waitFor method, you can marshall the callbacks to enforce an explicit update order in the event that there are dependencies.