Opened 12 years ago

Last modified 4 years ago

#322 new enhancement

Have global code page for Notebook

Reported by: TimothyClemans Owned by: boothby
Priority: minor Milestone: sage-feature
Component: notebook Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: Reported upstream. Developers acknowledge bug. Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description

Create a system for adding code to a notebook that can be executed by code in any cell in the worksheet. Before a chuck of code could become global the system would check it to make sure it does overwrite current SAGE functions, variables, and classes. Maybe the system could do that by executing the code and using the name space key in the various dictionaries to then see if a not found error is returned when name space called. It would be also be important for it to be easy to download a code package to be made global. I want this so I can make apps and use them from any cell in the notebook.

Change History (4)

comment:1 Changed 12 years ago by was

  • Resolution set to invalid
  • Status changed from new to closed

This functionality is already provided in the SAGE notebook by putting #auto somewhere in a cell. Also, using %hideall one can even hide the global code.

It's odd, because I've seen you use this functionality in your example sage notebook applications, so you know about it. Hmm.

comment:2 Changed 12 years ago by TimothyClemans

  • Resolution invalid deleted
  • Status changed from closed to reopened

I said notebook not worksheet. I'm talking about writing a function or class in a global worksheet from I could use from anyother worksheet. #auto has nothing to do with global just writing a function in a cell makes that function global for the whole worksheet that the function is defined in.

comment:3 Changed 11 years ago by mabshoff

  • Milestone set to sage-feature

comment:4 Changed 4 years ago by kcrisman

  • Report Upstream set to Reported upstream. Developers acknowledge bug.

See https://github.com/sagemath/sagenb/issues/263 where I suggest that the easiest thing to do is have a 'global' (per user) DATA directory just like there is the per-worksheet DATA directory.

Note: See TracTickets for help on using tickets.