Hi Eran, Thanks for sharing feedback. To me #2 make sense. #1 Like Christian Tzolov mentioned, I think showing output will not suitable for all cases. I think we can have small indicator instead of changing current behavior. For example, 'Show output' button on paragraph can blink when there're updated output.
Thanks, moon On Thu, Aug 6, 2015 at 2:43 AM Christian Tzolov <[email protected]> wrote: > +1 I've observed this behaviour and agree with both suggestions. > > I have some doubts whether #1 is suitable for all cases. For example a > paragraph with initialization shell scripts that produce tons of logs. > Normally I don't want to see those logs, at least not until an error > occurs. Of course one can redirect the output to a file to prevent result > pollution but still it is worth considering such usecases. > > On 6 August 2015 at 11:00, IT CTO <[email protected]> wrote: > > > Hi, > > I noticed today two issues with the show results button in the notebook > > and paragraph (the book like icon) > > 1) The first is that if we hide the result and update the paragraph and > > run it again no output is shown to the user. - we got a mail from our > user > > saying that zeppelin is not working just because he did not get any > > response as the paragraph output was closed. > > > > 2) the logic of the paragraph icon and the notebook icon is not the same. > > in the notebook the icon shows a closed book when results are shown (e.g. > > click here to close the result) while in the paragraph it is the > opposite. > > > > [image: Selection_008.png] > > my suggestion > > #1 - we should open the result upon running the paragraph or at least > > indicating that the output is closed. > > #2 - change the notebook behavior to match the paragraph behavior > > > > Eran > > > > > > -- > Christian Tzolov <http://www.linkedin.com/in/tzolov> | Solution Architect, > EMEA Practice Team | Pivotal <http://pivotal.io/> > [email protected]|+31610285517 >
