plugins example

[~flow]

hi all,

peppy looks neat! i like that it knows to display other things than
data and is written in python. is there any ready-to-download example
for a plugin? i got stuck in the documentation about the plugin API
and would prefer to start with a template. would be great if i could
do more text-processing tasks with this tool and i will be wanting to
integrate new commands that i write in python into the user interface.
also, how to configure key bindings?

cheers,

~flow

[~flow]

ok, so far i have grokked it: i downloaded the source distribution and
copied one of the text transform classes... appears to work, i just
have to copy the changed text_transforms.py to the library.zip/peppy/
plugins in the working installation (and delete text_transforms.pyo
from there), and a new command appears on the menu. great!

which brings me to the question: which part of the program decides to
include source.zip into sys.path? is there a way to put my own
locations into sys.path during program startup?

~flow

[Rob McMullen]

On Fri, Apr 11, 2008 at 12:06 PM, ~flow <wolfga...@gmail.com> wrote:
> ok, so far i have grokked it: i downloaded the source distribution and
> copied one of the text transform classes... appears to work, i just
> have to copy the changed text_transforms.py to the library.zip/peppy/
> plugins in the working installation (and delete text_transforms.pyo
> from there), and a new command appears on the menu. great!

It sounds like you're using the windows installer version -- it will
probably be easier to develop using the source distribution and
running peppy from there using the Windows cmd shell using the command
"python peppy.py -t"

(The "-t" flag is testing mode which dumps all the debugging info and
error printing to the shell window.)

> which brings me to the question: which part of the program decides to
> include source.zip into sys.path? is there a way to put my own
> locations into sys.path during program startup?

Well, I don't develop using the windows installer version -- I have a
script to create the windows installer when I want to release a new
version. Plus, I've found problems with py2exe using plugins that
aren't included in the main library.zip because py2exe won't include
any dependencies of the plugin if they're not distributed in
library.zip. See the following for more info:

http://trac.flipturn.org/wiki/ApplicationBundles

So, it's best do develop using the regular python source distribution.
I will have to address the dependency thing at some point, but I
don't know how to fix the problem.

As to your questions from your earlier message, let me just say that
the documentation needs improvement!

I've got some written up here:

http://trac.flipturn.org/wiki/HelloWorldTutorial
http://trac.flipturn.org/wiki/SimpleActionTutorial

but I need to move it over to googlecode because that's where I'm
hosting the plugin development because it handles all the user
management stuff for me.

http://code.google.com/p/peppy/

Here's the tutorial plugin example over on googlecode:

http://code.google.com/p/peppy/source/browse/trunk/tutorial/

Hope that's enough to get you started, anyway.

Rob

PS: I like Trac for the development of the main application so I don't
think I'll switch that over to googlecode, but managing users is a
pain because I have to do it by hand and the svn and trac instances
won't share passwords, and other problems. I thought plugins might be
where more collaboration will happen, so until I figure out OpenID for
Trac or something, plugins will be there.

[~flow]

looks great! i was at http://code.google.com/p/peppy before but i
somehow had overlooked the files under source. i'll definitely try to
run from the source distribution. thanks for the fast answer,

~flow