Jul 10, 2012 at 6:08 AM
Edited Jul 10, 2012 at 12:12 PM
Just played with it for a few minutes... it's still a little rough around the edges in places (I get "undefined" errors and some "java.lang.NullPointerException" exceptions when logging in), but thereafter it worked pretty well.
In terms of feature ideas, here are a few (I'm sure many duplicate your own list):
1. I couldn't immediately find the actions for an object, so I think they may need emphasising more.
2. I find it annoying that all windows appear in the middle, over the top of each other. Could you use a more intelligent algorithm?
3. I find the windows rather long and thin. Perhaps the collections could go off into a second column?
4. when a collection is opened, it creates a new window that is divorced from its owning object. If you moved the collections to one side, then the collection list instead could automatically open up in a div within the owning object (gracefully slide
5. the reference properties labels are not in bold whereas the value properties are. At first it wasn't obvious to me that they were reference properties
6. in all cases the reference properties were after the value properties. I suspect that this isn't honouring the member ordering; they are typically intermixed
7. the pop up boxes are ugly and in a different style; only critical warnings/errors should be a pop-up box, informational messages (eg acknowledging a property update) should be in some sort of discrete status bar
8. although I can tab around the widgets, I couldn't see how to invoke the menu actions at the top. Also, there doesn't seem to be any way to tab to an object's action menu
9. titles are not updated even if the underlying properties are
10. if I have two views up of the same object, and update one, then the other is not updated
11. bug: search for a Customer using "Find Customer by Account Number". Enter "AW00023447". Hit OK with the mouse ... it works. But hit enter, and it doesn't work, the URL in the bar changes, and the app is then frozen
I was using the current Chrome (20.0.1132.47) on Windows for this testing.
Another thought: since I'm sure you're going to get lots of other good ideas from folks, plus your own list, perhaps you should add them into github as issues? I've just added #11 as your first github issue. Was hoping there'd be a vote button, but there
doesn't seem to be.