Silvio Levy <[EMAIL PROTECTED]> writes:
>> One way to stop page modes from being loaded is:
>> user_pref ('conkeror.load.page-modes/google-search-results', false);
> This works well for me. Thank you.
> Regarding the larger issue, I'm hardly experienced enough to opine,
> but it would seem to me that a contrib directory with optionally
> loadable modules (i.e. not loaded by default) would be more
> market-neutral and generate fewer surprises than a hardwired list of
> sites that are specially treated (google, youtube, youporn etc.)
Well, specifying that a module is to be loaded by default is a separate
matter from actually placing it in a different directory. The
defaults/preferences/default-modules.js file specifies which optional
modules are loaded by default (currently all optional modules). It is
not clear that putting some modules in a separate directory would
actually provide any advantage.
The minibuffer does show you if there is a page mode loaded.
I think of page modes as being roughly analogous to Emacs major modes,
though of course there are many differences.
I think that for many sites, a page mode can be designed such that it is
essentially a strict improvement, in that everyone, or nearly everyone,
prefers it. For media sites like youtube and google video where the
mode merely specifies how to find the embedded media file and changes
some operations like save (s) and shell-command-on-file (x) and
shell-commmand-on-url (X) to operate on the embedded media, it is hard
to imagine that anyone would find it undesirable, and I think nearly all
users would prefer that as many such modes as possible are loaded by
default.
Similarly, for sites like google mail and google reader where the site
can only be used reasonably in pass-through mode (enabled via C-M-q)
without the page mode, everyone would likewise find the mode an
improvement.
It seems that in the case of the google search results mode, I may have
gotten it wrong, and so it seems that it would likely be best to disable
that mode by default.
As to the question of whether to distribute such modes separately from
Conkeror itself, I think it is a matter of weighing the advantages and
disadvantages of the two alternatives. Currently, there really isn't
any good system for separate distribution, and due to this problem,
there is strong reason to distribute them with Conkeror.
I don't think saving disk space is really an important argument at all,
as Mozilla is very large itself. The page modes are often quite small,
so even hundreds or thousands of them wouldn't take up that much space,
though I suppose if it really got to that point it may well make sense
to somehow separate them into a different repository or coming up with
some better distribution method.
Likewise, keeping them in the main Conkeror repository provides a good
way to ensure that the most up-to-date version is easily available.
Perhaps others can share their opinions on this, though; even simple
statements of preference would be useful.
--
Jeremy Maitin-Shepard
_______________________________________________
Conkeror mailing list
[email protected]
https://www.mozdev.org/mailman/listinfo/conkeror
