Re: I just tried notebookLM! 🤯

Hi, On 17/09/24 11:04, Edward K. Ream wrote: I should emphasize that all these AI tools should be valuable as starting points. [...] The same strategy should work with a blog about Leo or LeoJS. Revise the results until they pass expert judgement. Revise the settings to eliminate any hint o

Re: Abridged summary of leo-editor@googlegroups.com - 1 update in 1 topic

Hi, On 6/07/24 23:18, Félix wrote: Some personal thoughts: The genius of Leo, its 'foundational features independent of their implementation' or, if you will,  the 'Leo-as-an-idea' concept... Is the masterpiece, from Edward's mind. Maybe Edward feels otherwise because its implementation is,

Re: LeoJS needs to be its own thing

Hi, On 7/07/24 12:05, Thomas Passin wrote: Again, TiddlyWiki seems the model.  In fact... a Leo plug-infor TiddlyWiki would seem a natural! I've tried TW at least three times over the years.  At first I think it's wonderful, then little by little I learn again that it's not quite wh

Re: On Leo's strengths outside the technical

I agree with you Matt. As I have documented in this very list, as I have drifted away from Python and textual representation of computing to Pharo and live coding, I'm not using Leo daily anymore and instead I'm putting my effort in building a interactive documentation solution made on top of P

Re: ENB: Seconds thoughts about Trilium Notes

Hi, On 26/04/24 16:36, Matt Wilkie wrote: Leo is plain text first, and achieves rich text and media by rendering. Trilium is rich text and media first, with the primary entry mechanism through the 3rd party CKEditor which saves as html. This is the foundational split behind the whole VR and

Re: ENB: Seconds thoughts about Trilium Notes

Hi, On 26/04/24 11:49, Thomas Passin wrote: I think that Edward does not appreciate how often users want to use Leo as an *Notebook* as opposed to a *writing* tool. For a notebook, one wants to include all kinds of material, text and graphics, and then *look at and read* it many times. For w

Re: I just had successful eye surgury

Edward, Take good care of yourself and your health. We'll be missing you, but the community knows that your wellness comes first. Best recovery. Offray On 28/03/24 15:03, Edward K. Ream wrote: A vitrectomy

Re: ✨LeoJS beta 0.2.11 Released!

Talking about AI (or Apparent Intelligence, as I like to call it) generated images. The Asian lady in the first picture, has this kind of "strange AI hands": https://www.youtube.com/watch?v=24yjRbBah3w Congrats on the new releases. Offray On 23/01/24 11:34, jkn wrote: Reminds me of this, a

Re: Issue #3710: EKR's last lecture

Also I recently discovered Julia's Pluto[1][1a] and I really like their focused notebook environment saved in plain text instead of Jupyter's cumbersome and human unfriendly JSON. A breath of fresh air, following the steps in human/diff friendly formats for interactive notebooks of Pharo's Graf

Re: Issue #3710: EKR's last lecture

On 27/12/23 2:52, Edward K. Ream wrote: On Tue, Dec 26, 2023 at 6:14 PM Offray Vladimir Luna Cárdenas wrote: > Thanks for your "last" lesson You're welcome. > Regarding Rust. I have found Nim[1] a pretty good language. Thanks for the link. I am converting leoAst.p

Re: Issue #3710: EKR's last lecture

Thanks for your "last" lesson, despite with you interactions after that post you keep teaching us in the community. Regarding Rust and the oxidation of everything (A.K.A. rewrite it in Rust) I have found Nim[1] a pretty good language with visible inspirations on Python (like its syntax) and wi

Re: Leo, @auto-md, and Markdeep

On 19/12/23 20:29, Thomas Passin wrote: On Tuesday, December 19, 2023 at 7:38:30 PM UTC-5 off...@riseup.net wrote: ...  What has been pretty useful is also to have a web preview of the document running in localhost. Something similar, implemented with some minimal server, like Flas

Re: Leo, @auto-md, and Markdeep

Hi, This is a no so long detour on a sightly related matter on how we are using Markdeep for our documentation purposes. At the end, I offer some insights of what could be useful if such workflow would be implemented in Leo or LeoInteg. I have been using Markdeep as a way to create data narr

Re: ENB: Moving on from Sherlock

Edward, I'm happy to see that you have move on, finding value in Pharo (an hopefully other links) despite of finding the "Stop writing dead programs" condescending and even insulting. Of course, the fact that robust and modern systems have been massively constructed in a particular way, does

Re: ENB: Moving on from Sherlock

On 14/09/23 20:18, HaveF HaveF wrote: 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 o

Re: ENB: Moving on from Sherlock

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]

Re: New User's Guide To Leo

Hi Thomas, This looks pretty good! Thanks for the document and the effort behind. The visual tour of what Leo is capable of is very compelling and a good showcase to new users about why to use Leo. Keep the good work, Offray On 7/05/23 23:56, Thomas Passin wrote: I've been thinking that the

Re: New Leo "Package" File Format?

Hi, What we do, is that we package the associated files to a data narrative as a Fossil[1] repository, with versioned and unversioned files. Versioned files are used for the ones where we want to track the history and the unversioned are used for raster files (for example, PDF outputs for the

Re: Thumb-nail Explanation Of Leo

I think that your explanation is pretty complete. For me, one of the most important aspects of Leo is that the structure of the plain-text documents is not only implicit, and in that sense "rarely visualized", as you put it, but also emergent and user provided. I was always able to take a plai

Re: Feature to upgrade leoInteg and vscode

Upvoted! Seems that we are just one vote away of getting this feature in the backlog. Hopefully we'll get that vote from a member of this community. Cheers and thanks for the work behind Leo + VS code. Offray On 16/02/23 1:31, Félix wrote: If you feel like it and have 5 seconds of free time,

Re: Abbreviations For Greek Letters

The excellent TeXmacs [1] has the most fluent math/symbolic writing experience I have experienced so far, mostly because of its use of environments (normal text, equations, math, sections/subsections, tabular material and so on). On a particular  environment you press a shortcut and you start t

Re: Leo is (and should be) complete

I join to Thomas' thanks. As I said, Leo and this community has been an important source of inspiration and I'm happy to be part of it since near 2005 and despite not being much active now that I use other languages (Pharo, Lua, Nim) Leo's mark continue in my way of thinking documents and compu

Re: Is It Time For A Leo Project File Format?

I usually keep my Leo files and its imported/exported files in Fossil repository[1] (kind of a GitHub in a box, with less impedance), all with relative links to the repository root where project files are located. Fossil's author propose SQLite as a file format [2][2a] and I think that single,

Re: ENB: Live coding in Leo?

Hi, On 5/03/22 7:09, Edward K. Ream wrote: *Summary* Thanks for these links. The first two deal with system design issues that do not relate directly to programming languages. The second two links relate to issues closer to my world. Edward Thanks for taking a detailed look of the videos

Re: ENB: Live coding in Leo?

Hi, On 3/03/22 8:52, Edward K. Ream wrote: In this Engineering Notebook post I'll explore changing Leo while Leo is running. Imo, changing Leo "on the fly" is impossible, but thinking about what would be necessary might suggest potential improvements to Leo *Background* Live coding is supp

Re: The joys of coming back to Leo

Hi Edward, I don't know abut pylivecoding until now, but I can tell you that  its author was a pretty active member of the Pharo community and made some introductory tutorials to it and projects bridging Pharo, Blender and Python[1], so I can see the traces of a Smalltalk inspired live coding

Re: Schedule for this year

Hi all, It's good to see these paths ahead. I particularly like the priority 3 as it resonates a lot with my approach with Grafoscopio (my Pharo powered outliner, inspired by Leo, Jupyter, TeXmacs, Smalltalk among others) development and its grassroots communities involvement solving "real life" p

Re: 🦁 leojs and leointeg status update 🦁

Hi, Thanks for this work and the link to the issue about what inspired LeoJS at https://github.com/leo-editor/leo-editor/issues/1025 . Even as a long time Leo user (not so much now) I find the succinct definition of the defining features pretty enlightening. In fact I would like to have links from

Re: ENB: The kernel of leojs: Leo in JS

On 16/12/20 4:55 p. m., Edward K. Ream wrote: > > > On Wed, Dec 16, 2020 at 1:32 PM Offray Vladimir Luna Cárdenas > mailto:off...@riseup.net>> wrote: > > On the idea of a Leo core in a machine efficient fast language, I > think that Nim is a worth exploration a

Re: ENB: The kernel of leojs: Leo in JS

On the idea of a Leo core in a machine efficient fast language, I think that Nim is a worth exploration also, as is syntax is Python inspired, compiles to JavaScript, has good metaprogramming facilities. I have found it pretty productive when I need a more low level or multi-paradigm, cross browser

Re: SB: What I'll be studying

hon.git > - cd brython/www > - python3 -m http.server > - browse to localhost:8000 > > (current trunk returns 404 for 'Tutorial' ) > > On Mon, Nov 9, 2020 at 12:27 PM Offray Vladimir Luna Cárdenas > mailto:off...@riseup.net>> wrote: > > Hi, &g

Re: SB: What I'll be studying

Hi, In a world where JavaScript is a commonplace, disliking it becomes automatically opinionated :-). I put sparkles of JS here and there for my web sites, but I don't plan to make it my main programming language and now that JS transpilers are becoming a more common place I plan to keep using Ph

Re: SB: What I'll be studying

Hi, Adding to the Arjan's excellent suggestion, I would recommend: * Computer, Build me an app: https://youtu.be/qqt6YxAZoOc * The Return of 'Write Less, Do More' by Rich Harris  | JSCAMP 2019: https://youtu.be/BzX4aTRPzno For getting the overview you talk about, I would reemphasize the

Re: SB: WordPress web sites

On 24/10/20 6:09 a. m., Edward K. Ream wrote: > > > On Fri, Oct 23, 2020 at 1:48 PM Offray Vladimir Luna Cárdenas > mailto:off...@riseup.net>> wrote: > > I think that the most costly decisions are the first ones, because > one tends to be compatible with

Re: SB: The transition process

On 23/10/20 6:23 a. m., Edward K. Ream wrote: > In other words, it's important now to be as gentle on myself as I can. I have found that being gentle with past and future versions of myself have being healthy, particularly regarding stuff I don't understand yet and/or will be solving or retake

Re: Viewrendered3 How-To -- Insert An Interactive Plot Using Holoview and Bokeh

This is pretty cool! Interactive Live Coding Leo is closer and closer. Cheers, Offray On 15/10/20 5:20 p. m., Thomas Passin wrote: > An interactive plot can be inserted into the VR3 rendering pane.  This > example uses Holoview and Bokeh.  Copy the following code into a node, > open VR3, and exe

Re: I am about to start a sabbatical

Edward, Enjoy your sabbatical, explore new paths, rest, get confused, get inspired, be absent, be here. You have done a lot for this community and Leo is in good shape. So, thank you and see you after it (and a little bit meanwhile). Cheers, Offray On 16/10/20 9:49 a. m., Edward K. Ream wrote:

Re: ch ch changes

Thanks Matt for your active and valuable participation in this community. May the path ahead be interesting and hopefully cross with our, from time to time. Offray On 26/08/20 6:20 p. m., Matt Wilkie wrote: > Hello Edward and Leo community, > > As you've noticed I've kind of dropped out of Leo p

Re: I am going to start using PR's

On 22/08/20 10:37 a. m., Offray Vladimir Luna Cárdenas wrote: > Git/GitHub and kind of formatting processes to the image of the Linux > Kernel development Git/GitHub *is* kind of formatting processes to the image of the Linux Kernel development -- You received this message because y

Re: I am going to start using PR's

Hi, I have seen healthy discussion of features and commits in the Fossil Forum[1], without PR mechanism. I have seen a lot of discussion about features here with the engineering  notebooks withtout PR. Again not a prerequisite. But whatever works best for the community should be adopted. [1] http

Re: I am going to start using PR's

Lunzer, I may share the Fossil comments, as I'm an avid user of it. Paraphrasing Conway's Law[1] culture and infrastructure reflect each other and I think that Git reflect the bureaucracy of Linux Kernel development with its fork and PR by default, while Fossil considers a small group of developer

Re: I am going to start using PR's

On 17/08/20 11:28 a. m., Edward K. Ream wrote: > The days of cowboy commits are coming to an end. > > In future, I plan to create a PR for all my work. A PR is a good > record of what has been done, and it should help prevent unwanted > merge conflicts. > > I think separate PR's for all work make

Re: Why people are excited about vs code. Emacs, not so much

Agreed. VS code is a pretty good bridge for Leo to the masses (what some proposed saw on Jupyter but finally after some exploration it was not). Despite of that niche tools are important too (Leo over native Python is a probe of that). Now that we are exploring the path to the masses, telling that

Re: 1,110 words - "Show HN: Dendron – a roam like open source markdown note taking app"

"monetized" > VSCode sufficiently, it is no longer interested in it and kill the > project, again making it impractical for my use.  Compiling a project > is very far from viable independent  support for a project. > > SegundoBob > > On Sunday, July 19, 2020 at 3:30:29

Re: 1,110 words - "Show HN: Dendron – a roam like open source markdown note taking app"

Thanks Bob, Seems pretty interesting and with good ideas. I'm neither interested in MS stuff since long time ago (I stopped using Windows in 1999 and never looked back). Despite of my practical and philosophical distance with MS, I can see that VS Code is generating a lot of attention and seems t

Re: 23:15 video, "A Tour of Acme (2012)" by Russ Cox

Thanks for this Matt detailed recap (I'm seeing the video right now and mark the paper as pending). Seems pretty interesting, as I have a soft spot for digital artifacts archeology. Pharo/Smalltalk has been making any selected text executable since 70's. Also the idea of maximazed windows/panes in

Re: a portable Leo.exe, maybe

Thanks Matt. Those are good news. Recently I had problems installing Leo on my machine (Manjaro Gnu/Linux), which lead me to test finally Org Mode on Spacemacs (I may share the experience later). Anyway having more multiplatform self-contained programs ala Nim, Go, in Python is really appealing. Ha

Re: Reproducible computational science

HI Brad, I was thinking in combining something like the outline capabilities of Leo with the interactive capabilities of IPython/Jupyter, and I explored such possibility, but I found a lot of incidental complexity in the Python ecosystem[1], so I finally developed a simpler prototype for interacti

Where Leo shines for me

Hi, This is just a short story with two screenshots. I have been using Leo less and less, as I go to live coding and moldable environments and I'm building my own interactive outliner (Grafoscopio) powered by Pharo. But recently I need to tackle a difficult text while preparing a couple of papers

Re: Pyzo as a live Leo explorer

This looks pretty cool Matt! Kind of reminds me about the Pharo inspector[1][2], with its faceted navigation. I don't think this will be integrated in Leo in someway (I don't know about its live introspection capabilities), but is nice to see such experiments. [1] https://www.youtube.com/watch?v=

Re: What's next, continued

On 2/04/20 12:42 p. m., Thomas Passin wrote: > On Thursday, April 2, 2020 at 12:36:33 PM UTC-4, Offray Vladimir Luna > Cárdenas wrote: > >> And I would like to see live coding for Leo. I just don't how >> that's going to happen. >> > Maybe Leo

Re: What's next, continued

On 2/04/20 5:14 a. m., Edward K. Ream wrote: > On Wednesday, April 1, 2020 at 2:48:31 PM UTC-5, Offray Vladimir Luna > Cárdenas wrote: > > Live Coding has been a "dead end" full of "toys" for non-live > coders since about 40 years. > > > I'

Re: About zoom vs leo-editor

On 1/04/20 11:15 p. m., Matt Wilkie wrote: > > Even better that Zoom is Jitsi[1], which doesn't do extensive data > and metadata collection just to have a simple conference, is open > source, gratis, multiplatform and just requires a link to start > your talk. > > [1] meet.jit.

Re: Jupyter vs Leo + VR3

he browser and printed > to pdf. The page breaks aren't the best, but it was quick and simple.  > It whets your appetite, doesn't it? > > Enjoy! > > On Wednesday, April 1, 2020 at 1:40:29 PM UTC-4, Offray Vladimir Luna > Cárdenas wrote: > > > I'm

Re: What's next, continued

Hi, Is good to see the path ahead and the upcoming focus. On 23/03/20 8:11 a. m., Edward K. Ream wrote: > 3. Imo, live coding is a dead end. The cool demos are toys which can > not be scaled up: > > A: *Graphics*: Any graphics-based demo could be more easily recreated > with a slider that changes

Re: About VR3, holoviews and bokeh

This looks really cool! I was asking for a inspiring screenshot in other thread, unknowing that I would find them here. Thanks a lot, Offray On 30/03/20 7:34 a. m., Thomas Passin wrote: > And it turns out that it's just as easy to work with Seaborn, > > On Monday, March 30, 2020 at 6:48:29 AM UT

Re: Jupyter vs Leo + VR3

Hi, Nice to see this theme become alive again, as Jupyter interactive alike experiences combining with Leo outiling alike experience have been discussed before. We could have interactive emergent computing. I have been a log advocate of them and it was the reason I prototyped Grafoscopio[1], after

Re: About zoom vs leo-editor

Hi, Even better that Zoom is Jitsi[1], which doesn't do extensive data and metadata collection just to have a simple conference, is open source, gratis, multiplatform and just requires a link to start your talk. [1] meet.jit.si/ Leo is awesome for a lot of other thinks. Cheers, Offray On 31/0

Re: Leo for organizing notes? [Comments Item 9]

Hi, On 18/02/20 4:26 p. m., Matt Wilkie wrote: > My dream personal info manager and writing environment has the > structural organization and muscles of Leo, the pliable flexiblity of > Joplin, plump cushyness of Onenote, all together supported, wrapped > and transported as single solid entity lik

Re: Reusing design and code: the clash of cultures

Hi, I think that Leo has been pretty good at creating its own singular place that no other program occupies. There are a lot of interactive notebooks, for example and a lot of overlapping ideas in such space. But the way Leo (de)construct text (markup or code) is pretty unique and inspiring, even

Re: Leo for organizing notes?

As you are interested in documentation and Python, a good combination of them are the Jupyter (interactive) Notebooks. You can learn Python 3 using Jupyter and you will be learning also about light Markup languages in an interactive fashion. See more at: https://github.com/jerry-git/learn-python3

Re: Leo for organizing notes? [Experimental Restructuered Text format for a zettel]

Hi, Pretty interesting discussion. On the specifics of a file format. Maybe CommonMark + yaml metadata can be as simple as the proposals here and with all the benefits of Pandoc to process and convert between formats. See for example: http://dpaste.com/34H0J3S Cheers, Offray On 7/02/20 12:00

Re: Programming now feels like playing a video game!

On a related note, with the recent release of Pharo 8, someone said[1]: > I'm sure the author of this language uses the IDE like many people feel when they play minecraft. It's a playground of ideas for those who really love OOP. [1] https://www.reddit.com/r/programming/comments/erd65s/pharo_80_t

Re: On topic: Quanta magazine and today's links

On 9/01/20 5:25 p. m., Matt Wilkie wrote: > > On Thursday, 9 January 2020 13:24:28 UTC-8, Matt Wilkie wrote: > > If I had to recommend one web site on the web, it would be > Quanta Magazine .  It's free, > its articles are superb and filled

Re: Guide to writing better software documentation

Thanks for the link Matt. For me how-tos and tutorials are kind of mixed and I think that the examples don't work well to create a good boundary (teaching a small child how to cook and a recipe in a cookery book can do kind of the same). Also learning and understanding are not good boundaries for

Re: Markdown preferences

Hi, I use Pandoc's Markdown [1] for complex texts (technical docs, meeting notes and so on) and Markdeep[2] for quick publishing on the web and sane defaults. I'm now implementing a workflow to translate for the first to the second and vice versa. Pandoc filters give me the flexibility I need in c

Re: Improved asciidoc, asciidoctor and pandoc support

Hi, Nice to see those additions. In the Leo's documentation, I would expand about why the "pandoc tool must exist". Cheers, Offray On 7/10/19 10:31 a. m., Edward K. Ream wrote: > There are several major features here, spanning several issues, both > open and closed. > > This post will be pre-wr

Re: Status report: asciidoc & asciidoctor

Hi, On 4/10/19 8:26 a. m., Edward K. Ream wrote: > *Asciidoc markup vs markdown and rST > * > > Asciidoc markup is significantly better than markdown > , but > markdown is a straw man.  The real comparison must be between asciidoc > a

Re: Discusss: use Discourse instead of mailing list

Hi, My approach here is different and kind of choosing the underdog: Fossil, Nim, Pharo, Leo, instead of more popular tools. Not because of "underdogness" itself, but because this provides me a particular view point and agility where still few people is located, so the idea/practice to inspiration

Re: Discusss: use Discourse instead of mailing list

Hi, The idea of using another platform, instead of mailing list, has arrived locally from time to time. FYI we have considered NimForum[1] because of its simplicity and because we would like to deploy and migrate data in an easy way in case of being necessary. But for now, we still keep the mailin

Re: Two birthday stories on my 70th birthday

Dear Edward! Happy birthday and thanks a lot for the two decades gift that you have done continuously, year after year, for all of us (I started using Leo around 2005). Your insight, momentum, public thinking and craftsmanship has been really inspiring and energizing for many of us. Leo legacy l

Re: Leo and fossil merged with Rust

Hi, On 30/07/19 10:26 a. m., Matt Wilkie wrote: > > It has been a very long time since I've got this idea of combining > Leo with fossil. For all these years I felt that there was a great > potential in this mixture, but I haven't got the time to do > anything about it until recent

Re: Emacs features in Leo: general remarks

Hi, On 1/08/19 12:30 p. m., john lunzer wrote: > I don't want to imply that the "buffer" system is almighty (which it > is not) or that Leo should try to emulate it somehow. Buffers are > simply the medium through which emacs executes cohesion. Leo's medium > are trees and nodes. > > While each of

Re: Jeff R: What emacs features do you want?

Hi, Just some comments, now that I have the time. On 24/06/19 8:00 a. m., john lunzer wrote: > > > The more one uses emacs the more it becomes obvious that it is not an > editor or an IDE or a PIM, but simply contains all those things. emacs > is not an integrated development environment (IDE) bu

Re: Huge Aha: org mode/vimoutline champions don't have to transliterate Leo's python code!

Congrats on this aha :-) Really glad to see the Leo services coming finally to the picture. It was a long path, but surely a pretty powerful one. Cheers, Offray On 3/08/19 10:13 a. m., Edward K. Ream wrote: > On Saturday, August 3, 2019 at 10:02:53 AM UTC-5, Edward K. Ream wrote: > > *Summa

Re: I stopped using vim mode

IM habits I learnt for years which seem more powerful for > me than LEO's outstanding features. OK, almost everything LEO > suggests I can make with global search-n-replace > > Until I solve the editing issues I wont be able to give more > feedback a

Re: Jeff R: What emacs features do you want?

Hi, Many interesting use case from your original perspective. Leo was my main outliner to (de)construct complex text, as a researcher and PhD student. Clones are a killer feature on that front and I still use Leo to read and organize code which has been written by others. On your particular reque

Re: I stopped using vim mode

Hi, The path Vitalije is suggesting was the one that worked best for me with Leo... but took me years to discover it by myself. My first script was one that took a Leo (sub)tree and exported as a Markdown file in a desired path, using Leo node headers as Markdown headers and Leo node bodies as con

Re: About Leo and rust

Thanks for this encouragements to experiment with Leo in new directions. At some point I plan to retake the Pharo Chronicles, but I think that Leo/Grafoscopio integration would be done at file reading level. I would like to read some Leo outlines from Grafoscopio. Cheers, Offray On 6/07/19 12:0

Re: Team Leo: where are you from?

Hi, Yes, that would be advisable. At least the map I'm seeing here is still a map from the Global North, so Git would be a good way to keep it updated/diverse. Cheers, Offray On 9/07/19 12:27 a. m., Matt Wilkie wrote: > > https://www.mapcustomizer.com/map/Team%20Leo >

Re: Team Leo: where are you from?

On 21/06/19 8:32 p. m., Edward K. Ream wrote: > > > On Fri, Jun 21, 2019 at 8:01 PM Offray Vladimir Luna Cárdenas wrote: > > > seems more like a Global North one. > > Presumably you live in the South :-) Do you want to tell us where? > > I'll be happy to add

Re: Team Leo: where are you from?

Hi, On 20/06/19 6:34 p. m., Edward K. Ream wrote: > > > On Thu, Jun 20, 2019 at 1:30 PM Chris George > wrote: > > https://www.mapcustomizer.com/map/Team%20Leo > > > The world-wide Team Leo. Thanks.  Umm... seems more like a Global North one. I don't want to seem

Re: Book review: Mind in motion

Thanks for the recommendation. I will put the book on the radar. This work kind of reminds me about Richard Sennet and The Artisan, where his main thesis is that thinking is doing and vice versa. On a related note, that is why is so important for me having a live coding environment: is thinking by

Re: Rethinking Leo 6.1 and pyzo integration

Hi, On 21/06/19 11:53 a. m., Edward K. Ream wrote: > There might be a third way: some kind of client/server interaction > between Leo and pyzo/yoton. > > Yoton, pyzo's communication infrastructure, is worth learning and > playing with on its own. Communication between Leo and other programs > will

Re: discuss: Use markdown for Leo's documentation #1147

Hi, I agree on plain Markdown as a bad option for complex documentation, but almost nobody uses plain Markdown for that but some superset of CommonMark[1], as happens with Pandoc, which, BTW, has an Abstract Syntax Tree that enables high programmability an personalization[2] from several  programm

Re: Joe, is there any way to embed LeoVue's page in Leo's home page?

Hi, I wonder if there is a way to put the Leo File which generates the docs as a LeoVue outline directly. I think this could be a good showcase of what is possible by combining both in terms of a solid and fluent way to write and publish technical documentation (would search work in that case?

Re: Pyzo questions

On 22/04/19 6:43 p. m., Edward K. Ream wrote: On Mon, Apr 22, 2019 at 2:29 PM Rob > wrote: I have followed with some interest (though little understanding) Edward's pyzo project and have some questions: * After a cursory review of the pyzo.org site

Re: Answering my inner critic

Hi, One of the nicest things of this list is seeing Edward's though process documented openly even with its errand and good paths, as all of us take them but no much track is left behind for other to follow. Thanks for this, Offray On 20/04/19 9:13 a. m., Edward K. Ream wrote: My inner cri

Re: Joe, is there any way to embed LeoVue's page in Leo's home page?

I really like it! Thanks a lot Joe. Cheers, Offray On 20/04/19 9:58 a. m., Joe Orr wrote: How's this look for a start: https://kaleguy.github.io/leosite-pilot/ repo at: https://github.com/kaleguy/leosite-pilot Joe On Tuesday, April 16, 2019 at 6:10:27 AM UTC-4, Edward K. Ream wrote:

Re: The Pharo Chronicles: A Pythonic Pharo? A Pharonic Python?

Ohh... Ok. My approach was made a Leo inspired outliner on Pharo, kind of the opposite, but we're still miles ahead. Cheers, Offray On 11/03/19 3:58 p. m., Jacob MacDonald wrote: That was a typo, I meant Smalltalk on Leo. On Mon, Mar 11, 2019 at 12:54 PM Offray Vladimir Luna Cár

Re: The Pharo Chronicles: A Pythonic Pharo? A Pharonic Python?

Hi Jacob, On 24/02/19 5:17 a. m., Jacob MacDonald wrote: Somewhat related, I discovered Leo and Pharo around the same time and dream of writing a Smalltalk on top of Pharo someday. That project's been on the back burner for a couple years now though :) Thanks for your interest in Pharo. Ju

Re: 2019: The year of playful prototypes

Hi, On 2/03/19 12:20 p. m., Chris George wrote: As a non-programmer who has spent some time trying to learn python using Leo, having a fully integrated iPython terminal inside the main interface would be a killer feature that would extend Leo's reach. The current terminal plugin still segfaults

Re: 2019: The year of playful prototypes

Nice to see this playful approach. Maybe in those explorations GraalVM should be put in the radar: https://www.graalvm.org/ Cheers, Offray On 2/03/19 11:03 a. m., Edward K. Ream wrote: Imo, Leo is at a solid, stable state.  Sure, it could be improved, but it doesn't need to be. My overall

Re: How Ed should be spending his time.

Hi, On 6/03/19 10:08 a. m., Edward K. Ream wrote: > Leo is the answer to just about every question because of its power and flexibility - I think it needs concrete applications of that power in real world areas (maybe not my real world areas but someones real world areas) in order for it to be

Re: Leo on Android!

Really cool... At some time I plan to test Leo running on my tablet. Cheers, Offray On 26/2/19 16:11, Luka wrote: > It is now possible to run Leo on Android! > > Software configuration: pydroid, pyqt5 and ministro 2. Pyqt5 was installed > from pydroid quick install, ministro 2 was requested th

Re: Pharo Chronicles: time for a break

On 26/2/19 12:28, Edward K. Ream wrote: > > > On Tue, Feb 26, 2019 at 10:07 AM Offray Vladimir Luna Cárdenas > mailto:off...@riseup.net>> wrote: > > Hi, > > An answer on a particular point. I hope to come back with a more > detailed response in a coup

Re: Pharo Chronicles: time for a break

Hi, An answer on a particular point. I hope to come back with a more detailed response in a couple of weeks. On 26/2/19 8:09, Edward K. Ream wrote: > Pharo is a good enough language, with advantages I have already > described. However, it is not clearly superior to Python in any > significant way

Re: The Pharo Chronicles: bugs in grafoscopio

Thanks for this bugs report. I will address them in first or second week of March, when dissertation is done. Sorry for the delay. Meanwhile the new directives to import Pharo code as Leo trees is a clever workaround to the bugs in Grafoscopio from a Leo perspective. I hope to make Grafoscopio an

Re: Best Python IDE's on Slant.co

Mattew Butterick has similar concern about Lisp flattery regarding its power and even touch another popularity index (based on GitHub this time and before Clojure), as you can see on [1]. I think that he makes a pretty good argument about Lisp as a non professional programmer who codes (like myself

Re: The Pharo Chronicles: First impressions

Hi, Again, quick answers... On 23/2/19 7:19, Edward K. Ream wrote: > > *The IDEs suffer from Alzheimer's > * > > 1. The Launcher has a "quit on launch" checkbox, but there seems to be > no way to remember what it should be on the next launch.  Certainly it > is not saved automatically.  Using the

  1   2   3   4   5   6   >