At 1/31/13 09:58 PM, Gazuria wrote:
Anyway I'm really glad that your interested :D
yeah, it looks interesting. Here's some stuff I picked out of your last video:
1. 800x600 is a pretty standard resolution for Flash games these days, though you should have an option to set and save defaults.
2. That right-click menu in your states is getting pretty long. If you want to add more to it, I would recommend moving all of that into a submenu labeled "add" and removing the word "add" from all of the labels in that submenu.
3. custom FPS for every state could either be a really good idea or a really bad one. Keep an eye on that.
4. Most of the items under the preview should really be more a matter of code. Music can change and sounds can be dynamically added, "resource" looks like it could be "resources", in which case you're going to need more than a single drop-down, and i'm not entirely sure an offset for the entire state serves a real purpose. "Frame scripts" looks interesting, but if it does what I think it does, then why is it a checkbox? "Skip mode" could also change during the state, so i'm not sure it's a good idea to have one solid box for that, either.
5. A default initial state would have saves you a few headaches, but that's most likely in the past now.
6. Again, in the right-click menu of the game state, all of those "add..." options could be moved into a submenu.
7. Making starling a universal option instead of a scene-by-scene things may save a few headaches as well. Plus, I don't see many games that go "we'll use this framework here, but not here, and here again, and then this framework here..." - it's normally one solid framework throughout the entire game, because otherwise it's just a confusing, slow mess.
8. Utilize the keyboard more. Add shortcuts, because everyone loves shortcuts. Make everything readily-accessible to people with varying likes. Some people like to right-click, some people like the keyboard, and some people like clever use of mouse such as gestures and double-clicking, etc. Make sure there are many ways to get to where they're going.
9. The zoom is great, but once again more accessibility would be nice. A magnifying glass tool, mouse wheel, keyboard shortcut, double-left-click to zoom in and double-right-click to zoom out or something, etc etc.
10. Add buttons right to the components panel that allow you to import assets, or allow people to drag-'n-drop assets into the library from the OS directly (if possible) - readily-accessible everything is key to programs like this. Features count for nothing if nobody can get to them.
11. add snapping like the Flash IDE. Not just grid snapping for objects, but stuff like shift+click resize corners to keep the aspect ratio, etc etc. Also, registration snapping would be useful. And a button to turn it all on and off. Take a few leafs from the Flash IDE book; they have some great ideas packed into that IDE.
12. Display properties should auto-open when an object is selected. Most of the time, that's what you'll be dealing with, so why bother having everyone open it every time they select a new object?
13. The display property values should auto-highlight when focused upon so you can edit values more readily (highlighting text every time you want to edit it is a pain)
14. Turn Project->run into a submenu, and allow the options "debug" and "release" so you can check out how it all runs from all angles. Also, shortcut keys. F5 could stand for "run/reset debug" and Shift+F5 could stand for "run/reset release" or something.
15. DisplayObjects telling DisplayObjects how to run is poor design. A game engine should not be stored in a DisplayObject, because it has no use being a DisplayObject. I unserstand it's a button, but you should allow for an arbitrary class (an engine) to tell everything what to do. Right now, it's looking like Java: "if it isn't an object, it doesn't exist."
16. Your "add even listener" box doesn't give detailed information on which parameters do what. If you can import ASDocs, parameter names, or anything into the box somehow (a hover tooltip, maybe?) then it would be great. Generally, two programmers don't work on the same thing, so "number" and "boolean" are really useless when calling a function. We need to know what it represents, what it does.
17. Having to "edit listener" in order to remove it is a bit of a pain. Just move the "remove" to the right-click menu.
18. "Parameter 0" and "Parameter 1" is so much less helpful than "number" and "boolean" - at least those tell you what it's expecting.
19. Your up/down number arrows have no symbols. Just thought i'd point that out.
20. Defaulting values would have saved you headache for sure.
21. Having shapes other than circles for touch events would help greatly, if you haven't implemented it already. In the example you gave, triangle shapes would have done great service to your wheel of life.
and that's my list.