Commits on Jul 14, 2008
  1. Teach ajaxSetGetCombinedTags about datatype/section/topics

    scc committed Jul 14, 2008
    I even attempt to set the section and topic from the supplied tags, but I
    that is not fully working yet.
  2. CSS: minor changes getting closer to reality

    scc committed Jul 14, 2008
    Turned off the blue debugging box around the system bar.  Moved the spinner to
    the left as Rob asked.  No special color for editor tags (like 'dupe').  No
    extra weight for sections and topics.
  3. Hook the (+/-) capsule directly into the tag widget

    scc committed Jul 14, 2008
    We were partially hooked in before this; except that since we weren't going
    through click_tag, there was a chance to set one of {nod, nix} without
    deactivating the other (Sorry Jamie and Tim, I know it's not supposed to be
    possible, but I see it happen.)  Now that it goes through click_tag, it's
    subject to the normalize_nodnix() on commands that forces the correct
    	+ adapt click_tag() to also serve the (+/-) buttons
    		+ $tag_el is now $(this) if no .tag is found
    		+ deduce if the click is on the (+/-)
    		+ and select the right tag, if so
    		+ the old test for useless clicks on the <li> outside the tag
    		  must be updated to allow (+/-) clicks through
    		+ now we must find the tag-widget itself not just from inside,
    		  as before, but from outside as well
    	+ add click_tag as the click handlers on all new $('.up, .down')
Commits on Jul 13, 2008
  1. Try to prevent jQuery from thinking tags are XML; console.log for deb…

    scc committed Jul 13, 2008
    The tag response isn't XML, so not only is jQuery choosing the wrong type, it
    also then refuses to actually give us the respone because it's ill-formed.
    Don't release tag-widget for public use until removing console.log statements.
Commits on Jul 11, 2008
  1. Typofix

    jamiemccarthy committed Jul 11, 2008
  2. Typofix

    jamiemccarthy committed Jul 11, 2008
  3. Update

    pudge committed Jul 11, 2008
  4. Stupid alternation

    pudge committed Jul 11, 2008
  5. Bugfix: (already live) template logic for adding tag-widget was misgu…

    scc committed Jul 11, 2008
    s/the_user/user/ --- in other words: attach the tagwidget to this item if the
    user viewing it has tagwidget_debug, instead of if the user who _wrote_ this
    item has it set.  :-(  Thanks to Tim Vroom for figuring this out!
Commits on Jul 10, 2008
  1. New openproxy al2 type

    jamiemccarthy committed Jul 10, 2008
  2. Update

    pudge committed Jul 10, 2008
  3. Fix for comments loading in wrong order

    pudge committed Jul 10, 2008
    Async was our problem here, sync shouldn't cause a serious problem
  4. Dumb BBEdit syntax coloring fix

    pudge committed Jul 10, 2008
  5. Teach the tag widget about `contexts' for suggesting related tags

    scc committed Jul 10, 2008
    For now, build just the nod and nix contexts in the convenient template already
    using those tags: nodnix_menus.  Really, though, this needs to be moved into a
    template of its own, probably also containing the well known tags stuff from the
    earlier widget styling commit.
    	+ firehose_up_down (called when you click the +/- capsule) now always
    	  wants to show the tag widget (if any), and sets its context
    	+ adding widget function: set_context.  Looks up the context by name in
    	  a global map, extracting a list of tags; then set_tags the new list
    	  as '<context>tags...' allowing any get="context" listeners to do the
    	  right thing
    	+ build the context map, filling in just nod context, nix context
  6. Teach the tag widget to style tags with global observations

    scc committed Jul 10, 2008
    E.g., if a tag appears both in the user tag bar and the top tags bar, then every
    occurance of the tag anywhere in that widget should be styled to reflect that.
    With that knowledge, the css rules could (for instance) hide in the user bar any
    tags that also appear in the top tags bar.
    Also made the style code smarter about `well known tags', though this machinery
    needs to move into a template.
    Big changes in the css to (a) make my rules win over more general base rules,
    (b) make the tag menus at least visible if not usable, (c) hide tags, as above,
    (d) renaming the prefix styles, (e) adding new styles for some of the well known
  7. As with tag-widgets, allow tag-bars to be stubs; saving code in favor…

    scc committed Jul 9, 2008
    … of templates
    The stub-expanding code decides you are a stubbed tag-bar if
    	(a) you say so, class="tbar stub"
    	(b) you have a 'get' attribute and _no_ class attribute
    Sample tag-bar stubs:
    	<div class="tbar stub" get="user" label="My Tags">tag1 tag2 tag3</div>
    	<div get="top"></div>
    The stub class will be deleted, and 'tbar' will be added if not present.  The
    value of your label attribute will become the content in an <h1 class="legend">
    element; the attribute itself will be deleted.  A menu attribute can override
    the default tag menus; the attribute itself will be deleted.
    	+ tagbar_data.list_el, the saved reference to the <ul> is now a jQuery
    	  object, so renamed $list_el
    	+ twidget_fns.init: no longer adds specific bars, now just expands stubs
    	+ new init_tag_bar(): expands and initializes a stubbed tag-bar
    	+ rewrote create_tag_bar() to now be a wrapper around init_tag_bar
    	+ added stub tag-bars to the widget template; we are no longer
    	  hand-coding them
    	+ create_firehose_vote_handler: assigns a class to prevent its listener
    	  from being treated like a stub
  8. Make tag-widget only show up for admins with users_param tagwidget_debug

    scc committed Jul 10, 2008
    The template checks the extra condition.  Other code now more carefully checks
    if a tag widget is actually available.
    	+ only include tag widget html if the user has tagwidget_debug set
    	+ firehose_fix_up_down: test if we actually found one; comment
    	+ firehose_handle_update: only install doubleclick if I actually see one
    	  or more tag widgets in the document
    	+ firehose_collapse_entry: also close the tag widget, if any; clean up
Commits on Jul 9, 2008
  1. More accurate popularity for comments

    jamiemccarthy committed Jul 9, 2008
    Comments were being added to the hose with popularity based on
    current score, but score wasn't being taken into account for
    popularity changes based on tags.
  2. Insert some needy comments into the hose

    jamiemccarthy committed Jul 9, 2008
    Based on vars, a certain fraction of comments with a minimum level
    of neediness will be inserted into the hose once their neediness
    crosses that threshold (so they can be metamoderated).  Also, all
    comments inserted into the hose get their popularity and editorpop
    scores immediately recalculated.
Commits on Jul 8, 2008