On Sep 28, 10:38 am, Maurizio <maurizio.gran...@gmail.com> wrote:
> Can't we take advantage of inheritance for this issue? I don't know
> how far that can go, though, I'm not a programmer...
>
> Thanks
>
> Maurizio

I think this will cause headaches to non-programmers, if your idea of
dependence does not agree with the computer's. Your idea is probably
good for spreadsheet-like calculations, but maybe not for the large
code cells now common in sage. For few large cells with complex code,
the preparser might fail to find the correct dependence tree, but for
you it's a trivial task.

I think something like William proposed is more transparent. The GUI
might allow you to mark dependent cells explicitely with keystrokes,
clicks and commands.

For example, you click on a cell to select it, then Control+click on
the cell above to mark the current cell as dependent on the above, and
the color of the cells border changes to reflect that. From now on,
when you select a cell, that cell is blue, the ones it depends on are
red, and the ones that depend on it are green.

Or you can type control+shift+Enter, and a new cell appears below the
current one that depends on it.

Or you write chain(5) in one cell and get 5 cells afterwards, each
dependent on the previous ones.

But after messing around all you want, if you edit the source code,
you'll just find a statement like %eval([4,5,6]) at the end of a cell,
where [4,5,6] is the list of ids of the cells that depend on the
current one, maybe a comment at the beginning like #depends 1 2 that
lists the cells it depends on.

And of course it's completely optional, you don't even have to know
the possibility exists to use SAGE as you've done before.
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to