Up until a few weeks ago, I loaded/hid sage code in exactly that way. As you pointed out, that's now broken, so I'm trying to find another path forward.
On Tuesday, March 30, 2021 at 4:38:19 PM UTC-4 [email protected] wrote: > You may - theoretically - hide code by puttting it into a python file at a > URL and including *load(URL)* into the first sage cell. That code would > be loaded when the reader evaluates this cell. > Unfortunately, recently this stopped working when SageCell removed it's > Internet support. Hopefully, this will soon be re-established for selected > URL, in particular for URLs ponting to Github files. > > Michael Miller schrieb am Sonntag, 28. März 2021 um 22:51:16 UTC+2: > >> I'm setting up a sage cell that requires some front-end code to define >> functions. Rather than requiring my users to scroll through that code, I'd >> like to "hide" it. >> >> One possibility would be to autoeval the front-end code in a cell with a >> minimal template and hidden editor, then have my users work in a second >> (linked) cell with a normal template and editor. But defining cells with >> different templates seems to require using different div classes, and >> linked:true seems to work only within a class. >> >> 1) Is there a better way to "hide" code? >> >> 2) Is there a way to link cells that have different templates? >> >> Thanks! >> > -- You received this message because you are subscribed to the Google Groups "sage-cell" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-cell/ba1abd16-ccc8-4647-8a46-8e77658969f3n%40googlegroups.com.
