Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Options

Better Extensions page

13»

Comments

  • Options
    @ MySchizoBuddy See how you use delegation. You create a function and attach it to a part of a class. When the class is executed it call the function that are attached to it. Imagine the jQuery extension is a Render Control class. If the extension that need to use jQuery are jQuery delegations, you are sure that they will only be executed when jQuery is installed and you can make sure that the jQUery script is loaded first. That 's just a hack, that's not perfect, but that can be good enough in this case.
  • Options
    MarkMark Vanilla Staff
    Wanderer just had another good idea:

    I wish there was a way to mark extensions [not for release] to exempt them from the update checker
  • Options
    I wonder if may digress for a little self - education... What is the procedure for posting Yahoo-Flickr photos in this discussion, please? What is the procedure for posting the yellow-background "Dependencies: Yes" in this discussion, please? What is the procedure for posting the borders around the bordered-comments in this discussion, please? Any information will help me in another discussion about modifying categories. Thank you.
  • Options
    I like add ons. I like to download and install as many as possible. I like to make add ons to suit my extra needs. This results in a lot of add ons. Some add ons I disable and enable a lot, for reasons not needed to go into here. But because of this, I prefer an alphabetically listing of add ons. Thats why the first mock up of Schizo is the one I prefer, when viewing my add ons. Usability wise, having the support link as a seperate to go to the add ons download page seems like the best thing. Also names of not installed add ons, should go to their download pages. For Thickbox and Inn line add ons, how about instead of dependency, have it listed as "Takes advantage of". Add ons.

    In case you didnt notice, I like add ons and even managed to write add ons in every sentence in this post, at least once.
  • Options
    whoa i didnt notice!! thats weird!
  • Options
    MrDoI like to download and install as many as possible.

    No mention of add-ons:)
  • Options
    It was to the add on effect of getting to type ANOTHER post with a lot of add on talk in it, that I purposefully left out that sentence. It was also funny to see who would jump at it, saying "the second sentence has no add on". Thanks for biting Guazy (add on) !
  • Options
    haha, well shucks.
  • Options
    wow now i feel dum.......(Sic i know)
  • Options
    lechlech Chicagoland
    edited May 2007
    Mark pointed me here so I've only been able to briefly skim what's been discussed so excuse me if I'm repeating anyone as I've simply read an odd few suggested already mentioned. Although so far this all looks very promising, one thing may be added with the dependency notifications as noted in the first image. While splitting up dependencies or extensions that require them why not just allow the enabling of those dependencies when they're listed as such.

    So you can then see the dependency within the extensions that need them and instead of resorting the entire list to show sub-classed extensions as dependencies or weird tree/threaded views. the option to turn them on within the extension that needs them is already there. In a sense it would turn on both or all extensions needed (providing they're present) in one click. Otherwise grey out and disable the extension if its dependencies are not present and mark missing dependencies red with option links on where one can get them.

    Mark

    I wish there was a way to mark extensions [not for release] to exempt them from the update checker
    Perhaps adding a current status/min/max value to the extensions would solve this if the updater and add-ons site could check the values accordingly. A little extra work but beneficial in the long run.

    Status could work as a keyword (alpha/beta/release) and the updater could check for only release candidates as an example and anything marked as alpha/beta/anything else gets skipped. Alternately we could include an option of levels to check for if someone is running all beta extensions and wants to see updates for those as well. Maybe allowing authors to specify this value upon upload/modification of a new extension as well as in the extension itself so when things change neither vanilla or the add-on site gets confused.

    As for the version min/max values those are fairly self explanatory for targeting compatibility within Vanilla itself, I think all add-ons/themes/styles could take advantage of this in one form or another when we see more and more add-ons pop up.
This discussion has been closed.