Great, I look forward to seeing what else Icenium has in store.
#1. Just to follow up about the "Add" menu - I wasn't so much concerned about the behavior of the menu as I was about it's placement
. It only
applies to the Project Navigator/File Structure, so it belongs in the Project Navigator portion of the screen.
To emphasize further - you can collapse the Project Navigator to give you more screen real estate, and now the "Add" menu really
feels out of place.
Putting elements where they belong (meaning closest to the resources they operate on) will reduce confusion. That's all I'm sayin'.
#2. Oh and here's one more UI thing I noticed - when attempting to create a new file, if a file already exists with the same name, the OK button is disabled. Now in the user's mind there could be any number of reasons why a button would be disabled - and you're making them guess which one. Here was my scenario:
- Last week when I was playing around with Icenium Mist, I created a new html document with the default HtmlPage.html file name.
- Today when I was playing around with Mist, (specifically seeing how the "Add" menu would react when the Project Navigator part was closed), I clicked "Add" -> "New File" and I was prompted with the file creation dialog.
Now granted, someone who was actually developing an app would probably know their file names and not use the default ones, but you should still consider adding a message detailing what is wrong/what the user needs to fix.