RE: PyOhio Talk
8 views
Skip to first unread message
Ville Vainio
May 24, 2012, 6:53:53 AM5/24/12
to tfer, leo-e...@googlegroups.com
Quick comment: Leo is an outliner that is often used as an ide
Sent from my Windows Phone
Sent from my Windows Phone
From: tfer
Sent: 5/24/2012 2:29 AM
To: leo-e...@googlegroups.com
Subject: PyOhio Talk
I'm titling the talk: Leo: a paradigm shifting IDE
The description (400 character limit) of which I'm giving as:
Leo is an open source IDE coded in python, using PyQt. It can be used as a general project manager, handling all the files in your project, no matter what language(s), you are writing in. The shift that Leo gives you is that can organize your projects formally below the file level, which previously could only be done informally with section comments. Using outlines supports thinking & organizing.
Proposal deadline is June 1st, it can be edited until then.
I need to do a talk abstract.
Talks are 40 minutes.
Suggestions for material and wording can be discussed here.
Tom
--
You received this message because you are subscribed to the Google Groups "leo-editor" group.
To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/mnSENgwSoF4J.
To post to this group, send email to leo-e...@googlegroups.com.
To unsubscribe from this group, send email to leo-editor+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
tfer
May 24, 2012, 10:53:27 AM5/24/12
to leo-e...@googlegroups.com, tfer
Good, changed to:
Leo is a pure python, open source outliner, often used as an IDE. As a project manager, it handles all your files, no matter what language(s) you're using. Uniquely, it lets you to organize your projects below the file level, (elsewhere only doable informally with section comments). Using outlines supports thinking & organizing, allowing big/little picture focus shifts. Its great for code study.
Leo is a pure python, open source outliner, often used as an IDE. As a project manager, it handles all your files, no matter what language(s) you're using. Uniquely, it lets you to organize your projects below the file level, (elsewhere only doable informally with section comments). Using outlines supports thinking & organizing, allowing big/little picture focus shifts. Its great for code study.
To unsubscribe from this group, send email to leo-editor+unsubscribe@googlegroups.com.
Ville Vainio
May 24, 2012, 5:13:18 PM5/24/12
to tfer, leo-e...@googlegroups.com
Idea: quick start.leo is probably handy demo material, as it illustrates most of the core concepts
Sent from my Windows Phone
I'm putting together a proposal for a talk on Leo at the PyOhio conference in Columbus, July 28th & 29th. If accepted, it should give us an introductory video as these talks are normally taped.
I'm titling the talk: Leo: a paradigm shifting IDE
The description (400 character limit) of which I'm giving as:
Leo is an open source IDE coded in python, using PyQt. It can be used as a general project manager, handling all the files in your project, no matter what language(s), you are writing in. The shift that Leo gives you is that can organize your projects formally below the file level, which previously could only be done informally with section comments. Using outlines supports thinking & organizing.
Proposal deadline is June 1st, it can be edited until then.
I need to do a talk abstract.
Talks are 40 minutes.
Suggestions for material and wording can be discussed here.
Tom
--
You received this message because you are subscribed to the Google Groups "leo-editor" group.
To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/mnSENgwSoF4J.
To post to this group, send email to leo-e...@googlegroups.com.
To unsubscribe from this group, send email to leo-editor+...@googlegroups.com.I'm titling the talk: Leo: a paradigm shifting IDE
The description (400 character limit) of which I'm giving as:
Leo is an open source IDE coded in python, using PyQt. It can be used as a general project manager, handling all the files in your project, no matter what language(s), you are writing in. The shift that Leo gives you is that can organize your projects formally below the file level, which previously could only be done informally with section comments. Using outlines supports thinking & organizing.
Proposal deadline is June 1st, it can be edited until then.
I need to do a talk abstract.
Talks are 40 minutes.
Suggestions for material and wording can be discussed here.
Tom
--
You received this message because you are subscribed to the Google Groups "leo-editor" group.
To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/mnSENgwSoF4J.
To post to this group, send email to leo-e...@googlegroups.com.
Ville Vainio
May 27, 2012, 9:24:33 AM5/27/12
to Edward K. Ream, leo-editor
Fwiw, I find the 'template' word below a bit alien...
Remember 'Making it stick'? It's always better to be concrete and
direct, to the extent of talking about @others and sections
Sent from my Windows Phone
From: Edward K. Ream
Sent: 5/27/2012 1:49 PM
To: leo-editor
Subject: Re: PyOhio Talk
On May 26, 4:27 am, "Edward K. Ream" <edream...@gmail.com> wrote:
> I like your use of the term "template". It's evocative, and allows you to avoid details about @others and sections.
The term "template" is brilliant. Rather than saying something overly
general, as I have been saying for years, "in Leo, outlines are
significant everywhere", the term allows us to say something like:
"In Leo, templates are aware of outline structure and, thanks to Leo's
DOM, Leo scripts are aware of the outline in which they are embedded."
External files created by Leo are *not* aware of outline structure,
unless they use the leoBridge module. Thus the distinction between
Leo scripts (including plugins) and external files becomes sharper:
the former are aware of outline structure, the latter are not.
Here, the template language consists of @others, sections and section
references, and Leo directives. All three "understand" outline
structure, and are defined in terms of outline structure. Also, the
term "outline structure" really refers to *graph* (DAG) structure.
It may be too late to change your abstract, but I hope this helps
organize your talk. It has certainly clarified my thinking.
Edward
--
You received this message because you are subscribed to the Google
Groups "leo-editor" group.
Remember 'Making it stick'? It's always better to be concrete and
direct, to the extent of talking about @others and sections
Sent from my Windows Phone
Sent: 5/27/2012 1:49 PM
To: leo-editor
Subject: Re: PyOhio Talk
On May 26, 4:27 am, "Edward K. Ream" <edream...@gmail.com> wrote:
> I like your use of the term "template". It's evocative, and allows you to avoid details about @others and sections.
The term "template" is brilliant. Rather than saying something overly
general, as I have been saying for years, "in Leo, outlines are
significant everywhere", the term allows us to say something like:
"In Leo, templates are aware of outline structure and, thanks to Leo's
DOM, Leo scripts are aware of the outline in which they are embedded."
External files created by Leo are *not* aware of outline structure,
unless they use the leoBridge module. Thus the distinction between
Leo scripts (including plugins) and external files becomes sharper:
the former are aware of outline structure, the latter are not.
Here, the template language consists of @others, sections and section
references, and Leo directives. All three "understand" outline
structure, and are defined in terms of outline structure. Also, the
term "outline structure" really refers to *graph* (DAG) structure.
It may be too late to change your abstract, but I hope this helps
organize your talk. It has certainly clarified my thinking.
Edward
--
You received this message because you are subscribed to the Google
Groups "leo-editor" group.
Reply all
Reply to author
Forward
0 new messages