On Sat, Oct 28, 2017 at 1:07 PM, Terry Brown wrote:
> On Fri, 27 Oct 2017 08:54:27 -0500
> "Edward K. Ream" wrote:
>
> > On Tue, Oct 24, 2017 at 10:33 AM, Edward K. Ream
> > wrote:
> >
> > > > I'll run my typical tests in the branch and let you know soon.
> > >
> > > Here are some minor pro
On Fri, Oct 27, 2017 at 2:35 PM, Jose Gonzalez wrote:
> I think it's also about building on Jupyter concepts as reproducible
> literate programming platform, not just cloning its current functionality
>
I agree. Imo, a complete script is the ultimate in "reproducible".
Fragments, as in Jupyter,
Imo, Google's projects pages are poor. There is insufficient organization
and formatting features.
Instead, let's use Leo's existing issues page for branch notes and for
project notes. If necessary, we can split existing issues into as many
sub-issues as necessary. The great advantage of using
On Sun, 29 Oct 2017 05:07:27 -0500
"Edward K. Ream" wrote:
> Work for me. Could you add an "about" or "help" item, say in the
> "More" dropdown, explaining as clearly as possible what this pane is
> supposed to demonstrate, and what your plans are for it?
Not sure about / help is really the pl
How best to track issues for arge sub-projects like leo_edit_pane?
I'd like to drop of lot of LEP related issues into the Leo issue
tracker, but could understand if there was resistance to that, so:
My preferred option - put them in the regular issue tracker with label
'lep', then anyone who wis
On Sun, 29 Oct 2017 12:59:17 -0700 (PDT)
"Edward K. Ream" wrote:
> Imo, Google's projects pages are poor. There is insufficient
> organization and formatting features.
>
> Instead, let's use Leo's existing issues page for branch notes and
> for project notes. If necessary, we can split existing
I'm doing something similar with Grafoscopio. I keep a "Dev's
notebook"[1] with a Kanban[2] like subtree to organize development. You
can get the last version of all documents inside Grafoscopio. So yes, I
think that using Leo to organize and document Leo development can be
pretty superior to use j
On Sun, 29 Oct 2017 16:06:13 -0500
Offray Vladimir Luna Cárdenas wrote:
> I'm doing something similar with Grafoscopio. I keep a "Dev's
> notebook"[1] with a Kanban[2] like subtree to organize development.
> You can get the last version of all documents inside Grafoscopio. So
> yes, I think that
On 26/10/17 05:45, Edward K. Ream wrote:
> On Wed, Oct 25, 2017 at 12:06 PM, Offray Vladimir Luna Cárdenas
> mailto:off...@riseup.net>> wrote:
>
>
> I have updated #561 to clarify the rationale behind this proposal and
> include some links.
>
>
> Thanks for this. The link to the Jupyter
On 29/10/17 16:13, Terry Brown wrote:
> On Sun, 29 Oct 2017 16:06:13 -0500
> Offray Vladimir Luna Cárdenas wrote:
>
>> I'm doing something similar with Grafoscopio. I keep a "Dev's
>> notebook"[1] with a Kanban[2] like subtree to organize development.
>> You can get the last version of all docume
Hi,
On 27/10/17 14:35, Jose Gonzalez wrote:
> I think it's also about building on Jupyter concepts as reproducible
> literate programming platform, not just cloning its current functionality
>
> See it as an alternative to the JupyterLab application
> (https://channel9.msdn.com/Events/PyData/Seat
Reading your responses I noticed my own mistake:
> - Separate code from outputs. One of the main strengths for Leo,
combining code and results into the same document, is also one of its main
limitations.
I meant " One of the main strengths for **Jupyter**, combining code and
results into the
12 matches
Mail list logo
