jerone's profile

Default-avatar

jerone

  1. 13
  2. 15
  3. 19
Open ideas
  1. 31 votes
    1
  2. 29 votes
    1
  3. 68 votes
    1
  4. 1 votes
    1
  5. 1 votes
    1
  6. 2 votes
    1
  7. 13 votes
    1
  8. 2 votes
    1
  9. 50 votes
    1
  10. 4 votes
    1
Completed ideas
  1. 1 votes
    1
  2. 103 votes
    1

    intigrate @version
    completed

  3. 16 votes
    3
Comments
  1. This should be optional, otherwise I would vote against this.
    I use google a lot to find interesting (parts of) scripts.

  2. I really like to see this coming, but this is a big issue.
    First of all this requires a co-op between userscripts.org and Greasemonkey, as both are maintained by two different persons. They need to find the perfect solution which Stylish has.
    Secondly is the update check. I suggest 2 methods, which both USO already has:
    - use the @version method (easy),
    - use the diff methode (have on big scripts)

  3. I like the idea, but where to put this sub-nav; left, top, right?

  4. I like it.

    Common tags are: @name, @author, @description, @include, @exclude.
    Then you have some useful ones: @version, @namespace, @homepage, @browser, @copyright.
    And there are some remaining: @statussize, @defaulticon.
    UserJs.org uses his own to add information to the scripts page: @ujs:description.

  5. So, options to select to be supported in and tested in:
    - which browser,
    - browser version,
    - extention/addon (like GreaseMonkey or IE7PRO),
    - extention/addon version.

  6. I voted for this one, as I like to know this too. The more small info, the better.

  7. In answer to cookieMonster and iamah a start: http://userscripts.org/scripts/show/11388

  8. I agree with znerp here. Deleting scripts would disadvantage people who use the script and also the maker if he/she want to update it later on.

  9. Add at least the most important links to wiki texts for example.

  10. I do like this. Long scripts i find much more interesting then sort ones.
    Maybe also how many lines and characters the script uses.

  11. Resulted this security fix into not allowing HTML code's in "Summary" box???

  12. Users can always ask for a screenshot.
    I think adding this feature will need bigger servers.
    Maybe a little note below the "Description" section, that says that a screenie may help clarifying, and link to ImageShack for example.

  13. Its an good idea, but the searcher can also define his/hers search better. Also it would be a lot of work to group tags that belong together.

  14. When an user update this list frequently, then this will give a good percent of 'most kept script'.

  15. Of course:
    There are a lot of scripts that change things about USO itself. If you make some kind of a review contest - say every year, you could add the most rated script to the site itself. Bilding it into the site as normal javascript.

  16. This is good idea and I would vote for it as I had some points :p
    It's on the planning to make my scripts work on the other browsers too.

    I don't think scanning for "GM_*" is a good idea, as it can be used for for example cross browser scripting.

  17. Indeed, it shouldn't replace the HTML support; to many scriptpages are using it already. BBcode as extra i wouldn't mind.

  18. Aren't we already using tags?!

  19. ImageShack works also.