peppy and editra

[Rob McMullen]

On Nov 16, 2007 12:44 AM, Peter Damoc <pdamoc at gmail.com> wrote:
> On Nov 16, 2007 1:32 AM, Bill Baxter <wbaxter at gmail.com> wrote:
>> Ooh, Editra does look interesting.  Could it be the python-based emacs
> > replacement everyone has been looking for?
> >
>
> The question is could peppy be merged into Editra?

I would suspect that merging peppy into editra for the general case
would be difficult since our frameworks are fairly orthogonal.

I've borrowed the editra styling mechanism for peppy and have
contributed patches back to Cody.  I suspect we will continue to share
at least that much code.

> There is soooooo much duplicate effort on these editors... this is silly...
> and the worst part of it might be that the wxpython community looks highly
> out of focus.

You could say that about the whole open source community.  KDE vs
Gnome, Linux vs BSD, wxPython vs PyQt, etc. :)

One one hand, it is duplication of effort to some extent, but on the
other hand we all have slightly different goals.  I'm writing peppy
because I need a framework to edit lots of different kinds of files,
not just editing source code (although it does that).  No other editor
framework in python does that using multiple top level frames, so I
wrote my own.  Maybe only a small minority of people find this useful,
but that's what I really need.

> So Editra has a solid foundation, let's build on it, let's make it feature
> complete.

I'll probably continue working on peppy. :)  My pet project and all.
But, I love sharing code and using code debugged by others.  peppy is
mostly GPL licensed while Editra just changed to the wxPython license.
 All of the stuff in peppy/lib, which is a bunch of generic controls
and things that are decoupled from peppy and don't depend on peppy
itself, is licensed under the wxPython license.  Feel free to borrow.

Rob