Re: form history

On Tue, 2005-03-15 at 18:39 +0100, Eyal Oren wrote:
> and is there some explanation somewhere on how to write extensions.
> do i need to recompile epiphany after I write an extension?

You don't need to recompile Epiphany after writing extensions. In fact,
often after upgrading (minor versions) of Epiphany you don't even need
to recompile the extensions.

The guide is at

I've also written a guide to using the Python Console. I heartily
recommend using Python to prototype extensions. You can do almost as
much as in C. (The only trick nobody has figured out yet is Mozilla
interaction, but that may be possible; I don't think anybody has tried
to get it working at all.)

The Python Console guide:
(some time I or somebody else will write up descriptions for all the
extensions and then put them on the Epiphany website. When that happens,
the Python Console page will move to Epiphany's website.) Note that
there is a newer Pyphany release than the one mentioned in that web
page; search this mailing list's archives for the release announcement.

The Epiphany source code is an invaluable resource, whether you're using
C or Python to write extensions. Be sure to keep it handy. Also, the
existing extensions are good examples of how to do New and Exciting
Things. (Not to mention, the extensions-manager-ui extension is darned
useful just for *loading* extensions.)

If you need any help, ask on IRC (#epiphany on, ask on
this list, or email me directly.

Adam Hooper <adamh densi com>

Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]