| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
| |
This adds the new key Embedded to the .plugin
file which specifies the function to call instead
of peas_register_types to perform that same job.
https://bugzilla.gnome.org/show_bug.cgi?id=721693
|
| |
|
|
|
|
|
|
|
| |
This allows us to avoid using Lua's C API and have a
more understandable implementation.
https://bugzilla.gnome.org/show_bug.cgi?id=742410
|
|
|
|
|
|
|
| |
Using "peas-plugin-loader-python" as a
prefix is just too long.
https://bugzilla.gnome.org/show_bug.cgi?id=742349
|
|
|
|
| |
Using vgdump and cgdump isn't very informative.
|
|
|
|
| |
Should be safe given gedit's .gitignore also does this.
|
|
|
|
| |
This uses the provided gtkdoc-check program.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
https://bugzilla.gnome.org/show_bug.cgi?id=739306
|
|
|
|
|
|
| |
When the PEAS_PYTHON_PROFILE enviroment variable
is set profiling information will be output when all python
plugins are unloaded.
|
|
|
|
|
|
|
|
| |
There have been changes to the gjs bindings and as the issue
has only recently been noticed it is assumed that support for
them is not highly desired.
https://bugzilla.gnome.org/show_bug.cgi?id=711356
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch reworks the build system so that we use the same sources to
build both a python2 loader and a python3 loader. The python 2 one
keeps the same name for backward compatibility, while the python 3 one
is explicitely called "python3".
Supporting py2 and py3 in the same build is tricky since the existing
autotools support is limited, so we make some assumptions:
- there are separate --enable-python2 and --enable-python3 flags,
--enable-python has been removed
- the py3 loader is in a separate dir but compliles the files from the
py2 loader
- for py2 we only check the binary and the python2-config tool, while
for py3 we use the proper AM_PATH_PYTHON macro
- for py2 we manually detect pyexecdir, hopefully with the same logic
used by the AM_PATH_PYTHON macro
- we do not check for Python.h header anymore since it is not strictly
needed and autoconf caching makes it difficult
- for we build the demos only for python3 (unit tests instead are
replicated for both)
https://bugzilla.gnome.org/show_bug.cgi?id=691081
|
|
|
|
|
|
| |
The vala plugin keeps breaking the build to Vala breaking
API so just remove it.
https://bugzilla.gnome.org/show_bug.cgi?id=684457
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=622664
|
|
|
|
|
| |
This generates .gcov files for C files in libpeas, libpeas-gtk and
the loaders and then it reports the coverage for each of the libs.
|
| |
|
|
|
|
|
| |
The rule runs all the tests under callgrind with the appropriate enviroment
variables and options set and the log is saved to cgdump-$$test_prog.
|
|
|
|
| |
For now the calling with args and property tests are disabled.
|
|
|
|
|
| |
For now the property tests are disabled because tests that
should fail succeed.
|
|
|
|
| |
This will allow us to easily run the same tests on other loaders.
|
|
|
|
|
| |
The rule runs all the tests under valgrind with the appropriate enviroment
variables and options set and the log is saved to vgdump-$$test_prog.
|
| |
|
| |
|
|
|
|
|
|
| |
- drop old python bindings files
- update for libpeas-gtk renaming
- add the generated tarballs
|
|
|
|
|
| |
Rather than use the gedit version numbering, use a 0. one to emphasis
the "under development/unstable" side of things.
|
|
|
|
|
|
|
|
|
| |
This is a way to handle all the plugins at once, for some specialized
use. Especially, "PeasActivatable" extensions fit fine with this new
object.
A way to check that called functions don't expect OUT or INOUT args is
currently missing.
|
| |
|
|
|
|
| |
GPE was already taken as a project name.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Those are not perfect yet as they don't allow creating a new engine and
as API coverage is not complete yet anyway, but it will serve as a base
for the python loader.
|
| |
|
|
The Gedit namespace has been replaced by a GPE namespace which means
"Gedit Plugins Engine" or "Gnome Plugins Engine" as you prefer.
Only the C loader has been imported so far, and there are still a few
gedit-isms within the source code.
|