Re: [gedit-list] Gedit Plugins - Unofficial Enhancement Proposal

["Vinicius B. Fuentes" <vinibaggio gmail com>]

I also agree with Trond Danielsen,
btw, it would be nice to have (like NewStuffManager proposes) downloadable
plugins directly from gedit, just like the GNOME-art program,
so users could see that's easy to add new plugins and that
there are cool plugins after all, it would fetch a list of plugins and with
their description, author, it's web page, etc. It's all included in the
gedit-plugin file

On 2/23/07, Trond Danielsen <trond danielsen gmail com> wrote:

2007/2/23, Steve Frécinaux <nudrema gmail com>:
> On Fri, 2007-02-23 at 00:40 +0000, Zeth Green wrote:
> > 1. Single Plugin Format
> >
> > All plugins have a .gedit-plugin file. However, beyond that, at the
> > moment, plugins can be organised in two ways. They can be a single
> > file, or they can be a directory. This inconsistency will make it very
> > complicated for graphical plugin installation and especially
> > uninstallation.
> >
> > I propose a single format. All plugins will basically follow the
> > directory approach, but the gedit-plugin file will be inside the
> > directory.
>
> This is mostly an implementation matter. If you have some graphical
> plugin manager, he will deal with that by itself. You download the
> tarball and the GUI installs it correctly. That's how the theme manager
> works fwiw and there is no problem about that. BTW you seem to forget
> there are also C plugins (yeah, a third "format", even harder to
> install).
>

Wouldn't it be easier to add and remove plugins if the plugin engine
did a recursive search through the plugin folders? That way each
plugin could be installed in separate folder, instead of having all
.gedit-plugin files in the "root" folder?

> > 5. No bundled plugins.
>
> I don't agree. Bundled plugins are either there for ages (when nobody
> even knew gedit supported plugins) or functionnalities that are so great
> we want them as visible as possible. Some are even activated by default,
> and we can't reasonnably implement it as part of the core. More,
> packaged plugins (either gedit or gedit-plugins ones) come with full
> support for i18n, and that's important.
>

Given that there is a easy way to add plugins, I think that moving as
many plugins as possible out of the core gedit package, would actually
boost the entire plugin collection. Currently the best plugins are
allready included in gedit, and I believe that many of the other
plugins get very little attention because of this.

I think the way the gnome theme manager handles additional themes is a
good way to solve this. Draging and dropping new themes into the
plugin dialog should automatically install them in the users plugin
folder.
--
Trond Danielsen
_______________________________________________
gedit-list mailing list
gedit-list gnome org
http://mail.gnome.org/mailman/listinfo/gedit-list

-- 
Vinicius Baggio Fuentes
comp05 // turma B
ICMC-USP
-=-
eu apoio:
www.sancalivre.org.br