Can I draw stuff directly in this, or is this just an After Effects to your as-yet-unreleased Canvas's Illustrator?
And by "draw" I don't mean "hassle with the pen tool and basic shape tools that I see down the edge of the toolbar in your screenshot", I mean "quickly draw lines with some kind of pencil/brush, and do some kind of simulation of frame-by-frame animation".
The screenshots just look like After Effects, and, well, that's just one visit to the Creative Cloud app away for me.
But there would be lot's and lot's of work to be done, to really compete with it(I cannot find any drawing tools as of now). But it looks good so far, I think.
The open source world needs more tools like this, so keep it up! I'll certainly be watching this.
EDIT I just saw this:
> Supported browsers: Google Chrome, Microsoft Edge
That's not good. I tried the preview in Firefox and it seemed to work fine. You do you, but if you're only targeting Chrome then count me as one potential user/customer lost.
> Cross-platform, online and offline
> Work directly online in the browser or install the PWA (progressive web application) and enjoy a fully offline experience.
Chrome and Edge support PWAs, while Firefox does not.
Of course, I could be interpreting this wrong, as saving and loading does not work in Firefox.
I'm curious how you plan to handle rendering the animations to a video. I think that will be a really challenging part to do in-browser, but maybe there are some libraries for this that I'm unaware of.
I can't even find something on YouTube?
Do I have to install and see? If so, that seems like a wee bit of a high bar.
Even after using the app, I can't figure out how to save/export to any format other than their own (eaf). Maybe that's why they don't mention it on the landing page. I have high hopes, but it needs more work before it'll be useful to the masses.
It runs in the browser. There's a big huge "try now" button at the top of the page.
Still, being dropped into that example doesn't really put me anywhere useful. A quick video or some quick step-through from the homepage would be good.
How did I miss that button?!
1. MediaRecorder (requires browser support) https://developer.mozilla.org/en-US/docs/Web/API/MediaStream...
2. ffmpeg.wasm https://github.com/ffmpegwasm/ffmpeg.wasm/
edit: upon closer inspection it seems to be a wrapper, not a port.
Also, take a look at the opened issues, and you will see what kind of formats we are planning to support.
One more thing: we will support video exports somewhere in September. Why September? Because that's when WebCodecs will be available in Chromium-based browsers. I hope this helps.
While ideally there are graceful degradations for challenging browser feature situations, prioritizing getting this out into the world is fine, and the hacker news audience is definitely not representative.
You are getting the blame for the general situation of uneven advanced browser feature implementations, when that should be constructively turned elsewhere.
By the way, what are the benefits that made you choose a web app instead of a proper native application?
Is one of its main appeals the browser-based editing?
You forget the best viewed at 800x600 badge!
Seriously though, why is this even necessary? What are you doing that can't be done in FF or Safari?
It actually works in FF, so maybe testing to make sure it works? If their Github account is accurate, this is done by a 3 person team, so resources for that sort of thing are probably not abundant.
Do you really think this is a helpful suggestion?
You are simply suggesting more work for the dev. That is not really helpful.
The browsers still do not provide a consistent behavior.
When your goal is to ship main features as soon as possible, you cannot give priority to a niche browser.
Some people can take questions for what they are, an actual quest for understanding. Others take questions as a challenge and accusation.
The way you asked it sounded like a complaint more than a legitimate question.
> It took several layers to get an actual answer to the actual question of what is chromium based browsers doing that other browsers are not.
You're assuming that this is due to the difference between Chromium and other browsers, but this could be just due to testing. Browser compatibility takes time to get right. It has an opportunity cost.
> Some people can take questions for what they are, an actual quest for understanding. Others take questions as a challenge and accusation.
Your question was voiced as a challenge and accusation. If you want your questions to be read as a quest for understanding, try to show more empathy, show some humility and show that you already thought of possible answers. Something like this: "I was surprised to see that this is only compatible with Chromium. I can't think of any APIs specific to Chromium that are necessary for this, but maybe I missed something. Is compatibility with other browsers on the roadmap?".
When your question is accompanied by the suggestion that you know better than the developers how they should be spending their time, it doesn't come off as a quest for understanding.
Especially as I was looking for something like this for quite some time within the free software space.
- Does it export to HTML? GIF? MP4?
- Can it animate SVGs?
- Does it support Sprites?
I think if someone was wanting to move away from After Effects, they'd want to know these things.