jvkersch's profile - activity

Great, thanks! I was sort of hoping that you had implemented this for your Hopf fibration video :)

Niles, did you ever get this to work? I need exactly the same functionality, but for parametric_plot3d, maybe you can open a ticket for this?

Thanks Mike! Even at the expense of increased load, I think this would be a good thing to have. I've been passing links to Sage notebooks to sceptical colleagues so that they could experience first-hand the awesomeness of Sage, but this is somewhat hampered by the fact that people first have to create a login...

Allowing non-logged in users to use interacts is currently something that's not supported. There's a trac ticket up at #7908 which would allow for this. Also, there's some work being done to make the notebook more scalable to enable the server better cope with the increased load caused by allowing this.

Recently I put together a worksheet with some interactive elements, which I then uploaded to the sagenb.org server for the world's enjoyment. However, the interactive elements (sliders, plots) are only visible when the user is logged in. For users who are just browsing, only the code is visible.

Did I miss a setting somewhere to allow even users who are just browsing to play with the worksheet? Or is this part of the design of sagenb?

The worksheet is up at http://www.sagenb.org/home/pub/2630/. Thanks!

Cool; I didn't think about the fact that non-standard extensions aren't readily accessible from within the notebook.

This seems doable too -- my code is valid Python. Are there any "sage eggs" that I could take apart to see how its done and where the relevant files end up?

I agree that this would be a good idea. It doesn't seem as if the optional packages are reviewed, so that's a good point. I unpacked some of the packages, and it looks like something I could put together.

I've been working on a bit of code that is of interest to a bunch of people but far too specific to even be considered for inclusion in Sage. Is it possible to package my code as an spkg, put the binary on a server somewhere, and then have interested parties install it by typing ./sage -t url-to-package? Or should I just stick to distributing my .sage files as tarball?

Sorry if this is already in the developer manual! However, when I checked, most of the instructions dealt with preparing an spkg and submitting it to the trac server, which is not what I want to do.