Overall the clean/flat design works great for construct 3. But the clean/flat design seems to be missed on the tabs, instead they have a shadow/gradient with round corners and more of a 90s web feeling. The only thing that feels like it doesn't belong there.

True, those tabs were criticized by many users. I might also add that (asked by several people as well) the lines next to the events on the event sheets really helped the eye to follow which events are indented in C2. I see no reason why they were removed. It just makes it harder to read the visual code.

And for some reason Construct 2's browser object won't work in Webview, either. I'm about to try it in Webview+.

The browser object's Close action works just fine in my project built with Cocoon.io Webview.

Man whoaa you're freaking me out here, do you mean that you were responsible for the bankruptcy of Goo and now you're going to make Scirra go bankrupt ? Is this some kind of threat?

Where did you get that?

+1 for this. Hopefully it's not too hard to implement and can be useful in many cases.

Well.. If I was going to do a manual Id have liked it to be as complete as possible

to the point that you'd literally have all your answers to 90% of questions

I get your point, but this is what tutorials and the forums are for. You can't expect a manual to answer 90% of all the possible questions. The manual's purpose is to provide reference on how the engine works. For the past 4-5 years, I found the manual exceptionally useful. It only missed minimal information, but then the forums had those.

A far more easier solution would be to just accept 'early bird' paid subscriptions to unlock the event limitations at least.

That would only solve the problem for the limited beta testing, which I'm ok with. In my post I reflected to the free edition's limitation, since I think that the 50 event limitation is too limiting and not enough for complete smaller games. It's just for playing around. My students may not reach the 100 event cap in our classes, but a few of them beat the 50 limit in C2. If we were to use C3, they would hit a wall with their first game (and the engine would've left a bad impression).

You may create complete games in 50 events, but that implies that you already know how the event system and game development logic works (you may even know how to use functions). I don't feel like that this is true for beginners or students.

How did you select anything? when I save to local I can't select where to save.

I guess the browser brings up a window for saving downloads (can be set in browser settings). But saving a file into a cloud drive doesn't mean that C3 support iCloud. It would only support it if you could save there directly from the editor. I don't know the difficulties behind not currently supporting iCloud, but since MAC is on the supported platform list it would only feel right if C3 would support it.

Then that shouldn't be the issue. Also, the size of the layout don't affect performance.

We are actually planning a full web-based editor to crowdsource translations, manage changes between releases, and so on. It won't be ready for a while, but that's what we want to do for this.

That's a great idea. I'm looking forward to it later on.

I decided to start a new topic since I gathered a few opinions and suggestions for the editor UI and usability, and I didn't think it would fit completely into any topic. I tried the new r13 version and it seemed that my points are still valid (though I removed some as reading trough the release notes, since those were fixed). I'm sorry if any of the following were fixed/changed since. In that case, please ignore that entry.

First about the free event limitations: I understand why Scirra is limiting the events more, but I'd like to throw in an idea: What about letting users increase their event limit even more after 50 (maybe up to 75) based on their activity and usage of the product? I'm thinking about something like "Complete your profile": view a tutorial, introduce yourself in the forum, etc..

And now for the editor (things I think should be fixed/added in the beta):

• I missed the option to set the object's name right in the Insert new object window. It's a bit bothersome to always right-click the object and rename it in the project tree.
• When you use the keyboard's On key pressed condition and make the event an "OR" block it should allow to use the condition again (like it does in C2). Right now you need to make separate events to support multiple key presses for the same logic.
• It could be a time saver to be able to copy frames from an animation to an other.
• When I delete a frame from the middle of an animation it selects the first frame of the animation. Making it deleting following frames by hitting the Delete key multiple times uncomfortable, since you have to select each frame with the mouse.
• When I copy and paste an action, I think the pasted action should go to the bottom of the existing action list, not to the top.
• When I activated Google Drive saving the editor didn't show my account profile picture, just a dashed cloud. A restart was required to fix this. Now I just tried it on a different computer and it works just fine (displaying my profile picture), but I think it's worthwhile to mention this.
• The exported projects still have the Construct 2 splash screen.
• It would be important to allow previewing in multiple browsers. I don't know that if it's possible or not as a browser based software, but if it's not then a link to the local preview could be displayed and copied into other browsers manually (it would be better than nothing and it could work on offline devices as well).
• When editing expressions (or variable values) I can't select the value already in that field with double clicking on the field. I have to specifically double click on the value. This is bothersome if you have a long input field but just a short value in it (I'm talking about the default variable values specifically).
• Adding a new placeable object (tested it with Text and Sprite) in the project tree while viewing an event sheet leaves the mouse in the "placing mode", forcing the user to switch to a layout and place the object. I think it would be better to just add the object to the project tree and leave placing it later for the user.

As for new features (ones I think should be added in the future):

• It could be a great addition if we could have multiple collision polygons. I had a few projects where I had sprites that could really use multiple polygons. Instead of 2 simple ones, I had to use one with tons of points to get the result I wanted (not so efficient). It's not so efficient either to split sprites just for the purpose to have more polygons. This has been asked by several users as well.
• It would be also a great time saver (and also a preparation for a possible modular system later on) if users could copy and paste events or objects from one project to an other. The editor could bring up a window for the user to correct (replace or delete) all missing references. This was also asked by many developers.
• While it's great to have previews inside the editor, I think previewing animations right inside the animation editor would be great. It could save a few clicks and make the development a bit smoother (thinking about projects with lots of animations, it can be very uncomfortable to set the properties, exit the animation editor, select the animation from the sprite's properties and preview it, then back to the animation editor for adjustments for each animation).
• I read

  Elliott 's suggestions about the UI layout and I agree with them:

1) Save custom layouts to use from the settings menu.

2) Being able to dock the preview window.

The editor fully supports translation, but we are extremely busy with a range of complex aspects of the launch. We're hoping to address it in the near future.

If your answer to Momio 's question is that we can make translations ourselves, will there be a simple to edit file where one can do that?

I solved that issue by comparing loopindex:

| Global number endofloop = 10

+ System: For "" from 1 to endofloop

----+ System: LoopIndex = endofloop

-----> Text: Set text to "Do stuff here"

(Well, it seems that the copy as text function works just fine).