Unterhaltung

Nachrichten

1. mk

   so, let's "turn on" some more new HTML5 element names in mt #piwigo #theme... nav, main, section (I'll do menu later). first question to solve: do I use one nav element containing 1-3 'bars', or do I create a section with 1-3 nav elements?

   Sunday, 17-Nov-13 20:12:09 UTC von oracle.skilledtests.com
   • Jon Kulp

     @mk I'm not sure about this either. I think I only used 1 nav section and gave the other 2 nav-type areas different div names. Probably could make all 3 nav with different classes though, or just different id.

     Sunday, 17-Nov-13 20:40:40 UTC
   • mk Jon Kulp

     @jk the problem is, so far at the top of the content area you can have up to three 'bars' which each can contain a combination of pure navigation elements (breadcrumbs or pagination), and one or more toolbars (thelatter would be 'menu' in HTML5); I've wrapped the three bars (class .headerBar) in a div (#headerBarWrapper). So far so good - but that's HTML 4.01. By now I've reasoned my way to: the 'wrapper' would be a section; inside that section would be up to three divs (.headerBar), and inside each you could have a nav element and/or a menu element. ...

     Sunday, 17-Nov-13 20:48:59 UTC
   • mk Jon Kulp

     @jk references for this: http://www.whatwg.org/specs/web-apps/current-work/multipage/sections.html#the-nav-element , http://html5doctor.com/nav-element/

     Sunday, 17-Nov-13 20:49:55 UTC
   • mk Jon Kulp

     @jk Also, these 'bars' were sitting inside a #content element, but semantically they are not content; so I should take the whole construct out of it and put it on top. I can still visually tie them together with teh same or slightly different background color

     Sunday, 17-Nov-13 20:52:11 UTC
   • mk

     @mk OK, so I'll start with taking the whole thing out of #content, and ponder teh rest while doing that... #babysteps #theme #hacking

     Sunday, 17-Nov-13 21:06:18 UTC
   • mk

     @mk \o/ the more I am #hacking away and moving stuff around, the more consistent it all gets <3

     Sunday, 17-Nov-13 21:35:57 UTC
   • Jon Kulp

     @mk Oy! More complicated structure than I'm dealing with!

     Sunday, 17-Nov-13 22:30:30 UTC
   • mk Jon Kulp

     @jk it's complicated all right: the presence of each lower level depends on a toolbar action in a level above - essentially a 'drill down' operation. It took me a lot of time to really understand that and get it coded consistently (and even, using Smarty, add an extra bottom margin only on the bottom headerBar) #theme #chiselingaway

     Sunday, 17-Nov-13 22:39:14 UTC
   • Jon Kulp

     @mk omg yikes. Glad I'm not learning css on something that complicated. Btw I checked my code and I used the nav tags in 2 places, topnav and sidebar. I have nav-type <ul> in footer area too but for some reason didn't use nav tags there.

     Sunday, 17-Nov-13 22:55:54 UTC
   • mk Jon Kulp

     @jk the standard says to use nav for 'major' navigation sections (whatever 'major' is!), and also that footer normally contains some navigation elements that don't need to be marked up as such (like contact or copyrioght links)

     Sunday, 17-Nov-13 23:00:54 UTC
   • Jon Kulp

     @mk must be why I didn't use em there :) the topnav list on my site is for a few University-wide navigation links, sidebar is for school of music site-specific nav. I think those fall within the standard.

     Sunday, 17-Nov-13 23:14:53 UTC
   • Jon Kulp

     @mk btw if you're interested here's the testing site, still haven't launched on University server yet. http://jonkulp.net/som/

     Sunday, 17-Nov-13 23:17:39 UTC
   • mk Jon Kulp

     @jk yes, that makes sense.you could also have one nav for site-wide navigation and another for on-page (toc) navigation. etc.

     Sunday, 17-Nov-13 23:19:03 UTC
   • mk Jon Kulp

     @jk great - you can see mine evolving at http://pwg.unsim.pl/ - scaffolding and all ;) (yes, occasionally some things don't work but I do my best to maintain main functionality even while I'm hacking away)

     Sunday, 17-Nov-13 23:25:55 UTC
   • Jon Kulp

     @mk well it doesn't load a theme at all for me. Error: Parse error: syntax error, unexpected ')', expecting T_PAAMAYIM_NEKUDOTAYIM in /home/mkatsma/public_html/pwg/_data/templates_c/1d2kwse^%%B8^B86^B864D0DF%%infos_errors.tpl.php on line 4

     Sunday, 17-Nov-13 23:48:42 UTC
   • mk Jon Kulp

     @jk it should work again now - I just need to tweak some styling because I now have the headerBarWrao above the conten instead of inside it - but that's for #tomorrow!

     Sunday, 17-Nov-13 23:58:24 UTC