Small Interface Suggestion

[Joseph DiPerla]

I like the new suggested way. It would be more... Comfortable.

But whatever you choose to do CJ is fine by me.

[LeChuck]

I much prefer the new way. It makes it easier and faster to navigate.

[Scummbuddy]

I would be for the change. I've often felt for this change, but didn't feel worth mentioning. If there was a way to switch between two interfaces, such as one with tree branching, or not, I think everyone would be happy.

But again, this is such a low profile suggestion, we'll see. Maybe this could be added to the suggestion tracker, so that more people can add their thoughts.

[Shane 'ProgZmax' Stevens]

Any change that enhances object oriented design is definitely a step in the right direction- whether it 'seems' strange at first or not.  Streamlining ags and making lists bulleted (I made a somewhat similar suggestion about bulleting views so you could store all a characters views in separate bulleted lists (much like how the sprite manager handles folders and subfolders) = extremely OO and convenient) will improve productivity in the long run.  In fact, one way to greatly improve overall utility would be to use a system similar to the folder/subfolder system the sprite manager uses.  The consistency gain between different parts of the editor would ultimately benefit everyone.  Example:

the View editor would handle things like:

-EGO
-[foldername1]
  -(all views in this folder...Let's say this folder handles 'special' animations like jump, run,etc).

-[foldername2]
  -(all views in this folder...Let's say this folder handles walk animations).

etc

-EGO1 (repeat process above).

Now all views have been oriented around an 'object'.  The object in this case is EGO, but it could be 'tree', 'Bill', 'Dog', or 'Gigantic computer'.  This could be extended to dialogs as well, although the current method uses bulleting of a sort already (with the option names list).  If any of this is confusing I apologize, I've just read too many programming books on OO design and find the long term benefits to be worth extra effort (for my part anyway, I'm not assuming that CJ is my slave and must do it). 

[fovmester]

I like that, Prog! 

[Ubel]

Me too, very good idea ProgZmax! I'd like to see something like this in the later versions of AGS.

[petazzo]

I think it would be useless. Now it works fine, it is intuitive and it don't cover too much space.