2009-06-25, 09:19
Don't know if this applies to the issue I mentioned ... By default, I was under the impression I started with caching off; however, I've tested it with both options.
For the record, I too made it very clear in my post that I think Ember outshines all others -- not only from it's capabilities, but in it's very methodology and design paradigm. This has nothing to do with my point earlier, about not having to continue replying to the same questions / or the need for explicit questions to debug. And it certainly doesn't suggest that I feel the software is any less viable and to anyone whose read the forum, just about everyone here can appreciate the early stage of the app.
With that said, here are some quick suggestions (some of these may already be addressed) in the event you see benefit in them:
* Option for More verbose/finite logging (not only on-error). This is all the more important as you're seeing, where the app works perfectly for one person and doesn't for another. In this development stage, verbose logging will be well worth the upfront overhead to author.
* Feature Request. Probably the most intuitive feature I've noticed missing, is the inability to multi-select (Cntrl-A / Shift-Click / Cntrl-Click) and then either proceed with those movies selected, or mark those movies selected. Because you're already using the "Mark" paradigm, might as well stick with it, but multi-select should be enabled at least for purposes of marking multiple rows at a time.
* Minor Unexpected Behavior. When switching between line-items in the Movie-Metadata list (to choose the specific movie when multiples exist), the process (which appears to be async) is not terminated when the user clicks to a different line item. To the untrained user, this causes a bit of confusion as it appears the results are being rendered for the newly selected item (when they are not).
* False Matches that are not a result of the data provider. I noticed some strange behavior with roughly 1-in-20 movies, where the data provider was returning "exact matches" or preferred matches, yet Ember was not choosing them. I only ran the first 200 movies in my collection (since I'm forced to explicitly right-click each, at this early stage) -- but some movies, such as "Baby Momma" "Better Off Dead" "Bookies" "Edward Scissorhands" had exact matches, and yet Ember used alternatives or marked them as unavailable.
For the record, I too made it very clear in my post that I think Ember outshines all others -- not only from it's capabilities, but in it's very methodology and design paradigm. This has nothing to do with my point earlier, about not having to continue replying to the same questions / or the need for explicit questions to debug. And it certainly doesn't suggest that I feel the software is any less viable and to anyone whose read the forum, just about everyone here can appreciate the early stage of the app.
With that said, here are some quick suggestions (some of these may already be addressed) in the event you see benefit in them:
* Option for More verbose/finite logging (not only on-error). This is all the more important as you're seeing, where the app works perfectly for one person and doesn't for another. In this development stage, verbose logging will be well worth the upfront overhead to author.
* Feature Request. Probably the most intuitive feature I've noticed missing, is the inability to multi-select (Cntrl-A / Shift-Click / Cntrl-Click) and then either proceed with those movies selected, or mark those movies selected. Because you're already using the "Mark" paradigm, might as well stick with it, but multi-select should be enabled at least for purposes of marking multiple rows at a time.
* Minor Unexpected Behavior. When switching between line-items in the Movie-Metadata list (to choose the specific movie when multiples exist), the process (which appears to be async) is not terminated when the user clicks to a different line item. To the untrained user, this causes a bit of confusion as it appears the results are being rendered for the newly selected item (when they are not).
* False Matches that are not a result of the data provider. I noticed some strange behavior with roughly 1-in-20 movies, where the data provider was returning "exact matches" or preferred matches, yet Ember was not choosing them. I only ran the first 200 movies in my collection (since I'm forced to explicitly right-click each, at this early stage) -- but some movies, such as "Baby Momma" "Better Off Dead" "Bookies" "Edward Scissorhands" had exact matches, and yet Ember used alternatives or marked them as unavailable.