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
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
Oh, I didn't understand that the question was whether or
not to abandon 2, that wouldn't be good.
I'd welcome help from someone running Leo trunk in a virtualenv
with Py3 and PyQt5
On Wed, Jan 14, 2015 at 9:26 AM, Edward K. Ream edream...@gmail.com wrote:
On Tue, Jan 13, 2015 at 10:06 AM, Kent
On Wed, Jan 14, 2015 at 7:35 AM, Jacob Peck gatesph...@gmail.com wrote:
wLeo could access .leo files in a variety of spaces:
- Local files
- github repos
- elsewhere in 'the cloud' (DropBox? SpiderOak?)
- stored on a private server
True. The question is, would wLeo be an
On 1/14/2015 10:55 AM, Edward K. Ream wrote:
Writing to a local device involves having a server running on that
device.
Nope -- HTML5 brought support for localstorage and the FileSystem API.
Web apps can write persistent files to client devices.
Is there any impediment to using Leo with files that are in the local
DropBox folder?
Not that I know of. I just created @file
path-to-dropbox\Dropbox\test.py
and saved it. Changed test.py in the Dropbox folder. The changes appear
when I reloaded the .leo file containing the @file node.
In the browser would also benefit the outreach issue:
http://leo-editor.com/demo ...
On Wed, Jan 14, 2015 at 9:58 AM, Jacob Peck gatesph...@gmail.com wrote:
On 1/14/2015 10:55 AM, Edward K. Ream wrote:
Writing to a local device involves having a server running on that device.
Nope -- HTML5
On 1/14/2015 10:38 AM, Edward K. Ream wrote:
The question is, would wLeo be an improvement over plain Leo. At
present, I do not see how. For example, plain Leo will have *much*
better drawing and file-related performance than wLeo
. And if wLeo is merely going to deal with local files
On Wed, Jan 14, 2015 at 7:43 AM, Brad brad.reisf...@gmail.com wrote:
Can any of the lessons learned and infrastructure from the IPython
notebook and project Jupyter (https://jupyter.org/) be of use?
Excellent question.
I hadn't known about jupyter until just now, but it's derived from
On Wed, Jan 14, 2015 at 9:43 AM, Jacob Peck gatesph...@gmail.com wrote:
On 1/14/2015 10:38 AM, Edward K. Ream wrote:
The cross-platform support is the key here. Being able to run it on *any*
device with a modern web browser is crazy useful. Leo on my tablet, Leo on
my phone, Leo on my
On Wed, 14 Jan 2015 08:35:00 -0500
Jacob Peck gatesph...@gmail.com wrote:
- elsewhere in 'the cloud' (DropBox? SpiderOak?)
Is there any impediment to using Leo with files that are in the local
DropBox folder? Hmm, I have DropBox synced. on my phone, but the
Android outliner DGT GTD links
On 1/14/2015 11:28 AM, Edward K. Ream wrote:
Is there any impediment to using Leo with files that are in the local
DropBox folder?
Not that I know of. I just created @file
path-to-dropbox\Dropbox\test.py
and saved it. Changed test.py in the Dropbox folder. The changes
appear
On Wed, Jan 14, 2015 at 9:40 AM, Kent Tenney kten...@gmail.com wrote:
Oh, I didn't understand that the question was whether or
not to abandon 2, that wouldn't be good.
The question is merely whether to encourage Leo's core developers to use
Python 3 when writing (and checking!) their code.
On Wed, Jan 14, 2015 at 9:58 AM, Jacob Peck gatesph...@gmail.com wrote:
On 1/14/2015 10:55 AM, Edward K. Ream wrote:
Writing to a local device involves having a server running on that
device.
Nope -- HTML5 brought support for localstorage and the FileSystem API.
Web apps can write
On 1/14/2015 7:31 AM, Edward K. Ream wrote:
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
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
This should be documented somewhere. This post will be prewriting for such
docs.
Recently I realized that Leo must insert sentinels into external files even
if the user never uses clones. Indeed, sentinels create **identity**, the
notion that a particular nodes starts at *this* place in the
FWIW, I'm pretty pessimistic about Python 3 at this point. Python 2 seems
to be good enough for most people.
On Tue, Jan 13, 2015 at 6:06 PM, Kent Tenney kten...@gmail.com wrote:
I recently tried to switch to v3, as I remember, I was thwarted
by problems having to do with PyQT in a virtualenv.
18 matches
Mail list logo
