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

Feature Request: re-open welcome window / connect to multiple servers #10

Open
goerz opened this issue Jun 1, 2014 · 1 comment
Open

Comments

@goerz
Copy link

goerz commented Jun 1, 2014

A nice feature would be to have an option in the menu to re-open the Welcome window, allowing to connect to a different server, or open the directory listing for a server in case the window was accidentally closed.

My use case right now is that I start multiple iPython notebook servers (with different working directories) on the command line, and the have ipython-desktop connect to one of them by setting the correct port number in the configuration. At the moment, I can only connect to on server that way; it would be nice to do multiple connections.

I can do this easily in the browser, of course, but what I like about ipython-deskop is that I have a separate app. In the browser, I always and up with a million open tabs, and it's hard to switch between regular browsing and the tabs running my notebooks easily.

@mangecoeur
Copy link
Owner

I did think of this use case, but it's quite fiddly to handle, mostly because the mechanism for keeping track of ipython server processes at the moment is very primitive. I tried to design the desktop experience to be more like a regular app, when you close the welcome window the server is stopped. It could definitely be more refined.
Specifically I would like some way of starting the server as a child process to make sure it is always killed when the parent process terminates. At the moment I could sort of handle the scenario you suggest but a lot of failiure cases would result in orphaned ipython processes. Not got enough time just now to fix this properly, but its definitely on the cards at some point.

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

No branches or pull requests

2 participants