[sage-support] Re: Sage VM: Googe Chrome should NOT run in kiosk mode

2012-12-03 Thread Volker Braun
Really I see the browser running inside the VM as a crutch for those that 
can't use their host browser because of a misconfigured firewall. 

I understand your frustration being stuck with kiosk mode, but I don't 
think that making the environment in the VM more complex is a good idea 
either. Not using kiosk means you have to add window manager, desktop 
environment, ... Ideally the notebook would have some plugin system so we 
can add additional settings in the notebook settings to configure keyboard 
and other basics. Perhaps run a web-based shell or file manager. And/or a 
python script running on the host that can pull files out of the VM. 

If you really want a full desktop environment in the VM then its not that 
difficult to install; go to the console, log in, yum install whatever you 
want.



On Monday, December 3, 2012 2:05:46 PM UTC-5, john_perry_usm wrote:

 Hello

 Sage VM runs Chrome in kiosk mode, and refuses to get out of kiosk mode (I 
 can press F11 to my heart's content; it doesn't change anything), therefore 
 won't allow any changes to its settings. The settings certainly need to 
 change for non-trivial work, as when I'd like to save a worksheet to a 
 shared folder created through the VM, and not to /home/gui/Downloads, which 
 is not accessible to the Windows desktop, or not easily.

 For some real entertainment, try clicking on Chrome's invitation to view 
 the folder where a file was downloaded. The window comes up full screen and 
 you can't navigate back to Chrome, or not easily.

 What exactly is the appeal of kiosk mode? On the user's own machine, it 
 constrains the user and makes it hard (well nigh impossible?) to change 
 settings or to explore. Perhaps there is some trump in kiosk's hand of 
 which I am unaware, but IMHO it has to go.

 john perry

 PS: I also liked the old way, where the user was given an explicit option 
 to run command-line sage or worksheet sage. I can work around the current 
 approach (CTRL+ALT+Fsomething does the trick), but if anyone cares, it 
 would be really nice to have the old way back.


-- 
You received this message because you are subscribed to the Google Groups 
sage-support group.
To post to this group, send email to sage-support@googlegroups.com.
To unsubscribe from this group, send email to 
sage-support+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support?hl=en.




[sage-support] Re: Sage VM: Googe Chrome should NOT run in kiosk mode

2012-12-03 Thread john_perry_usm
On Monday, December 3, 2012 1:24:38 PM UTC-6, Volker Braun wrote:

 Really I see the browser running inside the VM as a crutch for those that 
 can't use their host browser because of a misconfigured firewall. 


Pshaw. For some reason I was under the impression that this wasn't working 
anymore. Probably because some student had a misconfigured firewall, and I 
didn't see it.

I'm working with another student now, and you're right, it works just fine. 
Thanks for pointing that out. :-)

john perry

-- 
You received this message because you are subscribed to the Google Groups 
sage-support group.
To post to this group, send email to sage-support@googlegroups.com.
To unsubscribe from this group, send email to 
sage-support+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support?hl=en.