Open GoogleCodeExporter opened 8 years ago
Here is a Screenshot of my suggestion.
Original comment by thadguidry
on 27 Aug 2011 at 9:56
Attachments:
Thanks, Thad. Originally, because the preview updates as you types and changes
the expression, the intention of showing the expression in the preview column
header is for you to know which expression (editing version) it corresponds to.
I do understand that this design has its problems and will think about it.
Original comment by dfhu...@gmail.com
on 27 Sep 2011 at 9:05
But do you think a user will simply know their expression anyway, since it will
be in the larger text area above ? My thought was YES, and so my feeling of
feeling redundant, and the header better used as a hinting mechanism. Hmm,
maybe a 2 header system would work, the 2nd header being for errors and hints,
or perhaps errors and hints should always be handled generically with jquery
popup overlays ?
Original comment by thadguidry
on 27 Sep 2011 at 1:21
The scenario is this: the user is typing in some rather long expression, and
the preview is lagging behind (especially if Refine is not run on the local
machine). When the user stops typing and looks at the preview, we want them to
know whether or not the preview is displaying the results of the full
expression, rather than some intermediate, half-baked version that likely
contains syntax errors.
Then there's also the issue of what text to display for various types of
intermediate result objects. Full Java class names seem a bit too low-leveled.
Original comment by dfhu...@gmail.com
on 28 Sep 2011 at 3:45
Renamed issue. Marked as Enhancement, Post 2.5.
Original comment by dfhu...@gmail.com
on 29 Sep 2011 at 3:07
Original comment by tfmorris
on 18 Sep 2012 at 3:15
Original issue reported on code.google.com by
thadguidry
on 27 Aug 2011 at 8:57Attachments: