gregier / libpeas Goto Github PK
View Code? Open in Web Editor NEWA GObject plugin library
Home Page: http://live.gnome.org/Libpeas
License: GNU Lesser General Public License v2.1
A GObject plugin library
Home Page: http://live.gnome.org/Libpeas
License: GNU Lesser General Public License v2.1
Introducing libpeas =================== libpeas is a gobject-based plugins engine, and is targetted at giving every application the chance to assume its own extensibility. It is currently used by several Gnome applications like gedit and Totem. It takes its roots in the old gedit plugins engine, and provides an extensive set of features mirroring the desiderata of most of the applications providing an extension framework. Multiple extension points ------------------------- One of the most frustrating limitations of the Gedit plugins engine was that it only allows extending a single class, called GeditPlugin. With libpeas, this limitation vanishes, and the application writer is now able to provide a set of GInterfaces the plugin writer will be able to implement as his plugin requires. On-demand programming language support -------------------------------------- libpeas comes with a set of supported languages (currently, C, Lua 5.1, Python 2 and Python 3). Those languages are supported through “loaders” which are loaded on demand. What it means is that you only pay for what you use: if you have no Python plugin, the Python interpreter won't be loaded in memory. Of course, the same goes for the C loader. Damn simple to use (or at least we try hard) -------------------------------------------- Adding support for libpeas-enabled plugins in your own application is a matter of minutes. You only have to create an instance of the plugins engine, and call methods on the implementations of the various extension points. That's it, no clock harmed. A shared library for everyone ----------------------------- As I noted earlier, the latest improvements of our beloved development platform made it possible to create bindings for apps very quickly. And with the Gnome 3 announcement, this looked like the perfect timing to make the plugins engine and its latest improvements available to everyone, with a library. Also, hopefully it will reduce code duplication and allow bugs to be fixed at the right place, once and for all, improving the quality of our applications. As a member of the Gnome community and as an offspring of gedit, libpeas already shares most of the Gnome infrastructure and philosophy: * You can download the first release tarball on the Gnome FTP server. * You can browse the source and contribute using our git repository. * You can come and discuss with me and others on #libpeas (GimpNet) * And you can report bug or propose new features through the good old Gnome Bugzilla, against the libpeas module. A few hints on using libpeas ============================ As always for the new projects, it can take some time to grasp all the subtleties at first. Plugins versus Extensions ------------------------- Something that is going to puzzle most of the newcomers is the fact that the libpeas API talks about both plugins and extensions, two terms that are usually used interchangeably, but who have very different meanings in libpeas. Let's try and give a definition of both of these words in this context: - Plugin: In the context of libpeas, a plugin is a logical package. It's what you will enable or disable from the UI, and at the end it is what the user will see. An example of plugin for gedit would be the file browser plugin. - Extension. An extension is an object which implements an interface associated to an extension point. There can be several extensions in a single plugin. Examples of extensions provided by the file browser plugin would be the configuration dialog, the left panel pane and a completion provider for file names. Sample code ----------- The libpeas package contains a sample application called peas-demo, and sample plugins written in C, Lua and Python. The global idea is this one: you create a new PeasEngine instance and give it the information needed for it to find your plugins. Then you load some plugins (you can use the PeasGtkPluginManager for that purpose) and perform actions through some PeasExtensions objects you can get from the engine. Copied from http://log.istique.net/2010/announcing-libpeas
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.