The Drop Down Menu System

[Michael Morris]

Ok, I've been working for 2 months to mod Post Nuke into allowing the inclusion of the drop down menus seen on the Dusk site (www.thedusksetting.com). I've asked Russ allow me to implement them there.

Now the next trick is to implement them here - I'm analysing VBulletin's code, but I can't download it to run a seperate version on my home system to test the hack.

This reduces me to making educated guesses on what to change, backing up the original PHP file, implementing them and seeing what happens. The worst that could happen is the page will freeze or refuse to load unexpectedly. The messages themselves won't be affected unless you are caught sending one at the same time I switch a PHP file.

The longest possible downtime due to this would be 3 minutes.

Of course a better solution is for me to get a version of VBulletin 3.0 I can test locally, and if this is possible I would prefer to do these tests locally. Even after the tests are done, there is a slight possibility of service disruption.

I don't need admin status to conduct these changes - they are all code side and only require the FTP access I have now to conduct and implement.

Anyway, I welcome feedback on this from all who will be affected.

 

[DanMcS]

Why? What do these menus add that we don't already have?

I'm skeptical of change just for the sake of change. Particularly something that will probably add more processing time to all these dynamic pages, and the server was apparently having problems handling load in the afternoons last week. That may not have been a bottleneck at the http server, but still.

What's the business case for these changes? What do they add that users are demanding? If it ain't broke, don't crash my favorite online hangout

 

[DanMcS]

OK, so I've looked at the dusk site, and they're just those mouseover drop-down things admins seem to be enamored of today. I don't really like them.

1) They rely on javascript to provide this functionality, but not all browsers implement javascript correctly or the same. People running a different browser than what you've tested with, or who turn of javascript for whatever reasons, may not be able to use the site at all.

2) You seem to have completely eliminated regular links to those other pages, in favor of the drop-down menus. That's bad for the reason in 1, and also, it's inaccessible to disabled people whose browsers don't handle javascript hijinks well. You should never completely get rid of regular links.

3) Dropdowns are a nonstandard interface to a webpage. Webpages use links. Everyone knows them and how they operate. On the other hand, pages that use these dropdowns are all implemented somewhat differently, and users don't know what to expect. Simple interfaces are better.

4) They're buggy- if I accidentally pass my mouse over the menu header on that page, it doesn't disappear when I remove my mouse from the area and go back over the regular page. It's a pain.

5) You're potentially creating a lot of work for yourself. These are nonstandard with VBB pages, so when Morrus et al upgrade the version of VBB they're using again, whenever they do, you're going to have to reimplement them basically from scratch again.

If you're serious about putting these here on the regular site, make them an option which can be toggled in the user command post, swapping with regular links.

 

[Tallok]

The longest possible downtime due to this would be 3 minutes.
.

3 minutes? I can't survive that, don't do this to me! Augh!

 

[Michael Morris]

OK, so I've looked at the dusk site, and they're just those mouseover drop-down things admins seem to be enamored of today. I don't really like them.

Can you propose a better system to organize and display 77 links?

1) They rely on javascript to provide this functionality, but not all browsers implement javascript correctly or the same. People running a different browser than what you've tested with, or who turn of javascript for whatever reasons, may not be able to use the site at all.

Incorrect. Netscape 4.0 is the latest browser that chokes the chicken on the code. It loads the image, but the drop downs don't appear. I've checked this script and it works on Netscape 5.0 or later, IE 3.0 or later, Opera 3.0 or later, and all versions of Safari. The browsers it wouldn't behave on load the image and then nothing happens on the news page.

As to this page, if you're posting here, your browser *will* run the code. The interface you use to type this message in is JAVAscript driven.

2) You seem to have completely eliminated regular links to those other pages, in favor of the drop-down menus. That's bad for the reason in 1, and also, it's inaccessible to disabled people whose browsers don't handle javascript hijinks well. You should never completely get rid of regular links.

Dusk isn't the main ENWorld site, so why should it have all the ENWorld links?? The drop down menus are there because it gives site continuity to the whole site without crowding up the rest of the page. Major corporations with multiple product lines use these dropdowns for that reason - Take a look at WotC's site for a better example of how it affects global site design.

As I pointed out the first time this debate came up, this isn't a plan to "get rid" of existing links - it is a supplement to the existing system. In many cases it provides links where none currently exist.

As to the handicap argument - again - if they're on this board, they're browser will process the script. The functionality of the news site won't be affected - indeed the menus will restore some links already taken down to trim the crowding that was occuring. You're also complaining about removing many links that aren't even ON the messageboards - just the news site. Vis a vis the news site doesn't have a link to each individual forum.

3) Dropdowns are a nonstandard interface to a webpage. Webpages use links. Everyone knows them and how they operate. On the other hand, pages that use these dropdowns are all implemented somewhat differently, and users don't know what to expect. Simple interfaces are better.

I prefer to give other people more credit for intelligence than that. And if you think drop down menus are more simple lets see you design a 77 link scheme - fit it on ONE page and leave room for other content. And when I say one page, I don't mean a left hand column that runs down for 4 screens.

4) They're buggy- if I accidentally pass my mouse over the menu header on that page, it doesn't disappear when I remove my mouse from the area and go back over the regular page. It's a pain.

It is set to dissappear 3 seconds after mouse out. The reason for this is if you are on a daughter menu of a daughter menu of a daughter menu you don't necessarily want it to dissappear if your mouse comes off the menu for a split second.

5) You're potentially creating a lot of work for yourself. These are nonstandard with VBB pages, so when Morrus et al upgrade the version of VBB they're using again, whenever they do, you're going to have to reimplement them basically from scratch again.

Most of the VBulletin updates are on the backend of the code. Once I figure out how to get the code to work once, it shouldn't be too hard to reimplement it. Besides, software changes are fairly rare due to board disruption.

If you're serious about putting these here on the regular site, make them an option which can be toggled in the user command post, swapping with regular links.

WILL NOT HAPPEN. Russ has already stated that. If they are implemented, they will be implemented in full.

 

[Michael Morris]

Why? What do these menus add that we don't already have?

I'm skeptical of change just for the sake of change. Particularly something that will probably add more processing time to all these dynamic pages, and the server was apparently having problems handling load in the afternoons last week. That may not have been a bottleneck at the http server, but still.

What's the business case for these changes? What do they add that users are demanding? If it ain't broke, don't crash my favorite online hangout

Two lines of code, properly placed, are all that are required for Post Nuke. Should be the same for VBB. The first time the script loads it may take a moment for dial up since the script is 50 K, but once loaded it is cached and never reloads.

The case for the change was stated succinctly the first time this was debated (Which was greenlighted until the difficulty of the implementation became known). In brief, it will help bring the site together as a unit and make it easier to jump between the various pages. Right now there is only 1 link from news over to forums and vice-versa, and the news link to here is kinda small.

While it is good to be honestly skeptical of change, it is also dangerous to resist change on the basis of it being new.

I'm biased somewhat on this - I've been working, on and off, to get this feature up for the boards since April.

 

[DanMcS]

Can you propose a better system to organize and display 77 links?

You don't need 77 links. For instance, the "Community" and "D20 Guides" menus basically deep-link into enworld.org. A single link there would suffice. There's a lot of complexity here that isn't totally necessary.

As to this page, if you're posting here, your browser *will* run the code. The interface you use to type this message in is JAVAscript driven.

No it's not. There's a link at the bottom of each message which goes to, for example, "forums/newreply.php?do=newreply&p=1222283". That's a link to a server-side created page, no javascript involved. I have posted in the past to these boards with a text-only browser that doesn't even recognize javascript.

WILL NOT HAPPEN. Russ has already stated that. If they are implemented, they will be implemented in full.

Then don't add them. It's overengineered for the issue here.

Edited, you answered some of my questions in your second reply.

 

[Michael Morris]

No it's not. There's a link at the bottom of each message which goes to, for example, "forums/newreply.php?do=newreply&p=1222283". That's a link to a server-side created page, no javascript involved. I have posted in the past to these boards with a text-only browser that doesn't even recognize javascript.

That, sir, is a lie. I've seen the PHP code for the new messages. It uses JAVAScript. There's no away around JAVAscript or JAVA if you are to do a data entry field longer than one line.

Then don't add them. They're unnecessary.

That's your opinion. State it as such and don't phrase it as an order.

I think they are necessary to improve site navigation. If I didn't, I wouldn't have spent 6 months working on this. I hope that counts for more than your attitude problem with improving technology. I hate to break it to you, but the Commodore PET wasn't a very good computer.

 

[DanMcS]

Two lines of code, properly placed, are all that are required for Post Nuke. Should be the same for VBB. The first time the script loads it may take a moment for dial up since the script is 50 K, but once loaded it is cached and never reloads.

Fair enough. But why have a 50K script that can be replaced with a short list of links? Dusk would need a "hosted by (link)Enworld(/link)" type thing, which is enough to get to the main page, and from there, there should be links to, for example, the boards, the reviews, a list of hosted sites, etc.

The case for the change was stated succinctly the first time this was debated (Which was greenlighted until the difficulty of the implementation became known). In brief, it will help bring the site together as a unit and make it easier to jump between the various pages. Right now there is only 1 link from news over to forums and vice-versa, and the news link to here is kinda small.

The link from the forums to the news page is the big logo in the upper lefthand corner.

Site unity, fair enough, if you want to have a standard look across all the sites.

While it is good to be honestly skeptical of change, it is also dangerous to resist change on the basis of it being new.

I'm very rarely accused of being reactionary. But I write software, and I'm skeptical of complexity that isn't completely necessary.

I'm biased somewhat on this - I've been working, on and off, to get this feature up for the boards since April.

I understand. I'm trying to discuss the technical and UI aspects of it, not to critique you.

 

[DanMcS]

That, sir, is a lie. I've seen the PHP code for the new messages. It uses JAVAScript. There's no away around JAVAscript or JAVA if you are to do a data entry field longer than one line.

Well, I can't really prove it, but I just logged into a unix machine, started up lynx, and I'm posting this from a text-only telnet window. So it apparently still works fine. What javascript you've seen is apparently on the server side, and executes there independantly of viewing the page on the client side.

That's your opinion. State it as such and don't phrase it as an order.

I never said it was anything but my opinion.

I think they are necessary to improve site navigation. If I didn't, I wouldn't have spent 6 months working on this. I hope that counts for more than your attitude problem with improving technology. I hate to break it to you, but the Commodore PET wasn't a very good computer.

I'm 24. I never owned a commodore anything. You're taking this really personally, I'm just discussing the technical merits of the menus.