Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Expression Preview dialog to show type of results #443

Open
GoogleCodeExporter opened this issue Jan 26, 2016 · 6 comments
Open

Comments

@GoogleCodeExporter
Copy link

Line 424 Can we show the Type() of expression output with color coding, instead 
of the redundant expression itself ?

Original issue reported on code.google.com by thadguidry on 27 Aug 2011 at 8:57

Attachments:

@GoogleCodeExporter
Copy link
Author

Here is a Screenshot of my suggestion.

Original comment by thadguidry on 27 Aug 2011 at 9:56

Attachments:

@GoogleCodeExporter
Copy link
Author

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 [email protected] on 27 Sep 2011 at 9:05

@GoogleCodeExporter
Copy link
Author

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

@GoogleCodeExporter
Copy link
Author

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 [email protected] on 28 Sep 2011 at 3:45

@GoogleCodeExporter
Copy link
Author

Renamed issue. Marked as Enhancement, Post 2.5.

Original comment by [email protected] on 29 Sep 2011 at 3:07

  • Changed title: Improve Expression Preview dialog to show type of results
  • Added labels: Milestone-Post-2.5, Type-Enhancement
  • Removed labels: Type-Patch

@GoogleCodeExporter
Copy link
Author

Original comment by tfmorris on 18 Sep 2012 at 3:15

  • Removed labels: Milestone-Post-2.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant