Re: Porting of Python extensions?



Josselin Mouette wrote:
Le jeudi 02 juillet 2009 à 18:03 +0300, Xan Lopez a écrit :
Open bugs with the extensions and me or someone else will surely port
those, they sound pretty simple.

[..]

I have to say I’m also not fond of the JavaScript idea. Is it possible now
to access the DOM tree from the extensions? If it’s still not, it sounds
like a big regression from the Python extensions, from which you can use the
tons of existing Python modules.

Yes, I second that.  I'm currently struggling with rewriting Epilicious (with
a renaming in the process) in Seed.  The lack of basic things like a
dictionary type is really quite a nuisance.  The same goes for a set type.
I'm sure there are quite a few other things that I'll miss as I go along.

On the whole I'm so far not completely against Seed as a replacement of Python
as an extension language.  However, at the moment the missing pieces are
painfully obvious.  In the long term Seed does offer a chance of better
support and better integration (e.g. I hope I'll be able to stop re-compiling
epiphany for AMD64 just because the Python bindings break when compiled with
optimisation on that platform, a bug that's been known for years now).

Oh, BTW, I could _really_ need a Seed Console extension! :-)

/M

--
Magnus Therning                        (OpenPGP: 0xAB4DFBA4)
magnus@therning.org          Jabber: magnus@therning.org
http://therning.org/magnus         identi.ca|twitter: magthe

Attachment: signature.asc
Description: OpenPGP digital signature



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