Re: First draft of announcement of leoAst.py project
This may be totally irrelevant, but Python is likely to get a new parser: https://www.python.org/dev/peps/pep-0617/ Kind regards, Brad On Tuesday, July 14, 2020 at 9:37:29 AM UTC-6, Edward K. Ream wrote: > > > > On Tue, Jul 14, 2020 at 10:22 AM Edward K. Ream > wrote: > >> The first draft is here >> <https://github.com/leo-editor/leo-editor/issues/1565#issuecomment-654904747>, >> >> in the second comment of #1565 >> <https://github.com/leo-editor/leo-editor/issues/1565>. Please read and >> comment. >> > > To clarify, please make your comments *here*, not in the issue itself. > > Edward > -- 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/b5d4816f-2294-423c-b2d2-8034cd49f147o%40googlegroups.com.
Re: New features in leoInteg
I am using the extension by Alessandro Fragnani. Kind regards, Brad On Thursday, July 9, 2020 at 2:00:58 PM UTC-6, Félix wrote: > > Thank for your update Brad, > > I see what you mean and am currently working on solutions on that matter: > https://github.com/boltex/leointeg/issues/72 > > I feel the need to point out that if your settings are set correctly, > leoInteg *will* start everything automatically if your current workspace > includes a .Leo file. (short of actually opening the Leo file itself, for > which the command has to be initiated by the user) > > 3 options are necessary for this. (in the "leo settings" webview) "start > server" and "connect to server" and optionally the 'python command' > launch string... This should leave you in the state where the 'open file' > button is shown in the Leo panel. > > The fact that you're using a 'Project Manager' extension may come and play > a role in the auto-activation of leoInteg as described above. Also, there > are more than one extension named exactly "Project Manager" so i'm > wondering which one you're using... (the one by Alessandro Fragnani or > the one by Michael Škrášek?) > > I'm working on adding more features to all this to support suggestions > that you, and Edward made. > > So far, a realistic and easy thing to implement that I can think of > (without too much thinking) is something like: ... it would be that Leo > files would have a context menu option available in the regular file > explorer to 'open with LeoInteg'. I dont think its possible to override the > fact that if you ask vscode to 'Open' a Leo file, that it would simply show > you the XML content as it would have done if clicked on a regular XML file. > but I could be wrong. > > That would be in the short term,. taking more time to explorer those > avenues would lead to even better integration in the long run I'm sure. > > And please, don't hesitate to popup with more detailed ideas ! Greatly > appreciated! > -- > Félix > > On Thursday, July 9, 2020 at 3:32:53 PM UTC-4, Brad wrote: >> >> Hello Félix, >> >> I appreciate your hard work on this project! >> >> My workflow in VSCode is normally as follows: >> >> - Store directories as projects using the Project Manager extension. >> Directories can contain a variety of file types (Python, Jupyter, >> markdown, Leo, ...) >> >> - Open a project and click on various files in the VSCode Explorer to >> open them in tabs and make edits. >> For Leo files, it would be nice if opening a Leo file from the Explorer >> would start all of the necessary 'machinery' (e.g., server) if it is not >> started already so that I can immediately see the outline and work on it. >> >> I suppose the idea is that, if someone has python and the leointeg >> extension installed, operating on leo outlines will take no more setup than >> editing a text file. If the procedure requires command line operations or >> creating special shortcuts, I am guessing that the uptake of the extension >> may be limited to 'experts'. >> >> Kind regards, >> Brad >> >> >> On Wednesday, July 8, 2020 at 3:14:42 PM UTC-6, Félix wrote: >>> >>> Hi Brad! >>> >>> Glad you like it! >>> >>> Knowing that other people understand and use what i'm doing is a great >>> motivator and a pleasant experience! So thank you for taking the time to >>> report your usage of leoInteg! >>> >>> Not knowing much about VSCode extensions, do you imagine that further >>>> down the road a user of VSCode will just be able to open a .leo file and >>>> have the various components start up so that manipulating Leo outlines >>>> will >>>> be seamless? >>>> >>> >>> Well for some, (I think Ar-jan made it work seamlessly under >>> conda/anaconda, see >>> https://github.com/boltex/leointeg/issues/10#issuecomment-654665776 ) >>> it feels 'seamless' if you've configured the python command line option to >>> start the server and connect automatically... I guess I could start the >>> leoInteg extension all the time even if there's no .leo file in the current >>> workspace... (there's many little details that could be fined tuned to >>> offer a more pleasant experience) >>> >>> But I guess actually it depends what you mean exactly by 'seamless' and >>> 'open a leo file'. >>> >>> And with that, I'm inviting you to describe what the user experience >>>
Re: New features in leoInteg
Hello Félix, I appreciate your hard work on this project! My workflow in VSCode is normally as follows: - Store directories as projects using the Project Manager extension. Directories can contain a variety of file types (Python, Jupyter, markdown, Leo, ...) - Open a project and click on various files in the VSCode Explorer to open them in tabs and make edits. For Leo files, it would be nice if opening a Leo file from the Explorer would start all of the necessary 'machinery' (e.g., server) if it is not started already so that I can immediately see the outline and work on it. I suppose the idea is that, if someone has python and the leointeg extension installed, operating on leo outlines will take no more setup than editing a text file. If the procedure requires command line operations or creating special shortcuts, I am guessing that the uptake of the extension may be limited to 'experts'. Kind regards, Brad On Wednesday, July 8, 2020 at 3:14:42 PM UTC-6, Félix wrote: > > Hi Brad! > > Glad you like it! > > Knowing that other people understand and use what i'm doing is a great > motivator and a pleasant experience! So thank you for taking the time to > report your usage of leoInteg! > > Not knowing much about VSCode extensions, do you imagine that further down >> the road a user of VSCode will just be able to open a .leo file and have >> the various components start up so that manipulating Leo outlines will be >> seamless? >> > > Well for some, (I think Ar-jan made it work seamlessly under > conda/anaconda, see > https://github.com/boltex/leointeg/issues/10#issuecomment-654665776 ) it > feels 'seamless' if you've configured the python command line option to > start the server and connect automatically... I guess I could start the > leoInteg extension all the time even if there's no .leo file in the current > workspace... (there's many little details that could be fined tuned to > offer a more pleasant experience) > > But I guess actually it depends what you mean exactly by 'seamless' and > 'open a leo file'. > > And with that, I'm inviting you to describe what the user experience would > be in your mind, the best or nicest way to more fully integrate the 'open a > leo file' and seamless concepts, in a detailed and precise way. > > People who take the time to describe very precisely how a feature could > (or should) be experienced and implemented sometimes make a project move > along faster than people who submit actual code! > > Thanks again and don't hesitate to address any issues at all :) > -- > Félix > > > > > On Wednesday, July 8, 2020 at 3:52:07 PM UTC-4, Brad wrote: >> >> Hello Félix, >> >> As a regular user of Leo and VSCode, this is awesome! >> >> Following Matt Wilkie's great step-by-step account of how to get things >> going under Anaconda Python, I edited some leo outlines and was very >> impressed by the potential of this project. >> >> Not knowing much about VSCode extensions, do you imagine that further >> down the road a user of VSCode will just be able to open a .leo file and >> have the various components start up so that manipulating Leo outlines will >> be seamless? >> >> Thanks again. >> >> Kind regards, >> Brad >> >> >> On Wednesday, July 8, 2020 at 12:54:46 PM UTC-6, Félix wrote: >>> >>> Here's a quick list of most of the new features now on the "dev" branch. >>> Going to make little touch-ups and cleanup before merging to master. >>> >>> *New option setting : Use Leo Tree Browsing. (find better name!)* >>> >>> *New option setting : Show/hide 'edit headline' hover icon. (allowing to >>> remove all icons lets the user go directly from the tree to the body pane >>> with a single 'tab' hit on the keyboard.* >>> >>> *New Visual Helper: when changing option-settings, a new popup will >>> appear indicating the options have been changed but are still pending >>> 'saving' in the user's settings file. 1.5 Seconds later the 'Auto-saved' >>> message should appear as usual. (Some users were closing / changing tabs >>> too fast after changing settings and not realizing they had not waited long >>> enough for the 'auto-save' to kick in.)* >>> >>> *After changing the option-settings, if any changes involved the >>> hover-icons, the tree will refresh (debounced / timeout of 200ms) to >>> reflect the changes.* >>> >>> *The "currently selected node" attributes are now watched by leoInteg in >>> order to strictly show and allow relevant commands and icons only.
Re: New features in leoInteg
Hello Félix,
As a regular user of Leo and VSCode, this is awesome!
Following Matt Wilkie's great step-by-step account of how to get things
going under Anaconda Python, I edited some leo outlines and was very
impressed by the potential of this project.
Not knowing much about VSCode extensions, do you imagine that further down
the road a user of VSCode will just be able to open a .leo file and have
the various components start up so that manipulating Leo outlines will be
seamless?
Thanks again.
Kind regards,
Brad
On Wednesday, July 8, 2020 at 12:54:46 PM UTC-6, Félix wrote:
>
> Here's a quick list of most of the new features now on the "dev" branch.
> Going to make little touch-ups and cleanup before merging to master.
>
> *New option setting : Use Leo Tree Browsing. (find better name!)*
>
> *New option setting : Show/hide 'edit headline' hover icon. (allowing to
> remove all icons lets the user go directly from the tree to the body pane
> with a single 'tab' hit on the keyboard.*
>
> *New Visual Helper: when changing option-settings, a new popup will appear
> indicating the options have been changed but are still pending 'saving' in
> the user's settings file. 1.5 Seconds later the 'Auto-saved' message should
> appear as usual. (Some users were closing / changing tabs too fast after
> changing settings and not realizing they had not waited long enough for the
> 'auto-save' to kick in.)*
>
> *After changing the option-settings, if any changes involved the
> hover-icons, the tree will refresh (debounced / timeout of 200ms) to
> reflect the changes.*
>
> *The "currently selected node" attributes are now watched by leoInteg in
> order to strictly show and allow relevant commands and icons only. (in
> command palette and on the top title bar of outline views)*
>
> *Outline tree nodes also have more properties to allow stricter set of
> commands to be offered in via the right-click context menu
> ("goto-next-clone" only shown on cloned nodes, "refresh from file" only
> shown on '@clean/@files etc...)*
>
> *Hoist and dehoist commands have been implemented for the currently
> selected node *and* also for any visible node in the outline tree via
> right-click context menu. De-hoist command is accessible as an icon in the
> tree top title bar, as a regular command, and as a context-menu entry on
> the single topmost ode of a hoisted tree.*
>
> *Keyboard editing improvements: Commands try to bring focus back into the
> right pane after execution to improve the keyboard editing experience and
> fluency.*
>
> *Keyboard editing improvements: CTRL-T and Tab shortcuts that match Leo's
> behavior to switch active panel*
>
> *"Direct" keyboard navigation in the outline tree: Move the selected tree
> node and body pane with single arrow keys, as in Leo. Replaces vscode's
> usual tree navigation system. Optionally toggled on/off as an option
> setting.*
>
> *New keyboard shortcuts: *
> *gotoFirstVisible : alt+home,*
> *gotoLastSibling : alt+end,*
> *gotoNextClone : alt+n,*
> *sortSiblings : alt+a,*
> *showOutline : alt+t,*
> *Toggle outline/body focus : ctrl+t,*
> *Focus Body : alt+d,*
> *Focus body (from tree) : tab",*
> *Alt+Arrow keys: Direct Tree Navigation.*
> *Arrow Keys: (with 'Leo-tree-browse' option) Direct Tree navigation*
>
> As usual, please report anything that comes to mind while using this so I
> can make adjustments :)
>
> Thanks for trying this stuff out you guys!
> --
> Félix
>
>
>
> On Wednesday, July 8, 2020 at 11:47:45 AM UTC-4, Edward K. Ream wrote:
>>
>>
>>
>> On Wed, Jul 8, 2020 at 9:29 AM Félix wrote:
>>
>>> Note to self: Test under windows just before pushing after adding
>>> features!
>>>
>>> Turns out vscode commands are case-insensitive under linux! Which leads
>>> to compile errors when trying to run under windows with erroneous case
>>> inconsistencies!
>>>
>>> Thanks for trying, and sorry for this rookie mistake! All fixed under
>>> the dev branch now!
>>>
>>
>> Everything looks good now.
>>
>> Edward
>>
>
--
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/5665598d-5441-4162-97ac-1f7bff385d7ao%40googlegroups.com.
Re: Reproducible computational science
Hello Offray, Thank you for the insights! I will check out the resources you described. Kind regards, Brad On Monday, April 13, 2020 at 4:18:53 PM UTC-6, Offray Vladimir Luna Cárdenas wrote: > > 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 interactive > outlining, called Grafoscopio[2], using the Pharo live > coding/programming/computing environment [3] > > I think, as you, that there is a lot of potential for such interactive > outlining, for complex reproducible research documents, and you can see > something like that in the Org Mode world using Babel [4][4a]. I did my own > prototype about Panama Papers as reproducible research, as you can see in > [5], using pretty non-complicated tech stack (described there). > > Regarding reproducibility in a time frame of decades, you can make this > already with a Smalltalk, thanks to the image concept (which is there from > 70's). You can froze the state of execution of your object in the image and > reopen them a decade later, as I did with the simulation I made for my > Masters. It was as I left it in my master presentation a decade ago see > [6]. I propose to use Pharo/Smalltalk in tandem with functional package > managers (Guix/Nix alike), so you can have a pretty reproducible > environment and be more agile that Jupyter/Python community without the > baggage of incidental complexity. > > Cheers, > > Offray > > > [1] > http://mutabit.com/offray/static/blog/output/posts/grafoscopio-idea-and-initial-progress.html > [2] https://mutabit.com/grafoscopio/en.html > [3] https://pharo.org/ > [4] https://www.youtube.com/watch?v=dljNabciEGg=youtu.be > [4a] https://www.youtube.com/watch?v=GK3fij-D1G8 > [5] https://mutabit.com/offray/blog/en/entry/panama-papers-1 > [6] https://twitter.com/offrayLC/status/927313455543091200 > On 8/04/20 2:46 p. m., Brad wrote: > > I use Jupyter notebooks for a lot of my analyses. > Though I realize a lot more is possible, my personal preference is not to > use this platform beyond exploratory analyses where one can embed > relatively short snippets of code into the notebook. > > I know that one could zip a directory with Jupyter notebooks and data to > satisfy some of my requirements, but it seemed to me that with Leo's very > versatile structure, and the capability to naturally incorporate meta data > in a structured manner, might offer some advantages. > > Per Marcel's perceptive comments, I understand that Leo has only a > fraction of the users of Jupyter notebooks. However, that doesn't mean that > Jupyter notebooks are more capable for this task. > > This a hard problem and I was just suggesting that an 'out of the box' > solution using something like Leo might be worth considering. > > Kind regards, > Brad > > > > On Tuesday, April 7, 2020 at 6:14:14 PM UTC-6, Thomas Passin wrote: >> >> It's interesting to me, anyway. Could you talk about why you haven't >> found Jupyter notebooks to be satisfactory? On other threads we have been >> discussing whether Leo, with the Viewrendered3 plugin, might be able to do >> much of what Jupyter does, and have some advantages besides. Your question >> seems to fit right in. >> >> On Tuesday, April 7, 2020 at 3:57:27 PM UTC-4, Brad wrote: >>> >>> Hello All, >>> >>> As I see it, one of the more important trends in computational sciences >>> is reproducibility. I have tried out a number of platforms that attempt to >>> enable reproducibility and capture the provenance necessary to faithfully >>> recapitulate computational analyses; however, I found them burdensome in >>> terms of the imposed workflows. >>> >>> I wonder if Leo could be a compelling platform for this use case. >>> >>> Is anyone else interested in this use case? >>> >>> >>> -- > 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-e...@googlegroups.com . > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/73dc42a5-f61d-4a44-81b9-b51861f3d876%40googlegroups.com > > <https://groups.google.com/d/msgid/leo-editor/73dc42a5-f61d-4a44-81b9-b51861f3d876%40googlegroups.com?utm_medium=email_source=footer> > . > > -- 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/1d62cbfa-910c-4aea-8b1d-6b894d3b08a2%40googlegroups.com.
Re: Reproducible computational science
I use Jupyter notebooks for a lot of my analyses. Though I realize a lot more is possible, my personal preference is not to use this platform beyond exploratory analyses where one can embed relatively short snippets of code into the notebook. I know that one could zip a directory with Jupyter notebooks and data to satisfy some of my requirements, but it seemed to me that with Leo's very versatile structure, and the capability to naturally incorporate meta data in a structured manner, might offer some advantages. Per Marcel's perceptive comments, I understand that Leo has only a fraction of the users of Jupyter notebooks. However, that doesn't mean that Jupyter notebooks are more capable for this task. This a hard problem and I was just suggesting that an 'out of the box' solution using something like Leo might be worth considering. Kind regards, Brad On Tuesday, April 7, 2020 at 6:14:14 PM UTC-6, Thomas Passin wrote: > > It's interesting to me, anyway. Could you talk about why you haven't > found Jupyter notebooks to be satisfactory? On other threads we have been > discussing whether Leo, with the Viewrendered3 plugin, might be able to do > much of what Jupyter does, and have some advantages besides. Your question > seems to fit right in. > > On Tuesday, April 7, 2020 at 3:57:27 PM UTC-4, Brad wrote: >> >> Hello All, >> >> As I see it, one of the more important trends in computational sciences >> is reproducibility. I have tried out a number of platforms that attempt to >> enable reproducibility and capture the provenance necessary to faithfully >> recapitulate computational analyses; however, I found them burdensome in >> terms of the imposed workflows. >> >> I wonder if Leo could be a compelling platform for this use case. >> >> Is anyone else interested in this use case? >> >> >> -- 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/73dc42a5-f61d-4a44-81b9-b51861f3d876%40googlegroups.com.
Reproducible computational science
Hello All, As I see it, one of the more important trends in computational sciences is reproducibility. I have tried out a number of platforms that attempt to enable reproducibility and capture the provenance necessary to faithfully recapitulate computational analyses; however, I found them burdensome in terms of the imposed workflows. I wonder if Leo could be a compelling platform for this use case. The idea would be to have a sharable Leo file of a given format that would include enough information (exact code, data, specifics of the platform and libraries, etc.) such that the 'sharee' could exactly re-create the results of the 'sharer'. It seems that Leo is a rich enough platform that a 'schema' could be created to facilitate this kind of sharing. Is anyone else interested in this use case? Kind regards, Brad -- 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/7494538a-f530-48d7-aff0-dabe9763d87e%40googlegroups.com.
Re: Discuss: a proposed answer to python issue #33337
Edward, This is very interesting work. As you probably know, the Python core developers are a bit curmudgeonly when it comes to suggestions that haven't come from themselves. Be aware that the responses could focus exclusively on all of the potential problems, with the inevitable: "Why don't you put this on PyPI first and see how it is received?" -Brad On Wednesday, January 15, 2020 at 12:42:31 AM UTC-7, Edward K. Ream wrote: > > On Tue, Jan 14, 2020 at 8:00 PM Matt Wilkie > wrote: > > > you've worked incredibly hard to this point, and it must be really > exciting/enticing to be near a point of release and of shouting "hear ye, > hear ye" loud enough to attract attention, but don't make noise just yet! > > I agree that more work is needed. > > At the very least I think leoAst needs to be run on it's own (e.g. not >> rely on `import leo ...`), and then have a concrete quick start example or >> two like Terry and Btheado mentioned. >> > > A quick-start example is a good idea. The first that comes to mind is the > code that would fstringify a file. leoBeautify.py contains three fstringify > commands that could be reworked. However, those commands do "too much" in > some sense. > > The challenge is to create a motivating example, which can be solved with > only a few lines of code. That's a big ask, because I imagine anything > useful might run to a few pages of code > > I think the Python devs (and everyone else) need to be told in more detail > why the tool is useful. That involves a discussion of what "unify the token > and ast worlds" means, and why it would be useful. That's what I'll discuss > in an upcoming post. > > Edward > -- 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/69f49c9f-0058-4ef9-93f7-91c80abcf81e%40googlegroups.com.
Re: Leo in 2019
TheBrain looks very interesting, but to get the file attachment feature requires purchase of a Pro License, which is currently $219 and does not include upgrades or the cloud service. This may be a small cost relative to the gain in productivity, but being at the mercy of a vendor who can change pricing and license terms at will may be off-putting for some people. -Brad On Thursday, January 3, 2019 at 9:32:26 PM UTC-7, rengel wrote: > > On Friday, January 4, 2019 at 2:49:44 AM UTC+1, Joe Orr wrote: >> >> Hmm... yet another mind mapper. Not impressed. >> >> I don't need another hairball to deal with. Leo forces me to put things >> in order, but allows multiple orders. >> >> Ignore to your own detriment! > > I've been using outliners as PIMs ever since Dave Winer invented ThinkTank > <http://outliners.scripting.com/thinkTank2Pc.html> at the beginning of > the 80s, in between More, Agenda, Ecco, Freemind, MindMapper, and others, > and then TheBrain for more than a decade now. As a PIM, nothing comes close > to TheBrain. TheBrain has been used by Britannica and the World Economic > Forum. > > Try to manage 500,000+ items (nodes/thoughts) plus 45 GigaBytes so called > attachments (notes, images, links, tables, movies, PDF files, EXE files, > etc.), capture links, screenshots, texts, folders of your file system by > drag, access local files, your network, or the Internet with just one > click, rearrange, regroup any number of items visually and ad hoc, retrieve > everything almost instantaneously. Try all this using Leo or 'yet another > mind mapper'. Edward made a sound assessment: Leo has its place, but not as > a superior PIM. > > It's the scaleability and ease of use that sets TheBrain apart. > Having clones when you use an outline is nice. Not having the need for > clones is better when you can link any item to any number of parents. > TheBrains's structure is not a DAG where every node has but one parent but > a network, where any node can have any number of parent, child, and > 'sideways' links and even circular connections. > > There's a large public brain of a long time TheBrain user: Jerry's Brain > <https://www.jerrysbrain.com/>, that's often used to showcase TheBrain. > Try to do something like this using Leo. > > Cheers, and happy new year! > > Reinhard > > > (Disclaimer: I'm not connected to TheBrain company in any way.) > > > -- 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 post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Programming language support via the language server protocol
Hi, I wonder if adopting and implementing the 'language server protocol' would be of benefit to Leo. Details are given here: http://langserver.org/ -Brad -- 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 post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Leo *for* web apps vs. Leo *as* a web app
I understand. My thinking was that if you decide to move ahead, the IPython (and more generally Jupyter) developers have gone through the careful process (and pain) of designing an integrated, extensible system (tornado, zmq, json, javascript) that may be of use in a more general context. This might give the project a head start instead of having to discover a workable system based on lower-level components. On Wednesday, January 14, 2015 at 8:50:10 AM UTC-7, Edward K. Ream wrote: On Wed, Jan 14, 2015 at 7:43 AM, Brad brad.r...@gmail.com javascript: wrote: Can any of the lessons learned and infrastructure from the IPython notebook and project Jupyter (https://jupyter.org/ - private https://jupyter.org/) be of use? Excellent question. I hadn't known about jupyter until just now, but it's derived from IPython so let's pretend for the moment that similar remarks apply to both. I've thought about this question recently. Here are my present thoughts. IPython is quite different from Leo. The IPython notebook can and does write .nb files in a private format. Yes, .nb files can be shared, but the goal of notebooks isn't to create files but to use IPython. The collaboration model for IPython and Leo are different. Presumably, one would not use git on .nb files, though I suppose one could. In short, studying IPython's code would be useful *if* we knew we wanted wLeo, but the success of IPython's notebook does not mean that wLeo is useful. Edward -- 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 post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Leo *for* web apps vs. Leo *as* a web app
Can any of the lessons learned and infrastructure from the IPython notebook and project Jupyter (https://jupyter.org/) be of use? -Brad On Wednesday, January 14, 2015 at 5:31:38 AM UTC-7, Edward K. Ream wrote: I suspect that I shall be studying web technologies this year. They are way too important to ignore any longer. Besides, they are interesting technologies. Let me state a preliminary conclusion, which may not last more than a few hours: Leo has no real future *as* a web app, call it **wLeo**, unless one or more of the following becomes a web app: git, vim, emacs or eclipse. This follows the first things first principle: we want to make sure that wLeo would actually be useful. Web apps are connected to severs that (surprise) actually serve up content (from data bases or news feeds or something else). But what would wLeo serve up? Well, a .leo file, presumably on a *local* machine. That being so, we might as well use Leo on that local file. Just like vim and emacs do. Yes, we could imagine a collaborative Leo working on shared .leo files, but that seems pretty much a fantasy. Otoh, it is conceivable that Leo could be a killer app for *creating* web apps. Indeed, my brother Speed has done some interesting work in that direction. He calls his work leopard: the last two letters stand for response daemon. You might say that the mod_http plugin could be used as a prototyping engine for creating web apps. I started studying mod_http yesterday. This lead me to pages such as: https://docs.python.org/2/howto/sockets.html - private https://docs.python.org/2/howto/sockets.html https://parijatmishra.wordpress.com/2008/01/04/writing-a-server-with-pythons-asyncore-module/ - private https://parijatmishra.wordpress.com/2008/01/04/writing-a-server-with-pythons-asyncore-module/ http://code.activestate.com/recipes/259148/ - private http://code.activestate.com/recipes/259148/ https://docs.python.org/2/library/asyncore.html - private https://docs.python.org/2/library/asyncore.html https://docs.python.org/2/library/simplehttpserver.html - private https://docs.python.org/2/library/simplehttpserver.html https://docs.python.org/2/library/basehttpserver.html#BaseHTTPServer.BaseHTTPRequestHandler - private https://docs.python.org/2/library/basehttpserver.html#BaseHTTPServer.BaseHTTPRequestHandler and https://docs.python.org/3/library/asyncio.html - private https://docs.python.org/3/library/asyncio.html Here is a vid about the Tulip library that morphed into asyncio https://www.youtube.com/watch?v=aurOB4qYuFM - private https://www.youtube.com/watch?v=aurOB4qYuFM Whew! Your comments please. Edward P.S. mod_http needs some refactoring. I plan to create a new plugin to play with so as not to disturb mod_http in the interim. EKR -- 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 post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
