Hi everyone,
Dave Land escribió:
On Feb 7, 2011, at 7:39 AM, GrayFace wrote:
...
I'm sure that the august Anthony Lieuallen (frequent contributor to this
...
workings of GM's code) could answer this in more depth, but it appears
...
greasemonkey-dev list[1] that there were several reasons for this change:
-- The feature was all but unused by any but the most technical
users, who represent a tiny sliver of the overall GM user base.
...
-- I gather that some sensed that the UI of GM was too complicated
for the majority of "casual" users.
...
-- Other browsers' "GM-like" features (such as Google Chrome's
support for user scripts as a kind of "poor man's extension") do
not maintain a separate database of includes and excludes (as GM
...
(Comment: For as long as I've used Chrome, I have found this to
be the most irritating feature of Chrome's User Script support.
When I decide to update a script, I have to remember to save the
header out of the old version, then install the new version,
then edit the new version, etc, etc, etc. Very, very weak. GM
was light-years ahead on this, and has now fallen back into the
middle of the pack, as far as I'm concerned.)
Completely agreed on that, but I can see all of the above points, an I share
them to a certain extent.
-- Maintaining a database (in the form of config.xml) of includes
and excludes that is separate from the scripts themselves is
considered to be some sort of "bad form".
...
I hope this helps. If I got it terribly wrong, I hope that someone who
knows the arguments better than I do will correct me.
Not me, certainly.
As I see it, GM shouldn't modify any files on its own, so editing the scripts
without user intervention (i.e. when updating, to keep old includes and
excludes) is a no-no; OTOH GM developers don't want to keep the
includes/excludes data in a database separate from the scripts--well, I'm not
completely OK with that, but I could live with it if...
What GM could do (or the developers be kindly asked to implement) to make
everyone lives' easier when being updated, OR updating scripts is to compare the
old include/exclude rules, either from the XML DB or scripts themselves, with
the new ones when updating a script, and tell the user that he needs to manually
update it.
Just an idea.
Regards,
--
You received this message because you are subscribed to the Google Groups
"greasemonkey-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/greasemonkey-users?hl=en.
