0

I've noticed a few recent changes, which are of course somewhat annoying.

1. Sometime overnight, my option "Disable Clientside Scripting Enhancements" got reset, so this morning, everything is popping up like crazy. It's all right now, but I had to remember which box I ticked some time ago.

2. Double clicking on a folder to mark that forum as read now causes a page refresh. Very annoying if you're trying to mark several forums as read in quick succession.

3. Having gotten used to the "Forum tools" at the top of the page just bringing up a menu, I now have to deal with a jump to the other end of the page. Is the top link actually worth anything any more?

11
Contributors
35
Replies
36
Views
10 Years
Discussion Span
Last Post by WaltP
Featured Replies
  • 1
    John A 1,896   10 Years Ago

    [QUOTE=cscgal;424767]If I didn't work to continually improve upon DaniWeb, we would still be the small technical support forum for just Windows and Mac that we started as. If it wasn't for all of the evolutions and new innovations of the site, the C and C++ forums, where you spend most … Read More

0

Hi,

1.

If you remember, the option to disable the various JavaScript style elements was temporarily added to help debug all of the extremely slow page rendering and JavaScript timeouts that were being spit out when I updated the look of DaniWeb a couple of months ago.

Narue and others were experiencing timeouts where their web browsers would seemingly hang, but I didn't know what was causing them. So to help figure it out, I added the option to turn off each of the JS elements one at a time:
Turn off rounded corners
Turn off dropdown menu
Turn off hover tooltips

It turns out that, for all members who were complaining, it was the rounded corners that were the culpreit. The hover tooltips and dropdown menu don't cause any browser slowness.

In doing a quick run through the database, I noticed that the vast majority of members had disabled "rounded corners". Very, very few (fewer than 10) disabled one, or both, of the other two options.

Therefore, I went ahead and permanently turned off the rounded corners option yesterday, and so there was no reason to have this option in the control panel anymore. I don't feel there is a need to clutter up the control panel for just 10 out of 200,000 members.

However, in its place, I did add an option to disable ALL JavaScript, DHTML, and AJAX on the site in one massive swoop. This is useful to those with slower computers who just want quick forum browsing without all of the dynamic bells and whistles that slow down their web browsers. Not only does it disable the dropdown menu and hover tooltips, but it also disables all of the other dynamic-like forum features, such as AJAX quick reply (when things change without having to refresh the page), etc. It is nearly exact to the way that CProgramming is currently set up.

2.

Without AJAX (Asynchronous JavaScript and XML), JavaScript is no longer used to let you interact with the server without having to refresh the page. Therefore, you can no longer double click on a folder icon and have something be changed in the database without reloading the page.

3.

Without DHTML dropdowns, the links are located at the bottom of the page. Clicking on the Forum Tools link at the top now scrolls you down the page to where they're located. This is the same way that CProgramming does it.

Cheers,

Dani

0

Damn it, my spellchecker has got disabled again. I don't know why but any changes made to anything related to Javascript messes up with the spellchecker big time.

I guess the three options being merged into one is the cause of this.

0

I'm sorry, but I'm still incredibly confused how the SpellChecker is related to anything. I don't have any suggestions for you at this time.

0

~s.o.s~ is right, the spellchecker is now automatically disabled within the WYSIWYG editor. If you switch to plaintext mode, however, it comes back. I'm using Firefox.

0

I believe this is the problem that people were experiencing in the past. I'm not sure, as I don't use Firefox or a spell checker.

0

I don't post anymore... but I do occasionally browse. The floating popups are very annoying, like having tape stuck to your fingers. Please reinstate the option to disable popups.

0

Hi,

1.

If you remember, the option to disable the various JavaScript style elements was temporarily added to help debug all of the extremely slow page rendering and JavaScript timeouts that were being spit out when I updated the look of DaniWeb a couple of months ago.

Part of it was also there to get rid of that maddening bumble box that follows the cursor around. It is now annoyingly BACK!

I want the hover tooltips GONE!!!!!

Narue and others were experiencing timeouts where their web browsers would seemingly hang, but I didn't know what was causing them. So to help figure it out, I added the option to turn off each of the JS elements one at a time:
Turn off rounded corners
Turn off dropdown menu
Turn off hover tooltips

It turns out that, for all members who were complaining, it was the rounded corners that were the culpreit. The hover tooltips and dropdown menu don't cause any browser slowness.

No, but the hover tooltips just drive you crazy with visual interrupts.

[In doing a quick run through the database, I noticed that the vast majority of members had disabled "rounded corners". Very, very few (fewer than 10) disabled one, or both, of the other two options.

Therefore, I went ahead and permanently turned off the rounded corners option yesterday, and so there was no reason to have this option in the control panel anymore. I don't feel there is a need to clutter up the control panel for just 10 out of 200,000 members.

Dani

I want the dropdowns, but hate the tooltips.

0

Firefox has a built in spellchecker. But it won't work with the whizzywig editor. And somehow my account keeps getting changed back to whizzywig without my permisssion.

And I detest the bumbling tooltips.

0

by tooltips do you mean the thread preview that follows the cursor around on the menu page ? Yes I don't like that either and find it not at all useful when there is more than 1 post in the thread. Its just annoying.

0

I think Dani is the only one who likes it.

To turn that stupid annoying thing off, I had to disable the dropdowns, which I liked. It made the site much harder to navigate.

-1

I don't post anymore..

Hmmmm it must have been a ghost that made this post with your account then :D

Votes + Comments
I knew some idiot would post this kind of off-topic nonsense. You win.
0

I turned everything off a long time ago. It seemed like the safest ploy.

Somehow, each "nice" new feature also comes with some "nasty" elsewhere. The "ooh ahh" crowd might be able to take the pain, but I can't.

No other forum I visit has this constant churn in the user interface experience. This is a site to enable people to communicate, not some continual beta site to test the admin's web programming skills. If this were a downloaded program, and the UI was changing with each patch, you'd be losing customers faster than you could patch it.

I get into a mode where I know where everything is (eg. how to mark a forum read). Along comes a change, and I have to re-learn the UI sequence.

Every time I detect a change, I seem to spend (aka waste) a few hours wondering what else has changed.

Yet another example of what I would regard as useless tinkering.
http://www.daniweb.com/forums/forum6.html
Now some threads are labelled "Multi Page Thread", as if "1 2 3 4 5" wasn't bleedingly obvious enough.

Personally, I think it's about time there was a lot more transparency from the admins. For example, each change which might affect the UI experience of ANY member (no matter what options they've ticked), the change should be announced in a forum message with due notice.

All this "well the majority won't notice anything" argument doesn't wash, because the majority still have the options given to them. It's only the people who've been here a while (coincidentally, all the people who provide all the help) who've figured out that such options exist and have chosen to make some changes.

Oh, and FYI, I have all these things turned off, yet I still get a regular crop of "The server at www.daniweb.com is taking too long to respond." I even got one composing this missive.

0

>>Now some threads are labelled "Multi Page Thread",
I don't see that. Maybe its the way you have it set up in Control Panel ? I have Thread Display Mode set up as "Linear - Oldest First"

0

Actually, neither do I any more.

It seems that because DW was being so damn sluggish that by browser was displaying the "alt" text for the little graphic symbol immediately to the left of the numbers.

I withdraw that particular observation as being down to server lag.

0

Firefox has a built in spellchecker. But it won't work with the whizzywig editor. And somehow my account keeps getting changed back to whizzywig without my permisssion.

And I detest the bumbling tooltips.

I installed firefox 2.0 and the spell checker works with the editor for me.

0

It works now, because the whizzywig editor is now gone.

But to get rid of the bumbles, I had to get rid of the dropdown menus, so I have to scroll to the links, so the no-scroll bug stops me until the ad stops moving. And there are some ads that don't stop moving.

And now I can't tell which smiley I am getting, because the menu shows the text, instead of the smiley. Then the wrong one shows up.

0

Salem,

Thank you for your comments. I'm going to quickly respond to some of the points which you brought up.

(1)

If I didn't work to continually improve upon DaniWeb, we would still be the small technical support forum for just Windows and Mac that we started as. If it wasn't for all of the evolutions and new innovations of the site, the C and C++ forums, where you spend most of your time, and the entire software development category, for that matter, wouldn't even exist. To highlight some of the most recent changes, the reputation system would still be in its default buggy behaviour and there would be no way to browse through threads in a forum without having to hit the back button continuously.

In fact, all of the changes that have been made within the past months have certainly not been done just to "test my web programming skills" but instead come as either a direct request or need from the community, based in large part from feedback here in this forum. The changes made this month, for example, which include the similar threads feature, the behaviour of tooltips, the reputation system, the redesign of the blogs pages to more prominently feature member usernames and the blogs the entries belong to, the addition of syndication buttons, have ALL come as a result of feedback passed to me by members.

It's important to note that there are 200,000 members. Even if you only look at members who post on a regular basis, that's still over 2,000. Of course not everyone is going to like all of the changes or hate all of the changes. There might be a new feature that you like and someone else might hate. And then there might be a different new feature that you hate but someone else likes. My goal is to make the majority feel that, when looking at the overall picture, there are more things you like about the site than you dislike.

(2)

You mentioned receiving a "This server is taking too long to respond" message on a regular basis, in addition to sluggish behaviour in general (such as with the 'Multi-post' icon not being displayed).

One of the recent problems that we've been faced with is that of MySQL table locking. What this means is that, while lots of people can all read from a single table at one time, the table has to be temporarily locked each time a change is made to it. As DaniWeb grows, this causes problems because while, on average, we will have 2,000 people at once trying to read from the post table, everytime someone wants to make a new post, the INSERT sql query has to wait in line for all of the existing reads to finish up so it can gain temporary sole access to the post table to insert a new post. This is why it's been taking a long time when posting lately.

Another problem we've been faced with lately is a Denial Of Service attack over the last couple of days / week.

To combat these problems, just yesterday we upgraded to four brand new servers after nearly a month of planning and a week of setup. The problems you experienced yesterday were most likely due to you trying to access DaniWeb in the middle of the migration. Because this was meant to be an uneventful migration with very limited downtime (there was about a half hour in total when the website was replaced with a 'site currently unavailable' message while the database was being moved to its new home), the messages about the move were confined to Area 51 instead of publically.


That being said, do many of you agree with Salem regarding changes to DaniWeb being far too constant and making the UI have a steeper learning curve than it should?

0

> But to get rid of the bumbles, ...

Midi, the "bumble-bee" behaviour of the tooltips following the mouse cursor around no longer happens. The tooltips now work the same way that they used to pre-a couple of months ago when their so-called "bumble" behaviour was introduced.

0

Just to add ... we've now moved our most-updated tables, such as the post table, to MySQL type InnoDB as opposed to MyISAM. InnoDB uses row-level locking as opposed to table-level locking and therefore won't succumb to the locking problem we were experiencing with new posts. The reason it was just implemented is because it does use up more system resources, and therefore I was waiting for the move to a more powerful server.

0

Instructions for upgrading server:

1. Place old system in Cuisinart.

2. Turn on "liquify" for 30 seconds.

3. Pour into new server.

:icon_mrgreen:

-----

Some of the edit windows are showing a list of icon codes instead of the actual icons.

Some edit windows allow the whizzywig editor, and some don't. I thought it was gone.

0

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. And the editor selector was missing.

0

If I didn't work to continually improve upon DaniWeb, we would still be the small technical support forum for just Windows and Mac that we started as. If it wasn't for all of the evolutions and new innovations of the site[...]

Would you consider a "Release Notes" thread in which we can look for a brief summary of recent changes, over time, and maybe a small comment as to the goal/reason?

I wouldn't even mind if it was only writable by y'all. But at least somewhere to look when something "suddenly" seems to be unexpected behavior for those that may already have familiarity here.

0

Every change made is mentioned in either this forum or within Area 51. Changes which affect the majority of our audience I discuss here. When I want to have more elaborate behind-the-scenes discussions, or changes that typically affect only the regular members, are discussed in Area 51.

Sometimes I won't go into a ridiculous amount of detail with each and every thing. But I will definitely post something such as, "I've just redone the look of the blogs page. Tell me what you think!" I might also get into detail such as, "I've just redone the look of the thread pages today by moving the 'Mark as Solved' link towards the bottom of the page near the quickreply instead of the top, because it's more intuitive there, since someone is only going to mark a thread as solved after they've finished reading the thread and saw their question was answered."

0

Something I'm used to:

Attachments
Changes for version 1.0-RC2
-------------------------------

2005-10-24  mandrav

	* Fixed wxWidgets templates

2005-10-24  byo_spoon

	* Added InitDialog event handler
	* Fixed some bugs related to event handlers

2005-10-24  byo_spoon

	* Fixed dialog-initializing code generation (now using Create()
	  instead of constructor)
	* Fixed bug with crashes after configuring wxSmith
	* Addef Fit() and SetSizeHints() methods to code generated by sizers

2005-10-24  mandrav

	* Fixed a small bug in PluginWizard's generated code.
	* Fixed selecting directories when adding paths in global compiler
	  options.

2005-10-24  ceniza

	* ODT Exporter added.
	* The exporters now inherit from BaseExporter.

2005-10-23  mandrav

	* Fixed debugger plugin not working correctly with unicode wx.

2005-10-23  mandrav

	* Updated new splash screen

2005-10-22  byo_spoon

	* update.bat will put all resources also into output directory

2005-10-22  ceniza

	* Ampersand now written as & in the HTML Exporter

2005-10-22  ceniza

	* Fixed background color bug in the HTML Exporter

2005-10-22  byo_spoon

	* Changed options to generate precompiled headers automatically

2005-10-22  mandrav

	* Added explanation string in file options dialog, regarding
	  "Priority weight" setting.

2005-10-22  byo_spoon

	* Added support for precompiled headers

2005-10-21  mandrav

	* Updated Makefile.am for "StartHere" page resources

2005-10-21  mandrav

	* Added some eye-candy (courtesy by Thomas)

2005-10-21  mandrav

	* Updated wxWidgets templates. Added support for unicode builds and
	  a precompiled header.

2005-10-21  mandrav

	* Finally fixed honouring the "compile" and "link" unit flags when
	  loading a project
	* PluginWizard now asks to create and save the new project *after*
	  the dialog has run

2005-10-21  mandrav

	* Removed reference to stc.h in PCH files
	* Fixed a typo in tips.txt
	* Removed obsolete menu entry "View->Manager position"

2005-10-21  byo_spoon

	* Fixed bug when generating localized characters (ASCII > 0x80) in
	  code

2005-10-21  ceniza

	* Added RTF Exporter

2005-10-21  ceniza

	* Changed a tab to spaces

2005-10-20  byo_spoon

	* Fixed some bugs (seg-faults)

2005-10-20  mandrav

	* Bug fix: when adding files in project, only mark as "compile/link"
	  the right kind of files (was broken from PCH support)

2005-10-20  mandrav

	* Fixed certain context menu entries not working in project manager
	  and class-browser.

2005-10-20  mandrav

	* Fixed bug when opening a workspace by double-clicking in explorer.
	  Would open the workspace, close it and re-open it. Pointed out by
	  tiwag.

2005-10-20  mandrav

	* Added PCH support in contrib plugins.

2005-10-20  mandrav

	* Bug fix: when adding a new header file to the project, by default
	  don't make it compile/link.
	* Bug fix: when setting a header file as compilable (e.g. PCH), make
	  sure it has been assigned a valid compiler variable.

2005-10-20  mandrav

	* Fixed a possible bug in cbThreadPool::FreeThreads() implementation
	  (patch by Thomas)

2005-10-20  mandrav

	* When using "Go to line", ensure destination line is not currently
	  fodled or, if it is, unfold it (feature #1329422).

2005-10-20  mandrav

	* Added "Save project" menu entry under "File", to avoid confusion
	  for users (bug #1323196).

2005-10-20  mandrav

	* Bug fix: correctly remember position and size when closing the app
	  while minimized (bug #1324114).

2005-10-20  mandrav

	* When message pane is set to auto-hide and is hidden, when unset in
	  env. options show the message pane again.

2005-10-20  mandrav

	* Fixed bug with refreshing custom vars in compiler options, when
	  changing compiler (bug #1327769)

2005-10-20  mandrav

	* Fixed freeze bug on closing a project (related to thread pool)

2005-10-19  mandrav

	* Fixed wrong cast of void* to integer in parser.cpp (broke build in
	  64-bit CPUs)

2005-10-19  mandrav

	* Added precompiled header support in unix build system

2005-10-19  mandrav

	* Fixed broken src/src/printdlg.h (from last PCH commit)

2005-10-19  mandrav

	* Added precompiled headers (PCH) support :)

2005-10-19  byo_spoon

	* Fixed bugs with colours/font of main resource's window

2005-10-17  ceniza

	* Now uses current font type and size, and also background color.

2005-10-17  mispunt

	* fix unicode support in wxSafeShowMessage

2005-10-17  byo_spoon

	* Small bug fixes

2005-10-17  mandrav

	* Added a mutex lock in Parser::Clear() (would lock-up if more than
	  one projects were open).
	* Added exception handling in more places, regarding plugins.
	* Added new contrib plugin ("source_exporter") to export open file
	  to HTML (authored and maintained by Ceniza).

2005-10-16  zlika

	* Increased robustness of the parser

2005-10-16  mandrav

	* Added cbEditor::GetColorSet().

2005-10-16  byo_spoon

	* Fixed problems with static line widget and some small bugs

2005-10-14  byo_spoon

	* Fixed some bugs in dragging system, added some features

2005-10-14  mandrav

	* Removed a superfluous mutex locking in parser (may have caused a
	  deadlock on shutdown).
	* Implemented search in arbitrary paths/filemasks for find-in-files.
	* Enabled "Search->Find" when no project is open, to allow searching
	  in files.

2005-10-14  mandrav

	* Fixed ugly bug when auto-wrap for search was enabled and the found
	  text was deleted before wrapping around.
	* Implemented quick and ugly hack for certain compilers static lib
	  creation (bcc, dmc) that need a + or - sign in front of every object
	  in the link command. New compiler macros added for this:
	  $-link_objects, $+link_objects, $-+link_objects and $+-link_objects
	  (adding the respective symbols between $ and link_objects).

2005-10-14  rickg22

	* Fixed freeze-on-startup (99% CPU) bug. Added more debug messages for
	  the parser.

2005-10-14  byo_spoon

	* Fixed bugs when adding new resources

2005-10-13  byo_spoon

	* Improoved visual interface

2005-10-13  byo_spoon

	* Added Dragging assistance Added plugin configuration dialog

2005-10-12  byo_spoon

	* Added settings dialog Linux bug fixes

2005-10-12  byo_spoon

	* Fixed linux post-build script (icons are now copied properly)

2005-10-12  byo_spoon

	* Fixed some linunx-compatibility problems

2005-10-11  byo_spoon

	* Fixed some bugs in dragging routines

2005-10-11  byo_spoon

	* Improoved dragging routines

2005-10-10  byo_spoon

	* Improved preview picture fetching system (removed many visual
	  artifacts)

2005-10-10  byo_spoon

	* Fixed bugs in drag window

2005-10-10  mandrav

	* Re-uploaded the correct glfw.png template icon

2005-10-10  mandrav

	* Removed broken glfw.png template icon

2005-10-10  mandrav

	* Added GLFW project template (by Thomas Denk).

2005-10-09  mandrav

	* Updated setup files

2005-10-09  mandrav

	* Fixed build log's background color to respect system settings
	  (partly, patch #1318460 by Paul Mandalka)

2005-10-09  mandrav

	* EditorBase::Saved() is now actually called.
	* PluginManager now logs an error in the debug log if it can't load
	  a plugin, instead of displaying a message.

2005-10-07  mandrav

	* Added editor configuration option: auto-wrap search when EOF
	  reached (patch by tiwag).
	* Display the active editor's full filename in the status bar (patch
	  by tiwag).
	* Correctly update active editor's column/line when switching editor
	  tabs (patch by tiwag).

2005-10-07  mandrav

	* Fixed wrong tooltip in code-completion plugin's cache settings

2005-10-07  mandrav

	* Fixed order of projects being added as source dirs for the
	  debugger (bug #1281125).
	* Added debugger configuration option, whether to add the other open
	  projects (if any) as search dirs (bug #1281125).

2005-10-07  byo_spoon

	* Fixed some bugs Started to improove widget-dragging routines

2005-10-07  mandrav

	* Fixed UI glitch in find-in-files (the editor that performs the
	  search, that should be invisible)
	* Display a progress bar while the find-in-files search is performed
	  because it can take some time (rfe #1252189).

2005-10-07  mandrav

	* Added EditorBase::OnBeforeBuildContextMenu() and
	  EditorBase::OnAfterBuildContextMenu() which are called before and
	  after (respectively) context menu creation. Used in cbEditor to move
	  the caret to where the mouse cursor is, before creating the context
	  menu. This is because some menu entries scan the word under the
	  cursor and without this, it needed first a left click on the word in
	  interest and then a right click. Now it's done in a simple
	  right-click. This also implements RFE #1264036.

2005-10-07  mandrav

	* Allow multiple files selection when adding link libraries (rfe
	  #1290628).
	* Remember last directory when opening dialog for dir selection (rfe
	  #1294446 ).

2005-10-07  mandrav

	* Fixed check for externally modified files not to check files just
	  created and are still in the SaveAs dialog (bug #1303774)

2005-10-07  mandrav

	* Fixed find and replace dialogs to keep extra spaces in saved
	  history (bug #1305208)

2005-10-07  mandrav

	* Added extra parameter "trimSpaces" in GetArrayFromString()
	* Removed cbPlugin::GetSDKVersionMajor() and
	  cbPlugin::GetSDKVersionMinor() (moved inside following macros).
	* Added CB_DECLARE_PLUGIN() and CB_IMPLEMENT_PLUGIN(name) to ease
	  the plugin binding.
	* Updated all plugins in CVS to use the above macros.
	* Fixed code generated from PluginWizard to comply to the above
	  changes.
	* Fixed warnings in code generated from PluginWizard for
	  cbProjectWizardPlugin plugins

2005-10-07  mispunt

	* fix unicode support.

2005-10-07  mandrav

	* Updated plugin manager's messages when a plugin fails to load.
	* Fixed crash when adding to-do item at EOF and selecting to add it
	  in "New line below current line" (bug #1300981)

2005-10-06  mispunt

	* Fix co
0

That's definitely by all means standard for software. However, when was the last time you saw google.com or digg.com or cnet.com or any other large website for that matter publically release such a document? The answer: they wouldn't.

1

If I didn't work to continually improve upon DaniWeb, we would still be the small technical support forum for just Windows and Mac that we started as. If it wasn't for all of the evolutions and new innovations of the site, the C and C++ forums, where you spend most of your time, and the entire software development category, for that matter, wouldn't even exist. To highlight some of the most recent changes, the reputation system would still be in its default buggy behaviour and there would be no way to browse through threads in a forum without having to hit the back button continuously.

I think Salem's point is that changes shouldn't be exactly real time. No one's denying the fact that without your hard work DaniWeb wouldn't be where it is today. But one thing I would really enjoy is if you 'packaged' your changes.

Here's an example of a minor annoyance of 'tweaking': I frequently visit the forum index after reading a subforum to check if any of the threads I've just replied to have been updated. I think at first there was a link that said something like 'Forum Index' in the breadcrumb. When I searched for it one day, it wasn't there. Then it said something else when I reloaded the page. I reloaded again, and it said 'Forums'. It's not a huge issue in that case, but it's something I use frequently. Now there's no link at all, so I'm forced to use my bookmark to do it.

I know it's been suggested before, but a beta.daniweb.com would, in my opinion, be a vast improvement. You'd get a good idea of what kind of feedback you'll receive when you release it to the public, you could select users to test out your new changes, and once you've as many bugs as you can ironed out, release it. For users, it would mean learning the updated UI less often.

Votes + Comments
...couldn't have put it better myself.
This question has already been answered. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.