Not really because it cuts into UI design. But i see what you mean, i have it under control.
On Sat, Jun 7, 2008 at 7:14 PM, Darren West <[EMAIL PROTECTED]> wrote: > Cool design, maybe you could reveal the sublnks onClick? then keep the > panel open and repopulate with the relevant links as you move over the > navigation links. > > If you have the time/money in the project, it would be well worth > doing user testing :-) > > We maybe veering away from the purpose of this mailing list > > > 2008/6/6 James Jeffery <[EMAIL PROTECTED]>: > > The same image but with the content and withut the dropdown showing: > > http://img246.imageshack.us/my.php?image=standard01qi5.png > > > > I think it might work without the dropdown. I will have to speak to the > > youth centre manager on Wednesday. > > > > James > > > > On Fri, Jun 6, 2008 at 5:34 PM, James Jeffery > > <[EMAIL PROTECTED]> wrote: > >> > >> Here is an example of the NEW idea: > >> http://img391.imageshack.us/img391/3992/standard01yo8.png > >> > >> This has got me thinking though. If there is going to be a sub > navigation > >> part on every page is there really any need for the dropdown? > >> > >> By adding the dropdown the only benefit the user will get is that they > >> don't have to click twice to get to a section/sub page. For example to > >> access "Maypole Radio" they select other services and click. Without it > they > >> would have to click "Other Services" and select from the static sub > >> navigation menu. > >> > >> I am not sure if its going to be worth it in the end. Obviously the > static > >> sub navigation is going to be amust so that i can cover everything. The > >> Suckerfish menu now seems useless in a way. If i leave it there it may > add > >> extra confusion to the navigation of the website. If you get what i > mean. > >> > >> Cheers for the input so far. > >> > >> James > >> > >> On Fri, Jun 6, 2008 at 5:07 PM, James Jeffery > >> <[EMAIL PROTECTED]> wrote: > >>> > >>> With the pure CSS version, and using Javascript to take care of IE 5, > you > >>> can ensure it will work with browsers with JS disabled. Thats why i > chose to > >>> use the Suckerfish style dropdowns. Also you can add some extra > behvaiour > >>> ontop of the pure CSS menu's. > >>> > >>> I think maybe the best solution would be to display sub link on the sub > >>> pages. Save all the hassle of using conditionals and stuff. I did think > >>> about doing it this way at first but then started wondering about user > >>> experience and possible confusion. > >>> > >>> It's always the simple approaches that tend to be the best. > >>> > >>> Thanks for your support fellow CSS'ers > >>> > >>> On Fri, Jun 6, 2008 at 4:50 PM, Thierry Koblentz <[EMAIL PROTECTED]> > >>> wrote: > >>>> > >>>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > ] > >>>> On > >>>> Behalf Of James Jeffery > >>>> Sent: Friday, June 06, 2008 2:49 AM > >>>> To: wsg@webstandardsgroup.org > >>>> Subject: [WSG] Suckerfish and IE 5 with no Javascript > >>>> > >>>> Maybe i am being a little bit picky with this. > >>>> > >>>> I have a suckerfish dropdown, as i feel it is the best approach for > >>>> cross-browser (but not A grade) dropdowns. The website i am working on > >>>> is a > >>>> youth centre's. The target audience is the community, which can be > young > >>>> or > >>>> very old. The very old "may" be using IE 5 on older computers (at a > >>>> guess). > >>>> If they have JS disabled and are using IE 5 then they cannot view the > >>>> navigation links. > >>>> > >>>> Whats your views on the best way around this? > >>>> > >>>> I was thinking about sing PHP to determine what browser the user is > >>>> using > >>>> and if JS is enabled. If its IE 5 and it is not enabled then when a > user > >>>> clicks a link from the navigation menu the page will load but under > the > >>>> navigation will be another div that lists the links uder that sub > >>>> heading. > >>>> > >>>> ----------------------------------------------------- > >>>> | nav nav nav nav nav nav nav | > >>>> ----------------------------------------------------- > >>>> ---------------------------------------------------- > >>>> | sub link sub link | > >>>> | sub link sub link | > >>>> | sub link sub link | > >>>> ---------------------------------------------------- > >>>> ----------------------------------------------------- > >>>> all the other content goes on as normal > >>>> > >>>> Only users who are using a browser that does not support the hover > >>>> psudeo > >>>> selector on anything other than a elements will see that box. It will > be > >>>> generated using PHP before the page loads. > >>>> > >>>> I was thinking about doing that for all the users, and have that > >>>> displaying > >>>> regardless, but that may add confusion to the user experience i feel. > >>>> > >>>> Anyone ideas? > >>>> > >>>> > >>>> Hi James, > >>>> I have these two: > >>>> http://tjkdesign.com/articles/Pure_CSS_Dropdown_Menus.asp > >>>> > >>>> I believe they are compatible with ie5 Win and Mac > >>>> > >>>> But if you ask me, I'd say the best approach would be to use a good JS > >>>> menu > >>>> rather than a "pure CSS solution". > >>>> > >>>> -- > >>>> Regards, > >>>> Thierry | http://www.TJKDesign.com > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> ******************************************************************* > >>>> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > >>>> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > >>>> Help: [EMAIL PROTECTED] > >>>> ******************************************************************* > >>>> > >>> > >>> > >>> ******************************************************************* > >>> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > >>> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > >>> Help: [EMAIL PROTECTED] > >>> ******************************************************************* > >> > >> ******************************************************************* > >> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > >> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > >> Help: [EMAIL PROTECTED] > >> ******************************************************************* > > > > ******************************************************************* > > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > > Help: [EMAIL PROTECTED] > > ******************************************************************* > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* > > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
