Github user AhyoungRyu commented on the issue:

    https://github.com/apache/zeppelin/pull/1734
  
    @1ambda Great initiative for improving interpreter binding page UI! I also 
agree that current binding page is getting longer (thanks to the Zeppelin 
contributors :D) and getting hard to find. Definitely needs to be improved. I 
tested this branch and checked the improvement. Let me share my thought about 
this patch in here.
    
     - Currently the restart button is exposed so that ppl can know "I can 
restart this interpreter by clicking this button" by instinct. But \w this 
patch, ppl need to click "Carrot" button to open the dropdown menu and need to 
click "Restart" button to restart interpreter. And the user need to click at 
least one time to know about this. 
    
     - Seems don't need another tooltip in here since there is already the text 
"Restart"
    ![screen shot 2016-12-09 at 4 30 48 
pm](https://cloud.githubusercontent.com/assets/10060731/21041414/37198bb8-be2e-11e6-8d80-9c6420738110.png)
    
     - The color change for default interpreter is good idea i think! But the 
color is gone when it comes out as a result. 
    
![search_interpreter](https://cloud.githubusercontent.com/assets/10060731/21041453/67d16cda-be2e-11e6-9f6c-8b8e77b0a423.gif)
    
     - Shirking overall size also good idea. Was quite verbose. But the thing 
that interpreter button has smaller height than dropdown menu is quite awkward 
to me. 
    ![screen shot 2016-12-09 at 4 50 01 
pm](https://cloud.githubusercontent.com/assets/10060731/21041612/8fdeb128-be2f-11e6-891a-18c2bd760d17.png)
    
     - How about "Search bindable interpreters(?)" instead of "Search 
interpreter Bindings"? :D 
    <img width="335" alt="screen shot 2016-12-09 at 4 48 59 pm" 
src="https://cloud.githubusercontent.com/assets/10060731/21041595/6681d904-be2f-11e6-82c2-c7499f0d0875.png";>
    
    Most of them in the above are just my personal opinion. So surely you don't 
need to apply all of them. And thanks again for your effort to improve the UI! 
    
    



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to