3 ms·
The GP's point was that the tooling for animating was top-notch in Flash, whereas it's nonexistent in Electron.
by StavrosK 10y ago
The GP's point was that the tooling for animating was top-notch in Flash, whereas it's nonexistent in Electron.
- icebraining 10y agoI understood that point. Did you understand mine? The very same tool that made Flash animations is now Electron compatible. How can it be nonexistent?
- Animats 10y agoAdobe Animate doesn't use Electron. It generates code which uses its own Javascript runtime. Here's the runtime.[1] Adobe documents the format, and you can write to it directly. [1] http://www.adobe.com/devnet-docs/edgeanimate/api/current/index.html http://www.adobe.com/devnet-docs/edgeanimate/api/current/ind...
- icebraining 10y agoI'm not saying Animate uses Electron, I'm saying it's Electron-compatible, in that you can take an animation generated by Animate and include it directly into an Electron project.
- Animats 10y agoYou can put anything that will run in a browser inside other HTML. WebGL, Animate, and older formats such as Flash, Silverlight, Shockwave, QuickTime, and Java applets are often framed like that. That doesn't mean it's compatible. There's a long history of these boxed formats.
- derefr 10y agoThe parent's point was that, if you think the Flash authoring experience was better than the Electron app authoring experience, then why not use Animate to author (most of) your Electron app code?
- Animats 10y agoIf you're using Animate, why do you need Electron?
- Vanit 10y agogoal posts fly overhead
- StavrosK 10y agoThe original post was comparing Flash's authoring experience to Electron's authoring experience. The fact that you can use the former in the latter wasn't relevant. It was about what would happen to animation if Flash were to go away versus it Electron were to go away.
- derefr 10y agoI'm confused—what, precisely, is the "Electron authoring experience", when used in this sense? If you program an Electron app using HTML5, then isn't anything that outputs HTML5 part of the "Electron authoring experience"?
- StavrosK 10y agoNo, you're conflating writing something with running it. These are different in the same way that editing a photo in Photoshop isn't part of the "MS paint experience" just because MS paint can open the file. By "authoring experience" we mean making something purely in that platform, i.e. Electron vs Flash, i.e. writing it by hand vs using Flash's rich tooling.
- derefr 10y agoOh, okay. But, in that sense, there is no "Electron authoring experience," then. It no more "has" a text-editor you can use to "write Electron by hand" than it has an authoring app you can use to "create Electron in a WYSIWYG style." Electron is not even MS Paint; Electron is Preview.app. It doesn't assist you in making anything. It's a viewer. Do you blame Preview.app for not making it easy to make PSD files? Do you expect it to help you with that? Electron is, morally, a transpiler. It's a thing you shove a completed application through, and get a completed application for a different platform out the other side. The only necessary "Electron" part of an "Electron project" are the Electron-specific configuration fields in the package.json file. And that's effectively just a release/distribution spec file, much like the debian/ dir for projects that ship .debs. Which is all to say: there is no such thing as an "Electron project." There's just "web projects" that happen to ship Electron releases. (And, yes, there are projects that never bother to test in any other configuration, so they lock themselves into their code only working on Electron. But this is no different than locking your web project into only rendering on a particular browser.)