Hello Everyone, I wish to rephrase a comment I just made on PyPE. Actually, just after writing my previous mail, I came back to PyPE (by Josiah Carlson) to revisit it and have a fairer opinion: 1. PyPE is Python meant for Python (and the usual crew of C, text, TeX, HTML, XML) while Notepad++ can highlight dozens of languages. 2. PyPE is an editor but is also closer to an IDE So I decided to give it a new try. My concern however seems to be the lack of visibility of PyPE. I've noticed a few bucks - that's ok - but I would like to see more happening aroud PyPE.
Regards. Rene On Apr 8, 10:37 am, RAH <[email protected]> wrote: > Hello Everyone, > > I'm very new (3 days) to LEO and like to say a few things: > > 1) What kept me going - in spite of a steepp learning curve - is the > inherent beauty of the outline concept. > I began my project, organized my thoughts and when I have something > that comes to mind, I immediately connect it to a node. > This TDBUT (Top-down, Bottom-up, Transverse) facility is great for > code development. > > 2) I like it because it is "All Python". If a node contains a python > code snippet, I type "CTRL-B" and it executes. > All the tools I use are Python based: Python, Sphinx, LEO, WEB2py, > PyGTK, ... This creates unity and increases productivity. > The only exception is Notepad++ which a find somewhat visually more > appealing than PE (Python Editor). > > 3) I understand that "Editing" is a matter of choice and habbit. > Myself I'm not versed in Vi (I'm don't practice it enough) but use > Notepad++ (hence my earlier post on synchronization between @file node > and external file). If I wish to edit something where I'm not > comfortable enough within LEO + Vi, I save my work, move to Notepad++ > and do what I wish and return to Leo. > > I'm very pleased by what I see so far and I couldn't agree more with > Greg's words : > "I would love to see the core ideas of Leo --- that of structuring > entire programming projects as outlines with arbitrary levels of > nestings and the possibility of cloning nodes to create views --- be > spread to a wider audience. " > > With LEO, Litterate Programming is a real pleasure. > Congratulations Edward for your ideas, dedication and nice tool. > Regards, > Rene > > On Apr 8, 3:37 am, Gregory Crosswhite <[email protected]> wrote: > > > Hey everyone, > > > The purpose of this e-mail is to propose a project which I am > > tentatively naming "Viewpoint" in order to obtain feedback. > > > I shall start by presenting my two motivations for this project. First, > > while I love Leo and use it for nearly all projects that I work on, I > > have often felt frustrated by aspects of the user interface/editor that > > aren't as polished as other text editors, which is basically just caused > > by the fact that the Leo user/developer community is much smaller than > > most of the other major text editors. Second, I would love to see the > > core ideas of Leo --- that of structuring entire programming projects as > > outlines with arbitrary levels of nestings and the possibility of > > cloning nodes to create views --- be spread to a wider audience. > > > Thus I propose a project to build the following components: > > > (1) A Java interface that provides an abstraction of the Leo core data > > model/controller, plus support for adding listeners that are notified > > when the model is changed. > > > (2) A wrapper of the current code for Leo using Jython to implement (1), > > plus support for adding listeners that are notified when the model is > > changed. > > > (3) A Swing control based on JTree that provides a view of (1), designed > > such that there can be multiple independent views of the same (which is > > the reason for adding support for listeners). > > > (4) A plugin for jEdit that gives users the ability to > > create/open/save/edit/etc. Leo outlines, based on the control > > implemented in (3). In particular, I would like to see it have the > > following features: > > > *) Ability to have multiple views of an outline, using tabs or windows. > > *) Ability to open node bodies in separate windows. (Note that opening > > the same node body in multiple windows is not a problem, since they can > > all point to the same jEdit buffer.) > > *) Ability to run Leo scripts, assuming that one knows that one is not > > just using any implementation of (1) but the particular implementation > > of (2). > > > The reason for having having (1) and (2) be separate is to give people > > freedom to experiment with different back-ends. For example, someone > > could experiment with a back-end that is written in Java/Scala/etc. to > > see if it is faster. Or, someone could experiment with their own system > > of Node heading sentinels. In fact, my original plan was to start by > > writing my own back-end (that is, my own data > > structure/tangler/untangler in Scala, which is actually almost > > complete), but Edward managed to talk me out of having this be the main > > implementation. :-) > > > Thoughts? > > > Cheers, > > Greg -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
