On 21/03/17 10:31, Edward K. Ream wrote:
On Tue, Mar 21, 2017 at 10:05 AM, Offray Vladimir Luna Cárdenas
<[email protected] <mailto:[email protected]>> wrote:
>
Thanks to you for Leo and this live and constructive community. Ideas
are difficult to express by mail... sometimes is easier to build your
own software and send the link to the mailing list :-).
The links to the videos were especially helpful because they show the
dynamic nature of the software in action.
Yes. They revealed to me that Live coding and Agile Visualization give a
particular edge to Pharo over other technologies to prototype ideas. But
finding the proper"narrative" to share them took a lot of time. This
narrative is literate computing and now we're talking a lot about blue
sky Leo futures.
As I see it now, the question is always, "how easy is it to
emulate feature A in environment B?". It's pretty easy to set up
an @button node in Leo so that it emulates Pharo's instant
execution model. Whether it's possible to get access to agile
visualization in the python world is another question.
Agile visualization and live coding are game changers for me, so
much that Pharo became my platform to express/combine ideas.
Jupyter is exploring that path in some way for the Python word
with interesting ideas and a lot of attention, but also with a
complex multilayered (fractured?) stack behind. Hopefully Leo will
provide clarity there also.
Yes, I now understand why you like Pharo.
I used to think that coffeescript might be a good enough wrapper for
javascript, but having seen d3 and the agile visualization demos, I
think the only way to use javascript is via a package. There just
isn't time for low-level javascript (or coffeescript) coding.
I agree. In [1] I compare a little bit of D3 with Agile Visualization
(Roassal). Live coding still gives an edge, because you don't have to
deal with the fractured file system world: load/edit a file, (re)load
rendering in the browser, choose/learn your code editor and DCVS, etc.
There is a lot of friction. In the Grafoscopio User Manual (in English)
I say where Grafoscopio is similar and different from other tools
(including Leo, Jupyter and OrgMode). So yes, having coffe script as a
reference could be good, but I think that vega and vega lite or other
hight level languages should be part of the default experience of
literate computing in Leo, and the core search for future releases could
be in how to bring live coding to python via Leo (and its powerful
self-referential tree/DOM).
[1] http://mutabit.com/offray/blog/en/entry/sdv-infomed
[2]
http://mutabit.com/repos.fossil/grafoscopio/doc/tip/Docs/En/Books/Manual/manual.pdf
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 https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
