Here are some of the things I found while playing with it:
- The generated code is surprisingly clean. The output consists of
- an HTML file (with a few imports and a single div tag)
- a CSS file (easy to read, with IDs that match the object names defined in the tool)
- JQuery dependencies
- No real drawing tools - The current version only offers 3 shapes: rectangle, rounded rectangle and text. I assume there are more on the way. In addition to a few CSS tricks, they could have provided some basic shapes by generating SVG (or maybe HTML 5 canvas). You can still do just about anything you need to by drawing your shapes in Illustrator and exporting them as SVG or rasterized images. There is no explicit Illustrator support other than 'import image', but it auto detects changes in files.
- No sound or video - while html 5 does support video now, I was more concerned with sound. Sound effects and animation go together like chocolate and peanut butter. I can't help but feeling my creations seem like little silent movies in their current state.
- No components - Of course, components are more in the domain of Flex than Flash, and it would be a little early to expect components in an Edge environment
- The Stage metaphor - Edge uses a 'Stage' metaphore rather than a 'page' metaphore like you would find in Dreamweaver (or any content-driven web page). Seems like a silly thing to point out, but this tool is for making an animation in a box. It is not for making a web site. After you finish, you can take the resulting animation and plug it into your web page by pasting in all the dependencies and the div tag.
- Doesn't crop to the stage - Because Edge is so similar to Flash, I was a little surprised when I ran my animation for the first time and saw artifacts running out of the stage. Of course it makes sense, a jpg or svg doesn't stop rendering just because it ran out of the stage.. it's not in a plugin like shapes in Flash are. I initially didn't think this was a big problem, but I haven't found many good work arounds. When you add your animation to an existing web page, there are a lot of cases where the artifacts are going to run out onto the rest of your page. I've seen others solve this by loading the animation in an iframe, but that seems kind of dirty to me (although I had to resort to this trick in the example above)
- Browser compatibility - It seems to work fairly well on modern browsers. I was running into issues on IE8 and Firefox 3.6, but that turned out to be lack of SVG support (I was animating SVG drawings created in Illustrator). Other than that, I haven't seen any problems.
- Mac support - It runs on a Mac, which is more than I can say for JavaFX 2. I'm only mentioning this, because I wouldn't have even picked up Edge if I could have been working in JavaFX, but since I don't have a Windows machine at home, I found myself looking at other things.