next message in archive
next message in thread
previous message in archive
previous message in thread
Index of Subjects
Index of Subjects Doug, I think there might be other, non-client side, solutions. What I mean is non-Javascript. While I used to be a heavy user of Javascript, I've cut back because client side applications can be unperdictable. In fact not too long ago I had written a piece of perfectally viable Javascript code, and yet it would crash (something Javascript should be incapable of doing regardless of what the code is) Netscape 4 / WinNT, and only that. Now the only place I use Javascript would be in a frame, and I would try and keep it to Javascript 1.0, that way the only browsers that would see the code (Netscape 2+ or equiv.) would be able to handle it. One of the reasons that we used SSI in the new template is so system wide changes would be much easier; it may also prove to be a valuable tool in our current situation. Since all documents that use the template are generated partially on the fly, and they all use the same source files (which contain the body and table tags). Implementation of a change in colour could be done with a few keystrokes now, and we could continue discusion of a more versitile solution with at least a temporairy fix in place. One solution that would utilise our already-in-place SSI would be to have a script generate the body tags based to cookies retrieved from the user (Lynx has some, although limited, support for cookies, but that's beside the point). This way, we could have a custimization page that would send a cookie that would stay with the user visit after visit. But for the time I agree that we should move forward with a temporary solution. Johnathan Thibodeau On Sun, 30 Jul 2000, Douglas J. McCann wrote: > Hi David > > Further to my previous message, there are other design considerations that > should be addressed. The new template does not take advantage of other > browser functions that would improve the overall appearance and > functionality of the web page. > > Hover functions. > Graphics and other objects can display additional information when the > cursor 'hovers' over the object. See > http://www.chebucto.ns.ca/Chebucto/webmaster/vLink2.htm > > -When the cursor hovers over the CCN logo it displays the message "Serving > Your Community's Online Needs". > > -Over the Preferences object the cursor causes the message "Click to defer > to browser defaults" to appear. > > > For more elaborate messages, cursor control (style function) can change > the cursor from an arrow to a question mark. On click, an alert box can be > displayed, or a new informational page displayed. > > -Over the title "Chebucto Community Net" the cursor changes to a (?). > Clicking on the title launches a popup window providing CCN details. > > -Over the title "Webmaster" the cursor changes to a (?). Clicking on the > title displays an alert box. > > > > Default Background > This discussion began with allowing users to take advantage of their own > browser vlink and link defaults. However, there are other browser > defaults such as text size and background colour. > > If users have selected a background colour that is non-white, then our > page turns ugly. Various areas have table cells, where the background > colour is set to white. For example, in vlink.htm set the background > colour to grey. Then try the same thing in vLink2.htm. > > http://www.chebucto.ns.ca/Chebucto/webmaster/vLink.htm > > http://www.chebucto.ns.ca/Chebucto/webmaster/vLink2.htm > > > The solution to this problem is to not force cell background colour. > > <TD bgColor=#ffffff height=29 width=477> </TD></TR> > <!--second row--> > > <TD height=29 width=477> </TD></TR> > <!--second row--> > > > > Transparent Gifs > To correct for background colours and gif files, the gif background colour > must be set to transparent. > > > > So, while on the surface the new template looks good, there are many > design elements that were not considered before implementation. I think > it is incumbant on all our volunteers to review the template and present > their observations. Otherwise, we will be continuously 'adjusting' the > template, and redoing past efforts. > > > > Doug McCann > > On Sat, 29 Jul 2000, David L. Potter wrote: > > > > > Hi Doug... > > > > I've not bumped into this before... or at least not noticed it on other > > sites... as an individual surfing along and finding myself on a page > > such as the webcam page (for example) how would I know that I could > > change the colours... and how would I do it (especially if I was > > having trouble with the colours)? Would I have to be a 'regular user to > > know/be bothered to invoke it... as a one time or ocassional web visitor > > would I bother to change the interface or just leave in frustration...? > > > > Even if all of those questions have a positive answer, I not sure I see any > > significant benefit. From a design perspective, our 'known look and feel' > > only works if the individual has 'normal' vision, for all others, the > > look and feel is 'unknown'. > > > > If we design our pages to display well with the browser defaults (this > > becomes our known look and feel) then I would say we've done our job... > > whatever the user wants/needs to see should really be left to them should it > > not...??? > > > > As a fundamental design principle, I'm not sure that it makes a lot of > > sense to me for us to settle on an interface design that is known to give > > our users/visitors problems...? I would think that would qualify as a > > fundamental flaw in the the design. In the least, if there is a need for > > 'work-a-rounds' to accomodate individuals with a disability it would be a > > stretch to consider it a 'friendly' site. > > > > dlp > > > > > > > > On Sat, 29 Jul 2000 aa935@chebucto.ns.ca wrote: > > > > > Hi David > > > > > > By imbedding a user interface option creates an environment where CCN can > > > create a web page with a known look and feel, but also permits users to > > > customize the page to meet individual requirements. > > > > > > If we use the general default options, then CCN pages will have an unknown look > > > and feel. For example, we have a light blue <td bgColor=#deeee1> trim. If a > > > user were to set their default vlink to the same color then a followed link > > > would 'disa