I love the tool tips too, some people are disabled and just can't write proper subject lines. The java mouse overs are far quicker than opening the link and waiting for the thread to load only to find nothing of interest.

You know you can get anyone to do anything if you ask in the right way.

Dani, your site is truely awsome, and just a couple of months back there were these totaly cool options in the control panel that let me configure the javascript at a very granular level. Those options blew me away I was in options heaven, is it possible in your busy diary to bring them back please?

Bumbling highlights square. Thread preview window. Whatever you want to call it.

Well they don't bumble anymore

Yay! The bees are bee-ten.

Now fix the smileys so we can tell what we are getting. We now see the code instead of the smiley.

And people would use code blocks more if they had the button available in the quick reply box.

You're seeing a stripped down WYSIWYG editor because you have JavaScript features disabled. Because the bumble-bee tooltips are gone, you can now safely return to reenabling JavaScript features. The ability to disable all of the JS features is really reserved for people with very slow computers or dial-up connections, so they can still have an enjoyable DaniWeb experience even though it may be lacking in some of the more elaborate (and less necessary) bells and whistles.

As mentioned in a previous post, the vBulletin editor has rather messy code, and I was unable to find an easy way to add additional buttons to the Quickreply box. The next version of vBulletin is going to be migrating to the Yahoo! JavaScript API which means the QuickReply box will be rewritten for the most part. So I'll take a look at it when that happens. In the meantime, I'm not going to waste hours of time trying to figure out h ow to add a button to code that is so messy that the developers have already acknowledged it's being rewritten in the next version.

It seems to be working now. I was getting a different editor I hadn't seen before at times. It had dropdown menus for text color, smileys, and attachments. But instead of visible smileys in the dropdown, I saw the codes for the smileys. And the editor selector was missing

As you can see from the earlier post, I switched the scripting back on.

I still see the code for the smileys in the text, but not in the dripdown menu. And the spellchecker says the smiley is spelled wrong.

I had to start over again on this post, because I got "Database error" when I tried to go advanced to get the stupid smiley. When I hit back from the error message, the text I wrote was gone.

Messy code? Maybe they used the Cuisinart I mentioned in another thread.

The systems I don't have trouble are done by IPB.

No, you're standing on flawed reasoning. Feedback is not a scientific poll.

Indeed. Otherwise if 197,421 members said nothing and one said they wanted every message to start with Dear Doctor, this message would have started with Dear Doctor.

Wait a minute, back up the bus. No one claimed that feedback was a scientific poll. I'm saying, the only feedback you have is feedback given. That's all. If you are using feedback to make decisions about the site, scientific or not, then those are your parameters.

You can make no assumptions whatsoever about feedback not given. The vast majority of site users float in and out without perhaps ever noticing a certain aspect of the site. Dani assumes that since they didn't complain, they must be in favor. That's an unwarranted assumption and is not a sound basis for making decisions.

Feedback may not be either, but that's the system in place. So when 6 or so users complain about something, you can't balance that against the 97,000 who don't, assume that's 97,000 in FAVOR, and ignore the 6 who care enough to give feedback because they are the minority. Flawed reasoning.

You take those 6 votes, ask for more feedback, ("Is anyone in FAVOR of the way things are...?) and make a decision on that feedback. While not scientific, it's better than giving "opinions in my favor" to people who've expressed no opinion at all.

While all feedback is always appreciated and always taken into consideration, decisions which affect the grand scheme of things are never made exclusively based on feedback or polls from community members posting in this forum. It would be impractical to make a business decision which affects millions based on a tally of pro and con comments posted by 5 or 10 or even 20 people.

Decisions are typically made behind the scenes, using a wide variety of resources such as working with advisors, varoius in-person focus groups, and by data mining statistics such as tracking browsing habits throughout DaniWeb.

For example (a completely arbitrary and theoretical example, mind you), suppose 15 people say they love the navigation drop down menu and 1 person complains about it saying it's terrible. Navigational statistics might prove that only 15% of DaniWeb's audience uses the navigation menu while the remaining 85% go out of their way in their browsing habits to avoid it. In such a case, tracking the patterns of millions upon millions of visitors tells a better tale than 16 comments posted.

Public feedback from members is very important because it adds real voices to the numbers. For example, in the scenerio above, it's clear from the data collected that the navigation menu isn't working and so first instinct might be to remove it because it's doing damage when so many people alter their browsing habits just to avoid it. However, even though 15 people posted that loved the menu, the one person who didn't like it might have posted what he didn't like about it. That one post of feedback might influence a change to be made to the navigation menu to where the majority of website visitors now use it regularly. Had I not been paying close attention to statistics, and simply relied on public feedback first and foremost, I would have thought that the navigation menu was working just fine and just one person wasn't crazy about it. In that way, statistical data and public feedback work together to influence decisions.