Github user eranwitkon commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/191#issuecomment-129781252
Here they are re-attached
On Mon, Aug 10, 2015 at 10:23 PM Lee moon soo <[email protected]>
wrote:
> @eranwitkon <https://github.com/eranwitkon> Thanks for the feedback.
>
> 2) hide the notebook from the list works fine
> BUT I had a problem with my MD notebook when I set the tutorial notebook
as
> home page ( 2A94M5J1Z ) everything worked fine but setting my md notebook
> showed an empty page.
> attached is my md notebook
> Here is my homepage open as notebook:
> [image: Selection_010.png]
> Here is what I get when I set it as homepage
> [image: Selection_011.png]
>
> Could you re-attache screenshot?
>
> 3) idea: can we add a button on the notebook level by the schedule button
> with the "Set as homepage" option? instead of editing the env\site files?
>
> If there's "Set as homepage" button, the information need to be saved.
> I think note.json is not the place, because two or more notebook can have
> "set as homepage" option on, while note.json can be copied from the other
> instance of Zeppelin.
> Information need to be saved in somewhere Zeppelin instance specific place
> (like conf/interpreter.json).
>
> I think having "set as homepage" button is big enough to discuss and
> implement separately.
>
> 4) idea: out of the scope of this PR but should we have a zeppelin
function
> which list the notebooks in zeppelin e.g. z.notebooks collection, so I can
> write my personalized homepage but still get the list of notebooks? - if
> needed I can see the current homepage implementation and refactor it as a
z
> method.
>
> This is good idea and can be a future work
>
> â
> Reply to this email directly or view it on GitHub
>
<https://github.com/apache/incubator-zeppelin/pull/191#issuecomment-129572986>
> .
>
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
