Re: UI idea: body editors in a grid

If you fill the cells with stickynotes (as in tabula), the editors would at least stick to the nodes. Otoh, if more felxible body editors are just around the corner, it may not be worth the hassle. On Apr 19, 2012 1:51 AM, "Terry Brown" wrote: > On Wed, 18 Apr 2012 12:48:42 -0700 > Ville Vainio

Re: UI idea: body editors in a grid

On Wed, 18 Apr 2012 11:45:25 -0500 Terry Brown wrote: > Another feature I've wanted to add to free_layout is popping out any > element into its own window (replacing sticky-notes). You could go one > better and pop-out free-layout frames which could contain multiple > widgets, like tabula curren

Re: Free range body editors

On Wed, 18 Apr 2012 11:13:35 -0500 Terry Brown wrote: > bump :) > > On Fri, 16 Dec 2011 22:24:42 -0600 > Terry Brown wrote: > > > I suspect that if body editors could be made just slightly more > > flexible it would open up whole new ways of using Leo. It seems they > > just need two or three

Re: UI idea: body editors in a grid

On Wed, 18 Apr 2012 12:57:03 -0700 (PDT) "Edward K. Ream" wrote: > As I was thinking about doing body editors with free_layout (and by > extension, the tabula editors) I had another new thought: it's time to > replace the present difficult selection code with a broadcaster/ > listener framework.

Re: Node pipes

On Wed, Apr 18, 2012 at 2:23 PM, Ville M. Vainio wrote: > The 'ileo workbook' concept is...nice in theory, but the rigid ui model where > we show only one node at a time made it hard to visualize. Yet another use for a more general broadcaster/listener framework. Edward -- You received this

Re: UI idea: body editors in a grid

On Wed, Apr 18, 2012 at 2:57 PM, Edward K. Ream wrote: > On Apr 18, 10:53 am, Terry Brown wrote: > >> When the body editor is a well behaved widget it should be straight >> forward to place them where ever you want in using the free-layout >> mechanism. > > Yes.  This might the key. > > As I was

Re: Node pipes

On Wed, Apr 18, 2012 at 11:47 AM, Kent Tenney wrote: >> Certainly.  Just assign to v.b in the appropriate place. > > Right. Leo can be considered a programming language, it is able > to do most anything one dreams up. Here we are discussing what > features are appropriate to add to the 'standard

Re: UI idea: body editors in a grid

On Apr 18, 1:42 pm, "Ville M. Vainio" wrote: > I am bringing another angle into play here - systematic selection of what > nodes are shown in the editors, in the proposed scheme we would have a > single column of editors, each displaying every child of currently selected > node. The new broadcast

Re: UI idea: body editors in a grid

On Apr 18, 10:53 am, Terry Brown wrote: > When the body editor is a well behaved widget it should be straight > forward to place them where ever you want in using the free-layout > mechanism. Yes. This might the key. As I was thinking about doing body editors with free_layout (and by extension

RE: UI idea: body editors in a grid

You are probably right. We Could also adjust the sizes dynamically based on the amount of text in the nodes Sent from my Windows Phone From: Terry Brown Sent: 4/18/2012 10:31 PM To: leo-editor@googlegroups.com Subject: Re: UI idea: body editors in a grid On Wed, 18 Apr 2012 21:42:21 +0300 "Ville M

Re: UI idea: body editors in a grid

On Wed, 18 Apr 2012 21:42:21 +0300 "Ville M. Vainio" wrote: > I am bringing another angle into play here - systematic selection of what > nodes are shown in the editors, in the proposed scheme we would have a > single column of editors, each displaying every child of currently selected > node. >

Re: Node pipes

The 'ileo workbook' concept is relevant; it allowed you to easily reference other nodes in your scripts (wb.foo meant node with headline 'foo'). It's nice in theory, but the rigid ui model where we show only one node at a time made it hard to visualize. Tabula or grid would make it more concrete a

Re: UI idea: body editors in a grid

I am bringing another angle into play here - systematic selection of what nodes are shown in the editors, in the proposed scheme we would have a single column of editors, each displaying every child of currently selected node. Expanding the scope to a grid, we could have a grid-lock-column that wo

Re: Node pipes

On Wed, Apr 18, 2012 at 11:22 AM, Edward K. Ream wrote: > On Wed, Apr 18, 2012 at 9:48 AM, Kent Tenney wrote: > >> Could...any node...be designated as a destination for output? > > Certainly.  Just assign to v.b in the appropriate place. Right. Leo can be considered a programming language, it is

Re: UI idea: body editors in a grid

On Wed, 18 Apr 2012 11:12:45 -0500 "Edward K. Ream" wrote: > > When the body editor is a well behaved widget it should be straight > > forward to place them where ever you want in using the free-layout > > mechanism. > > Are you suggesting doing free-layout in tabula? No, although that gives

Re: Node pipes

On Wed, Apr 18, 2012 at 9:48 AM, Kent Tenney wrote: > Could...any node...be designated as a destination for output? Certainly. Just assign to v.b in the appropriate place. > could [Leo] duplicate the power of simultaneous feedback shown by Light Table. Yes, provided somebody understands what

Re: section references to other outlines?

On Wed, 18 Apr 2012 09:44:42 -0500 "Edward K. Ream" wrote: > On Wed, Apr 18, 2012 at 9:27 AM, Todd Mars wrote: > > > I can use clones to make section references to sections outside of the > > tree branch in the same outline. But how can I make section references > > to other leo outlines? >

Re: Free range body editors

bump :) On Fri, 16 Dec 2011 22:24:42 -0600 Terry Brown wrote: > I suspect that if body editors could be made just slightly more > flexible it would open up whole new ways of using Leo. It seems they > just need two or three things to make them really flexible. > > - a flag to indicate whether

Re: UI idea: body editors in a grid

On Wed, Apr 18, 2012 at 10:53 AM, Terry Brown wrote: > On Wed, 18 Apr 2012 12:37:22 +0300 > When the body editor is a well behaved widget it should be straight > forward to place them where ever you want in using the free-layout > mechanism. Are you suggesting doing free-layout in tabula? EKR

Re: UI idea: body editors in a grid

On Wed, Apr 18, 2012 at 10:53 AM, Terry Brown wrote: > On Wed, 18 Apr 2012 12:37:22 +0300 > "Ville M. Vainio" wrote: > >> How about taking this idea further and locking the body editors in a >> grid, or column? > > When the body editor is a well behaved widget it should be straight > forward to p

Re: UI idea: body editors in a grid

On Wed, 18 Apr 2012 12:37:22 +0300 "Ville M. Vainio" wrote: > How about taking this idea further and locking the body editors in a > grid, or column? When the body editor is a well behaved widget it should be straight forward to place them where ever you want in using the free-layout mechanism.

Re: simple file-open problem, probably Windows, but I gotta ask

> Have you tried the suggestions posted in this still-active > thread > ? Oops, my apologies! I *do* actively read this forum, and should have caught that. Sorry for the noise! -- You received this message because you are

Re: Cannot open Leo files by double-click in Windows Explorer?

On Wed, Apr 18, 2012 at 12:20 AM, Matt Wilkie wrote: > the docs have the wrong version, It should match the above: > http://webpages.charter.net/edreamleo/install.html#installing-leo-on-windows Good catch. I think rather than updating this for every release, I'll try to generalize it a bit so p

Node pipes

The editor envy resulting from the Light Table demo has me revisiting a feature that's been percolating. Sending output to the log pane is very useful, it's how Leo talks back. Executing from the command line means one space for input and output. Executing in a Leo node and writing to the log im

Re: section references to other outlines?

On Wed, Apr 18, 2012 at 9:27 AM, Todd Mars wrote: > I can use clones to make section references to sections outside of the > tree branch in the same outline. But how can I make section references > to other leo outlines? This is a frequently requested feature, but it can't be done at present. T

Re: UI idea: body editors in a grid

On Wed, Apr 18, 2012 at 4:37 AM, Ville M. Vainio wrote: > "tabula" plugin allowed you to edit many nodes simultaneously in an > MDI canvas - i.e. you could move the body editors around freely. Tabula is part of the stickynotes plugin. It creates the following commands: tabula

section references to other outlines?

hi! I can use clones to make section references to sections outside of the tree branch in the same outline. But how can I make section references to other leo outlines? (other @url file:dada.leo) or maybe make clones to other outline nodes so that I can make section references to them? thanks! todd

Re: I've lost rev 5259!!!

On Apr 18, 7:30 am, "Edward K. Ream" wrote: > This has turned out to be a happy accident. Indeed it was. Rev 5262 uses a completely different and more fundamental fix. leoQTextEditWidget.setInsertPoint now uses the more careful code in setSelectionRangeHelper, including the lengthHelper meth

Re: I've lost rev 5259!!!

On Apr 18, 7:00 am, "Edward K. Ream" wrote: > Does anyone have the 5259 code?  Can you send it to me? Never mind. This has turned out to be a happy accident, though I still don't understand why previously pushed code disappeared. In any case, rewriting the code has revealed something bizarre.

I've lost rev 5259!!!

Something very bad just happened to Leo's bzr repository. After pushing 5259, I tried to push some changes to leoProjects.txt. I got a conflict with Terry's work. A merge didn't work, so I reverted the (minor) commit and tried to merge. That didn't work, so I did a bzr pull --overwrite. Now my

Rev 5959 appears to fix bug 981849: incorrect body content shown

This is one of the strangest bugs I've ever seen. After extensive research, I can see nothing obviously wrong with Leo's code, but clearly something was wrong somewhere. Rev 5259 fixes this bug, apparently, by having v.restoreCursorAndScroll always call setSelectionRange with "full" parameters, t

UI idea: body editors in a grid

Hey, No time to mock this up right now, just throwing it out there. "tabula" plugin allowed you to edit many nodes simultaneously in an MDI canvas - i.e. you could move the body editors around freely. How about taking this idea further and locking the body editors in a grid, or column? One fun