Hi,
On 15/09/15 09:30, Edward K. Ream wrote:
[...]
We would all like to mix and match the favorite features from two
different apps. Even with open software that can be a practically
impossible task. There are various workarounds, including support for
importing and importing data from other apps. One of the things on
Leo's to-do list is to be able to import and export .ipynb files.
I'll say more about IPython in another thread.
Yep moldability (being able to mix, match and evolve) is an important
feature of tools that is almost forgotten or can be difficult to
implement. Sometimes changing the language/environment can be a proper
way to reframe/rethink the problems (as Kent pointed so cleverly with
the transition from C++ to Python in Leo's case). On moldability this
approach is very interesting[1]:
[1] http://scg.unibe.ch/research/moldabledebugger
Nice to see that this threads going towards cross-pollination of IPython
and Leo features. As you refer in the other thread, there is no document
level organization in IPython, which is really powerful in Leo and with
long exploratory documents the flat structure starts to weight a lot
(look the screenshot of an "abandoned" real case at [2]). Also having
interactive nodes ala IPython inside Leo trees could be powerful (in
trusted environments like the ones IPython/Jupyter are used). Enabling
sensible defaults for users, with this features integrated, could be
path to the "instant appeal" of Leo and wider adoption that has been
discussed in this community.
[2]
http://mutabit.com/deltas/repos.fossil/piamed/libro/doc/tip/Afiche/narrativa.png
Cheers,
Offray
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
