Re: What's your favorite way to discover nifty new programming tools, ideas, etc.?

2009-07-16 Thread Ville M. Vainio

On 7/16/09, Edward K. Ream edream...@gmail.com wrote:

 I've been relying on you, for the most part. It works, but is a bit
 passive :-)

I use google reader + rss feeds for:

planet.python.org
planet gnome
planet kde
planet ubuntu
planet debian

(yeah, google reader makes it pretty fast to skim that stuff)

-- 
Ville M. Vainio
http://tinyurl.com/vainio

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---



Re: Thoughts on Leo coding style

2009-07-16 Thread Edward K. Ream
On Wed, Jul 15, 2009 at 1:45 PM, Ville M. Vainio vivai...@gmail.com wrote:


 An example:

def add_for_polling(self, srcfname):
if not self.pollset:
 set up timer for timer_poll 
self.polldict[srcfname] = 0



I am moving away from this style.  Imo, it encourages overly long
functions/methods.  More importantly, sections can't be unit tested as
easily as a helper function.  In Leo's core you will see many helper
functions whose name ends in Helper.

Edward

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---



Re: What's your favorite way to discover nifty new programming tools, ideas, etc.?

2009-07-16 Thread Edward K. Ream
On Thu, Jul 16, 2009 at 1:19 AM, Ville M. Vainio vivai...@gmail.com wrote:


 On 7/16/09, Edward K. Ream edream...@gmail.com wrote:

  I've been relying on you, for the most part. It works, but is a bit
  passive :-)

 I use google reader + rss feeds for:

 planet.python.org
 planet gnome
 planet kde
 planet ubuntu
 planet debian


Thanks.  Here's a recent entry from planet python:

http://tierneylab.blogs.nytimes.com/2009/07/15/gates-puts-feynman-lectures-online/

Edward

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---



Re: What's your favorite way to discover nifty new programming tools, ideas, etc.?

2009-07-16 Thread Jesse Aldridge

http://news.ycombinator.com/  has some good stuff from time to time.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---



~/.leo/plugins

2009-07-16 Thread Ville M. Vainio

Currently, there is no standard place for leo to look for plugins,
apart from plugins directory of leo distribution.

That place is bad, because it's somewhere in depths of platform
filesystem, and it's only root-writeable.

Currently, I'm testing my 'autosphinx' plugin (which works fine btw
:-) by this script:

QQQ

import sys
sys.path.append('/home/ville/autosphinx')
import autosphinx
autosphinx.init()

QQQ

However, this sort of sucks for the end user. Perhaps we should
introduce ~/.leo/plugins directory, where users could install third
party plugins?

It should be looked at before the distribution 'plugins' directory,
because the users could then download the latest leo plugins from bzr
without having to wait for new version of leo.

-- 
Ville M. Vainio
http://tinyurl.com/vainio

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---



Re: ~/.leo/plugins

2009-07-16 Thread jkn

On Jul 16, 7:51 pm, Ville M. Vainio vivai...@gmail.com wrote:
 [...]
 However, this sort of sucks for the end user. Perhaps we should
 introduce ~/.leo/plugins directory, where users could install third
 party plugins?

definitely agree

J^n

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---



Re: ~/.leo/plugins

2009-07-16 Thread Ville M. Vainio

On Thu, Jul 16, 2009 at 9:51 PM, Ville M. Vainiovivai...@gmail.com wrote:

 However, this sort of sucks for the end user. Perhaps we should
 introduce ~/.leo/plugins directory, where users could install third
 party plugins?

More thoughts on this:

1. It should probably be possible to have plugins as packages
(subdirectories) in ~/.leo/plugins
2. This could be accomplished by adding ~/.leo/plugins to sys.path and
referring to plugins like autosphinx.leoplugin (which would be
handled by import autosphinx.leoplugin; autosphinx.leoplugin.init()
3. It should be possible to install leo plugins anywhere in
pythonpath. This way, you could just upload the plugins to pypi and
people could get them by easy_install autosphinx.
4. The current plugin system is a bit of a mess, in that every plugin
is a .py file is in the same directory. If your plugin needs extra
files, they are just on that one flat directory.
5. We could avoid making a definite choice about the plugin system
by introducing a directory ~/.leo/initscripts. Leo would run every
script in that directory *once* when it's launched (in arbirtrary
(alphabetical) order). Plugins could be loaded by just copying a file
there and doing the initialization.

The point 5 is probably the best short-term plan, since it gives us
unlimited tweakability without resorting to rules in .leo files.
It's also less of a security risk than autoexec kind of scripts in
.leo files.

-- 
Ville M. Vainio
http://tinyurl.com/vainio

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---



Re: What's your favorite way to discover nifty new programming tools, ideas, etc.?

2009-07-16 Thread Edward K. Ream
On Thu, Jul 16, 2009 at 1:51 PM, Jesse Aldridge jessealdri...@gmail.comwrote:


 http://news.ycombinator.com/  has some good stuff from time to time.


Thanks.

Edward

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---



Re: ~/.leo/plugins

2009-07-16 Thread Edward K. Ream
On Thu, Jul 16, 2009 at 1:51 PM, Ville M. Vainio vivai...@gmail.com wrote:


 Currently, there is no standard place for leo to look for plugins,
 apart from plugins directory of leo distribution.

 That place is bad, because it's somewhere in depths of platform
 filesystem, and it's only root-writeable.


I agree.



 Perhaps we should introduce ~/.leo/plugins directory, where users could
 install third
 party plugins?


Seems reasonable.


 It should be looked at before the distribution 'plugins' directory,
 because the users could then download the latest leo plugins from bzr
 without having to wait for new version of leo.


Again, this seems reasonable, but I haven't given it deep thought.

Improving how plugins are loaded or unloaded has been on the list for
years.  Leo 4.7 would seem like a good time.

To anticipate your next post, the subject could be considered a bit tricky.
It would be nice to do as well as we can now so we don't have to change
things yet again later.

Edward

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
leo-editor group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to 
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~--~~~~--~~--~--~---