On Mon, Oct 26, 2009 at 7:48 AM, Xan Lopez <[email protected]> wrote: > On Fri, Oct 23, 2009 at 8:47 AM, Magnus Therning <[email protected]> wrote: >> Since I learned that Python was being dropped as a language for extensions >> I've been working on porting my bookmark synchronisation extension >> (epilicious), first to Seed (which I gave up on after a short while) and >> then to something that compiles natively. C is too painful I find, so I >> opted to write the extension in Vala (with some minor pieces in C since >> there are no Vala bindings for Epiphany yet). >> >> IIRC I still have commit rights, but I'm hesitant to push a change that >> introduces new dependencies. Should I keep this extension out of the >> official tree (maintaining it as a patch), or should I push it? >> >> I don't care too much either way really. >> >> I should add that I have the intention of rewriting the extension in Seed at >> some point in the future. At the time (before the 2.28 release) Seed was >> simply to much work to bother with. I'm sure this will change, especially >> if/when libgee can be used from within it. > > What would be required to add support for Vala extensions? You only > need to depend on the vala compiler at compile time?
Yes, the vala compiler at compile time, and in the case of this extension libgee at compile+run time. /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe _______________________________________________ epiphany-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/epiphany-list
