After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 739306 - Remove support for seed-based Javascript plugins
Remove support for seed-based Javascript plugins
Status: RESOLVED FIXED
Product: libpeas
Classification: Platform
Component: seed
unspecified
Other Linux
: Normal normal
: ---
Assigned To: libpeas-maint
libpeas-maint
Depends on:
Blocks:
 
 
Reported: 2014-10-28 15:42 UTC by Garrett Regier
Modified: 2014-11-04 13:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Remove support for seed-based Javascript plugins (48.08 KB, patch)
2014-10-28 15:42 UTC, Garrett Regier
committed Details | Review
Remove everything the seed plugin loader used (51.81 KB, patch)
2014-10-28 16:38 UTC, Garrett Regier
committed Details | Review

Description Garrett Regier 2014-10-28 15:42:02 UTC
The seed bindings lack subclassing support and as such are holding back the capabilities that libpeas can depend on for certain features that plugins are expected to use.

The bindings are also rather unmaintained these days.


Moving the Python console support into libpeas had issues due to needing to support the seed plugin loader, with this maybe we can finally get that merged in.
Comment 1 Garrett Regier 2014-10-28 15:42:49 UTC
Created attachment 289526 [details] [review]
Remove support for seed-based Javascript plugins
Comment 2 Ignacio Casal Quinteiro (nacho) 2014-10-28 15:46:16 UTC
Review of attachment 289526 [details] [review]:

Looks good to me.
Comment 3 Garrett Regier 2014-10-28 16:38:53 UTC
Created attachment 289535 [details] [review]
Remove everything the seed plugin loader used

This is no longer needed as the seed plugin loader has been removed.
Comment 4 Ignacio Casal Quinteiro (nacho) 2014-10-29 07:51:23 UTC
Review of attachment 289535 [details] [review]:

I am all for removing stuff so go ahead :)
Comment 5 Garrett Regier 2014-11-04 13:52:25 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.