Hi,
Regarding the gap between static text and dynamic data, its explorers
and possible bridges, I think that the Smalltalk tradition makes a good
case for writing dynamic data instead of static text. Some years ago, I
talked about Pharo[1], my own, Leo inspired, outliner called
Grafoscopio[2] and now, there dynamic writing and exploration of dynamic
data/systems within such systems have a Glamorout Tolkit[3] which
improves on user interface and notebooks, while being a Pharo based system.
Bridging the gap between static text and dynamic data systems is maybe
one of the most important problems in informatics and user
experience/empowerment. Hopefully the Smalltalk tradition and ideas like
the one in Stop writing dead programs[4] will gain broader mindset. It
is good to see how such ideas are explored with Leo Editor.
[1] https://pharo.org/
[2] https://mutabit.com/grafoscopio/en.html
[3] https://gtoolkit.com/
[4] https://www.youtube.com/watch?v=8Ab3ArE8W3s
Cheers,
Offray
On 14/09/23 7:05, Edward K. Ream wrote:
This Engineering Notebook post discusses what I /wanted/ Sherlock to
do and discusses various alternatives.
*Exploring dynamic data*
We programmers write static text, but our programs deal with
dynamically generated data. I've often wanted better tools to study
the data that flows through our programs.
--
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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/5a932562-9263-166e-e72c-6d9afd403b99%40riseup.net.
