Only two issues remain open for 0.9.0:
https://github.com/greasemonkey/greasemonkey/issues/labels/0.9.0
One I believe to be an upstream bug, and the other is just a place
holder to remind me to get the latest translations from babelzilla.org
before the final release.
So, as linked above, here's the first release candidate for Greasemonkey
version 0.9.0. Please note that it is marked for Firefox 4
compatibility, so that it can be tested, but Firefox 4 compatibility IS
INCOMPLETE. Barring any big issues brought up, I'd expect the 0.9.0
release to include a few more translations, and a lower max version
compatibility flag (either 3.6.* or 4.0b7, I'm not yet sure which).
The known Firefox 4 related flaws are tagged for the next release:
https://github.com/greasemonkey/greasemonkey/issues/labels/0.9.1
Please check that list before reporting any Firefox 4 related issues.
Otherwise, we're generally very interested in hearing any feeedback,
positive or negative. The -dev list is the best place to discuss
Greasemonkey's development.
Thanks in advance!
Instinctively I suspect having a UI for this would be useful for
people who are not comfortable editing the code directly though.
> --
> You received this message because you are subscribed to the Google Groups
> "greasemonkey-users" group.
> To post to this group, send email to greasemon...@googlegroups.com.
> To unsubscribe from this group, send email to
> greasemonkey-us...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/greasemonkey-users?hl=en.
>
>
Correct. You can (and must, if you wish to change it) just edit the
script now.
> Instinctively I suspect having a UI for this would be useful for
> people who are not comfortable editing the code directly though.
As best we could tell, very few people in general change
includes/excludes. Our decision was basically that the cleaner UI
(without it in your face) was a gain for more people than the just
barely more complicated process of editing the file is a loss for those
that need to learn it.
- Is there a new requirement that we have to restart after
uninstalling a script? If I uninstall a script, and say re-install
it(if I don't see the above problem), it doesn't acknowledge to have
installed it. Though if I restart after uninstalling and then install,
it works fine.
- Could there be an ability to just 'type to the script name' in the
script management section rather than searching by scrolling - This
used to be the case in the old (or stable) GreaseMonkey. I hope you
get what I mean.
This has always been true. In 0.8.x, re-installing a script loses the
custom include/exclude values.
Also, the search you mentioned does find a script in FF 4.0, but then
you can't edit it if you right click. It only shows the 'Show More
Information', & Remove, Disable menu items and buttons.
Also, is no one else seeing the first problem? When I install a script
and re-install newer version after making modifications, very soon the
'Install' button stops working. If I go on to delete all the stale
'numbered' folders of the script, it immediately works again.
I just added https://github.com/greasemonkey/greasemonkey/issues/issue/1242
This seems like a critical blocker, to me. If this is an
intentional
change, users need to be made aware of it at install-time somehow.
-- Jay Rossiter http://www.cothlamadh.net/ 503.896.6187 si...@cothlamadh.net
Please don't. The -dev list is where discussion of the development of
core greasemonkey happens, and is where bugs should be discussed. As I
said in the original message which you quoted:
--
.. at the moment, Greasemonkey is reachable via a small icon
in the add-on-bar only. .. Eventually, I'd like to disable the add-on-bar on the
bottom of my browser ..