I'm having a number of problems with the browser UI that I'm hoping someone can help me resolve. I'm building relatively complex templates in 5.0 (5.5 in a month or so) that I need to give to clients who (to maintain everyones sanity) we assume are idiots. If its not obvious, they're going to call my customer service people who will in turn call me. I hate getting phone calls
So here are my problems:
With the Java UI, if I have a replicant with 0 instances, you can still see a label that tells you what you are replicating. With the browser UI, all you see is an empty bar with a button on the end. This triggers a number of usablity problems:
First, because the tree view is initially collapsed, just looking at the form gives me no indication what those bars are going to do. Even when I expand the tree view totally, there is no visual connection between what I see in the tree view and what I see in the form frame.
Second, in a relatively complex template, finding the relevant entry in the tree view for a replicant can be challenging. Clicking on the entry in the tree view sets no obvious focus on the frame with the form. You still have to guess what does what.
Third, if you have several replicants in a row, it gets very hard to find the one you want. And heaven help you if you have a replicant (whose content ends with a replicant that has 0 instances by defualt) followed by a number of other replicants. You just don't know whats going on.
Fourth, if you have an expanded replicant followed by a regular field, there is no obvious way to distinguish where the replicant ends, without looking at the tree view, which still requires a bit of thought.
So does anyone know how I bend the Browser templating into something more usable?
I'd use the Java UI, except that my descriptions, which tend to be long and descriptive get strangly truncated.
Adam
