On Thu, Jan 29, 2015 at 9:33 AM, Ville M. Vainio wrote:
> Leo already works with ipython, but I'm aware we are talking about ipython
> notebook here ;).
>
> I think I did an experiment on this back in the day - it would involve
> launching "ipython kernel" (that hosts all the data, and that is us
Leo already works with ipython, but I'm aware we are talking about ipython
notebook here ;).
I think I did an experiment on this back in the day - it would involve
launching "ipython kernel" (that hosts all the data, and that is used as a
backend for the web frontend) in the Leo process. This woul
> The biggest win-win that I can see would be to "insinuate" Leo somehow
> into IPython.
>
Count me for one that would love this!
Matt
--
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
On Wed, Jan 14, 2015 at 5:35 AM, Jacob Peck wrote:
> This means that *one single codebase* will run on Windows, Linux, Mac OS
> X, Android, iOS, Blackberry OS, Windows Phone, Tizen, Mozilla/Firefox OS,
> etc, with no complicated user installation.
dunno if it's relevant here, but Docker is on
On Wed, Jan 14, 2015 at 1:33 PM, Brad wrote:
> 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, javascri
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
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 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 supp
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
\Dropbox\test.py
and saved it. Changed test.py in the Dropbox folder. The changes
appear when I reloaded
> 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
\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.
Edward
--
On Wed, 14 Jan 2015 08:35:00 -0500
Jacob Peck 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 directly to my DropBo
On Wed, Jan 14, 2015 at 9:58 AM, Jacob Peck 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 persistent files
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.
http://www.noupe.com/design/html5-filesystem-ap
On Wed, Jan 14, 2015 at 9:43 AM, Jacob Peck 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 thermostat! A b
On Wed, Jan 14, 2015 at 7:43 AM, Brad 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
IPython so let's preten
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 the
On Wed, Jan 14, 2015 at 7:35 AM, Jacob Peck 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 improvement over p
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 to
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 **wL
19 matches
Mail list logo
