Re: Terry: todo.py semi-broken since rev6010

On 9/20/2013 11:31 PM, Terry Brown wrote: Emails crossed :) I'll try and sort it out tomorrow. Cheers -Terry Thanks! My hunch is that it is either a redraw issue, or something to do with the move of iconDir to c.cleo, rather than calculated on the fly. No clue though why that second bit w

Re: Warning: revs 6016-6020 contain a grand housekeeping

On 9/20/2013 11:29 PM, Terry Brown wrote: On Fri, 20 Sep 2013 23:05:39 -0400 gatesphere wrote: Even stranger - the icons (for a particular node) come back if I add a due date to the node... Terry, help! Hmm, so same file works on one machine and not the other? I don't seem to recall having a

Re: Terry: todo.py semi-broken since rev6010

Emails crossed :) I'll try and sort it out tomorrow. Cheers -Terry On Fri, 20 Sep 2013 23:18:32 -0400 gatesphere wrote: > Hi Terry, > > The revision you did to add the calendar icon on nodes with due dates > kind of broke todo.py for me. The icons for priority were missing on > several nod

Re: Warning: revs 6016-6020 contain a grand housekeeping

On Fri, 20 Sep 2013 23:05:39 -0400 gatesphere wrote: > Even stranger - the icons (for a particular node) come back if I add a > due date to the node... Terry, help! Hmm, so same file works on one machine and not the other? Anything you can send me? You're seeing the "calendar" "31" icon thin

Re: Warning: revs 6016-6020 contain a grand housekeeping

On Fri, 20 Sep 2013 19:50:34 -0700 (PDT) "Edward K. Ream" wrote: > Indeed, I did remove one method from bookmarks.py. bzr says you didn't...? Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop

Terry: todo.py semi-broken since rev6010

Hi Terry, The revision you did to add the calendar icon on nodes with due dates kind of broke todo.py for me. The icons for priority were missing on several nodes in workbook.leo, but they reappeared after clicking each node, applying a due-date, and then removing it. After this, I was able

Re: Warning: revs 6016-6020 contain a grand housekeeping

On 9/20/2013 11:04 PM, Edward K. Ream wrote: On Fri, Sep 20, 2013 at 9:58 PM, gatesphere > wrote: On 9/20/2013 10:53 PM, gatesphere wrote: Icons from todo.py are broken - my nodes are naked. I'm looking for the rev that broke them now, will repo

Re: Warning: revs 6016-6020 contain a grand housekeeping

On Fri, Sep 20, 2013 at 9:58 PM, gatesphere wrote: > On 9/20/2013 10:53 PM, gatesphere wrote: > >> Icons from todo.py are broken - my nodes are naked. I'm looking for the >> rev that broke them now, will report back. >> -->Jake >> > It appears to be rev 6010. Strange, because it worked on my ot

Re: Warning: revs 6016-6020 contain a grand housekeeping

On 9/20/2013 10:53 PM, gatesphere wrote: Icons from todo.py are broken - my nodes are naked. I'm looking for the rev that broke them now, will report back. -->Jake It appears to be rev 6010. Strange, because it worked on my other machine. I need to do some debugging here. -->Jake -- You r

Re: Warning: revs 6016-6020 contain a grand housekeeping

On 9/20/2013 10:50 PM, Edward K. Ream wrote: Today's work removes dozens of unused methods that are holdovers from the qt gui. All unit tests pass, and pylint is happy, but these checks apply mostly to Leo's core (and gui) code. It's possible that plugins may use some of these methods. Inde

Warning: revs 6016-6020 contain a grand housekeeping

Today's work removes dozens of unused methods that are holdovers from the qt gui. All unit tests pass, and pylint is happy, but these checks apply mostly to Leo's core (and gui) code. It's possible that plugins may use some of these methods. Indeed, I did remove one method from bookmarks.py.

Re: Leo Blog: publishing instructions added to the readme

On Friday, September 20, 2013 11:05:42 PM UTC+8, Jacob Peck wrote: > Hi all, > > I've written up some rough publishing instructions for writing articles > on the Leo blog. They're in the README.md file of the > leo-editor/leo-blog.git repo. You can view them here: > https://github.com/leo-ed

Re: My attempt at a Leo-flavored productivity system (with gamification)

On Fri, 20 Sep 2013 13:51:47 -0400 Jacob Peck wrote: > Plus, I wanted to add some gamification into them... so I came up with > LTD (Leo Things Done... yeah, bad name but it works for me). Co-incidentally the U of Minnesota's Institute on the Environment has an article on gamification in its cu

My attempt at a Leo-flavored productivity system (with gamification)

Hi all, I've been working out a way to increase my productivity - I juggle far too many tasks at any time, and the majority of them are personal, leisure projects (non-work related). I figured Leo would be a good tool for me to use -- especially with todo.py -- to manage this. I looked into

RE: On Topic: Intuition Pumps

> -Original Message- > From: leo-editor@googlegroups.com [mailto:leo-editor@googlegroups.com] > On Behalf Of Edward K. Ream > Sent: Friday, September 20, 2013 8:14 AM > To: leo-editor@googlegroups.com > Subject: On Topic: Intuition Pumps [snip] > "The general technique of making a more-o

Leo Blog: publishing instructions added to the readme

Hi all, I've written up some rough publishing instructions for writing articles on the Leo blog. They're in the README.md file of the leo-editor/leo-blog.git repo. You can view them here: https://github.com/leo-editor/leo-blog#how-to-publish-on-the-leo-blog Any suggestions? I have to admi

Re: On Topic: Intuition Pumps

> I am focusing on the simplest useful tools that might detect *some* kinds of errors. > I was generalizing. So what kind of errors would you detect? Also you say about code that handles run time type changes: " Indeed, *all* of Leo's functions and methods will quickly fail if they do not,

Re: New post on the leoblog: Custom printing with printing.py

On 9/20/2013 10:02 AM, Edward K. Ream wrote: On Friday, September 20, 2013 8:57:32 AM UTC-5, Jacob Peck wrote: > Just posted...http://leo-editor.github.io/custom_printing.html Excellent! I suggest putting this link in the docstring for

Re: "@@button replace g.choose" in scripts.leo

On Friday, September 20, 2013 6:33:20 AM UTC-5, Edward K. Ream wrote: > This morning I realized that 2to3 was designed to do something similar. I'll redo the script using 2to3 to see what the pros and cons are. And a little later I realized I had already written 2to3 fixers for the ill-fated d

Re: On Topic: Intuition Pumps

On Fri, Sep 20, 2013 at 8:50 AM, Todd Mars wrote: > So your static type checking project has the goal of producing > C-performance code system. Meaning it can be compiled into machine code. > No. I didn't say that. I don't really know what the goals are. As an antidote for this somewhat ridi

Re: New post on the leoblog: Custom printing with printing.py

On Friday, September 20, 2013 8:57:32 AM UTC-5, Jacob Peck wrote: > Just posted...http://leo-editor.github.io/custom_printing.html Excellent! I suggest putting this link in the docstring for printing.py. Edward -- You received this message because you are subscribed to the Google Groups

Re: New post on the leoblog: Custom printing with printing.py

On 9/20/2013 9:57 AM, Jacob Peck wrote: Hi all, Just posted an article that I've been meaning to write for... months now. Yeesh. It *should* be available here soon: http://leo-editor.github.io/custom_printing.html It's available now on the front page (http://leo-editor.github.io/), but it

New post on the leoblog: Custom printing with printing.py

Hi all, Just posted an article that I've been meaning to write for... months now. Yeesh. It *should* be available here soon: http://leo-editor.github.io/custom_printing.html It's available now on the front page (http://leo-editor.github.io/), but it takes github a few minutes to populate o

Re: On Topic: Intuition Pumps

So your static type checking project has the goal of producing C-performance code system. Meaning it can be compiled into machine code. Well the problem might be that code can make type assumptions and change types based on run-time events rather than build-time knowledge. So for example during

Re: Any way to create a hidden node?

On Fri, 20 Sep 2013 05:45:07 -0500 "Edward K. Ream" wrote: > I won't reject such a change out of hand, but I don't encourage it. And any > patch had better be compatible with the (complex) code that handles > directives. In other words, even if there is an @edit icon, Leo must > always support

On Topic: Intuition Pumps

I'm taking great pleasure in reading Intuition Pumps and Other Tools for Thinking http://www.amazon.com/Intuition-Pumps-Other-Tools-Thinking/dp/148051 by the great Daniel Dennett http://ase.tufts.edu/cogstud/incbios/dennettd/dennettd.htm Here is what Richard Dawkins had to say about the book

Re: Leo in a nutshell, including the Leo Aha

> > Programmable: Leo scripts (Python scripts in Leo outlines) have *easy* > access to all Leo outlines, and *easy* access to all of Leo's own source > code. Conversely, Leo outlines naturally organize even the largest computer > programs. > > The *Leo Aha* is the moment when someone realizes

Bugs to be fixed for Leo 4.11

Here is the list of bugs that I have tentatively scheduled to be fixed for Leo 4.11. I'll do as many as I can for 4.11b1, due in about a week. Besides these bug reports, there are enough documentation-related items to keep me busy. These are the only bugs I plan to fix. Feel free to request t

Re: "@@button replace g.choose" in scripts.leo

On Thursday, September 19, 2013 12:08:15 PM UTC-5, Edward K. Ream wrote: > This is a tricky task. One can't just use s.find to look for g.choose. Ditto for discovering the test, a and b args. Instead, the script must carefully parse Python strings, comments and parenthesized expressions. >

Re: Leo cheatsheet

On Wed, Sep 18, 2013 at 7:54 AM, wrote: > Is a Leo cheatsheet available anywhere? > Not to my knowledge. It's a good idea, and it's on the to-do list. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and s

Re: Calendar icon for todo items

On Wed, Sep 18, 2013 at 5:25 PM, Terry Brown wrote: > Just pushed a change which shows a calendar icon on nodes with duedate > ] > or duetime set via the todo.py plugin. Thanks for this work, Terry. Edward -- You received this message because you are subscribed to the Google Groups "leo-edi

Re: [Answered] Create a command that accepts arguments - Define a function globally for a Leo file

On Fri, Sep 20, 2013 at 2:42 AM, Fidel N wrote: > > >> def MyFunction(string): >> g.es(string) >> c.MyFunction=MyFunction #We store the function in c >> c.MyFunction("this works") > > Good trick. However, it pollutes the namespace of class Commands. Take a look at the tree:: @file l

Re: Why Leo as a web app is unlikely

On Thursday, September 19, 2013 7:55:22 PM UTC-5, Differance wrote: > > 2. Creating a Leo outline widget is extremely complex. Even starting > with a > > working javascript outliner, one has to deal with events (commands) > coming > > from Leo scripts rather than from the user. > > I wonde

Re: Why Leo as a web app is unlikely

On Thu, Sep 19, 2013 at 9:27 PM, Terry Brown wrote: > > > There are two reasons why Leo is unlikely ever to be a web app. > > By web app. you mean in-browser app., I'm assuming. > Correct. > > > 1. There are somewhere around a million lines of Python code in Leo's > core > > and plugins. Thu

Re: Any way to create a hidden node?

On Thu, Sep 19, 2013 at 9:18 PM, Terry Brown wrote: > the proposed change wouldn't interact with the inheritance issues The OP's proposal was to move '@edit', for example, from v.h to v.u['_attr'] or something like that, and render the node with an icon to show its @editness, rather than

[Answered] Create a command that accepts arguments - Define a function globally for a Leo file

Hi: While I was preparing the question I came up with the answer. Im still posting this because IMO its a very useful way of using the dictionary in c.XXX, and I couldn't think of it before. This can be used instead of @command for creating functions that accept arguments and are available in th