Skip to content

Conversation

@prabhjyotsingh
Copy link
Contributor

In current behaviour we have a fixed height for result container that contains either graph or table, but if type is text then the container expands to infinitely.

When type is text; then this is mostly logs, so we can have scroll around it and have fixed height for this container.

Before
screen shot 2015-12-07 at 4 11 49 pm

After
screen shot 2015-12-07 at 4 16 46 pm

@prabhjyotsingh
Copy link
Contributor Author

Also I've removed "loadResultType" function calls, as it did not had any respective loadResultType declaration or implementation.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

empty else {} is a bit odd?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I picked template function from $scope.renderHtml; fixed both $scope.renderHtml and $scope.renderText

@prabhjyotsingh prabhjyotsingh force-pushed the ZEPPELIN-491 branch 10 times, most recently from 93c8f38 to 3f14de7 Compare December 17, 2015 19:04
@prabhjyotsingh
Copy link
Contributor Author

Also I think this should have scroll to bottom of output button.

screen shot 2016-02-08 at 3 26 28 pm

@prabhjyotsingh
Copy link
Contributor Author

Have implement follow scroll to the end and scroll to top.

If there is a streaming output user can always have an eye on end of scroll.

ezgif-2672918947

@rconline
Copy link
Contributor

rconline commented Feb 9, 2016

Looks good. Can we get some attention from committers. Thanks!

@felixcheung
Copy link
Member

wow you are building Zeppelin from within Zeppelin ;)
@corneadoug - could you check this out please?

ng-click="scrollParagraphDown()" ></div>
<div id="p{{paragraph.id}}_text"
style="max-height: {{paragraph.config.graph.height}}px; overflow: auto"
ng-scroll="someFunction()"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is that line for? I didn't see any change when trying with and without.
Not sure if its necessary since someFunction doesn't exist anywhere

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Totally missed to remove this.

@corneadoug
Copy link
Contributor

Could you use the same tooltip as everywhere else in zeppelin for those two buttons?

@prabhjyotsingh
Copy link
Contributor Author

@corneadoug Thanks for the review. I was just experimenting with look and feel of those two buttons, but what you recommend makes more sense.

- have standard toooltip for Follow output and scroll top
@prabhjyotsingh
Copy link
Contributor Author

@corneadoug does this looks ok?

@corneadoug
Copy link
Contributor

Yes, LGTM

@felixcheung
Copy link
Member

merging if no further discussion

@asfgit asfgit closed this in 4daf7aa Feb 14, 2016
@prabhjyotsingh prabhjyotsingh deleted the ZEPPELIN-491 branch February 24, 2016 05:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants