gplugin/gplugin

Split plugin details into a separate page

19 months ago, Elliott Sales de Andrade
fcd52dc4273e
Split plugin details into a separate page

This modifies the `GPluginGtkView` into a stack, showing the list of plugins by default (called the 'overview'), or a page for a specific plugin. Going back and forth is automated, but an application can request the page for a plugin directly if needed.

The plugin row no longer expands to show details or shows a config button, but its activation goes to its own page now. This also makes each row a bit more balanced vertically, since there's no `GtkRevealer` taking up invisible space underneath.

The new plugin page is _mostly_ a copy of the previous plugin row, except:

* It's always expanded (or rather, it cannot be collapsed.)
* The main details are re-arranged a bit to fit nicely on a page.
* All information is found via `GtkExpression`s.
* Instead of separate labels for each author/dependency, these are now a single newline-separated label, which is easier to generate.
* Booleans display a check mark instead of text, like in the inspector.
* Information labels are selectable and have a `labelled-by` relation.
* The error message is allowed to wrap.

Settings, once implemented, can go at the end of this page.

I debated splitting the plugin info into a stack with 'important' vs 'developer-oriented' entries (somewhat how `GtkAboutDialog` splits its information), but that can go in a separate review if it's done.

NOTE: This deletes the `expanded` property from `GPluginGtkPluginRow`; that's probably an ABI break, though /r/1834 means it was never registered in a released version.

Testing Done:
Opened the separate page of a few plugins, and saw that details were available. Also, the switch was in sync with the switch in the overview.

Reviewed at https://reviews.imfreedom.org/r/1840/
There are a few notes about building on OSX.
First off, building has *ONLY* been tested against homebrew. If you want to
support fink or macports, please let me know and I will merge your pull
request.
## Lua
For the Lua loader to work, you need to install `lgi` from luarocks either
systemwide for lua 5.1 as `lgi` does not currently work with lua 5.4 which is
the default in homebrew.
To make this work, you'll need to install both `lua@5.1` and `luarocks` via
`brew install lua@5.1 luarocks`. Once those are installed, you'll need to
create `/usr/local/etc/luarocks/config-5.1.lua` with the following contents.
```
-- LuaRocks configuration
rocks_trees = {
{ name = "user", root = home .. "/.luarocks" };
{ name = "system", root = "/usr/local" };
}
lua_interpreter = "lua5.1";
variables = {
LUA_DIR = "/usr/local/opt/lua@5.1";
LUA_BINDIR = "/usr/local/opt/lua@5.1/bin";
}
```
Once that is done, you can then finally install `lgi` with the following
command.
```
luarocks --lua-version=5.1 install lgi
```
## Python3
If you're using homebrew, you need to install `pygobject3`.