WordPress Calendar Widget Above the Fold Cut to the Chase Tutorial

The recent WordPress Widget via Animated Emoji Button Above the Fold Tutorial “WordPress Widgets Above the Fold” work needs to return back to the specifics of those “early days” amended Calendar Widget because we want to contextualize …

chronology … with …
“Cut to the Chase” tutorial (gist)

Why? So that, you, the user, can ask a question like …

On Monday 10th December 2018 what is the gist of the "iOS iMessage Apps Primer Tutorial"

… and can, via the Above the Fold “clone” of the Calendar Widget and the click/touch of its “Iframes Up the Top” button, derive this information fairly easily via a new HTML select element dropdown, that we have introduced today …

Previous relevant WordPress Widget via Animated Emoji Button Above the Fold Tutorial is shown below.

WordPress Widget via Animated Emoji Button Above the Fold Tutorial

We have a dual purpose blog posting today that …

continues on the WordPress Calendar Widget WordPress Link to Iframe via Calendar Widget Above the Fold Tutorial “above the fold” theme, extending the coding logic to handle other widgets that the user may benefit from seeing “above the fold” … and in so doing …
we are starting down the road of “Emoji Button Animation” ideas, as an alternative dynamic menu thought

How do we structure the HTML of an “Emoji Button Animated”?

the emoji buttons are HTML “a” (link) elements style=’font-size:40px;’ … and for our animated ideas we now say for that original emoji HTML “a” (link) element we add style=’display:inline-block;’ … then …
nest this first emoji in an HTML div element style=’display:inline-block;’ that also includes within its innerHTML …
other nested emojis are added like the first but with different onclick logic to suit the widget purpose at hand and having different ID but the same style=’font-size:40px;’ and style=’display:none;’ … enforcing a “one emoji at a time is displayed” stratagem mixed up via …
the Javascript “steakknives()” function doing all this (the original contents before today’s changes emboldened) …
function steakknives() { var htinfo="", prefmore="", sufmore=""; suftries=["","-1","-2","-3","-4","-5"], preftries=["calendar-wrap;128197","recent-posts;128238","tag_cloud;127991","categories;128451","meta;128100","s;128270"]; if (!document.getElementById('atcalendar') && !document.getElementById('precalendar')) { if (document.URL.indexOf('animated_emoji=') != -1 || 7 == 7) { for (var ioup=1; ioup<preftries.length; ioup++) { for (var joup=0; joup<suftries.length; joup++) { if (document.getElementById(preftries[ioup].split(';')[0] + suftries[joup])) { if (htinfo == "") { htinfo="atcalendar"; } if (preftries[ioup].split(';')[0] == "s") { htinfo+="__at" + preftries[ioup].split(';')[0] + "earch"; sufmore+='<a id="at' + preftries[ioup].split(';')[0] + 'earch" style="display:none;text-decoration:none;font-size:40px;" href=#s title="' + preftries[ioup].split(';')[0].replace(/\_/g,' ').replace(/\-/g,' ').toUpperCase().substring(0,1) + 'earch' + ' positioned for you">&#' + preftries[ioup].split(';')[1] + ';</a> '; } else { htinfo+="__at" + preftries[ioup].split(';')[0]; sufmore+='<a id="at' + preftries[ioup].split(';')[0] + '" style="display:none;text-decoration:none;font-size:40px;" href=# onclick=" if (document.getElementById(' + "'" + 'justshow' + "'" + ')) { document.getElementById(' + "'" + 'justshow' + "'" + ').innerHTML=document.getElementById(' + "'" + preftries[ioup].split(';')[0] + suftries[joup] + "'" + ').innerHTML.replace(/' + preftries[ioup].split(';')[0] + '/g,' + "'" + preftries[ioup].split(';')[0] + '_t' + "'" + '); document.getElementById(' + "'" + 'justshow' + "'" + ').style.display=' + "'" + 'block' + "'" + '; } " title="' + preftries[ioup].split(';')[0].replace(/\_/g,' ').replace(/\-/g,' ').toUpperCase().substring(0,1) + preftries[ioup].split(';')[0].replace(/\_/g,' ').replace(/\-/g,' ').toLowerCase().substring(1) + ' to top">&#' + preftries[ioup].split(';')[1] + ';</a> '; } } } } if (htinfo != '') { prefmore="<div id=precalendar title='" + htinfo + "' style='display:inline-block;'>"; sufmore+="</div>"; setTimeout(steakknives, 5000); } } document.getElementById('site-title').innerHTML+=' ' + prefmore + '<a id="atcalendar" style="display:inline-block;text-decoration:none;font-size:40px;" href=# onclick=" if (document.getElementById(' + "'" + 'justshow' + "'" + ')) { document.getElementById(' + "'" + 'justshow' + "'" + ').innerHTML=document.getElementById(' + "'" + 'calendar_wrap' + "'" + ').outerHTML.replace(/calendar_wrap/g,' + "'" + 'calendar_wrap_t' + "'" + '); document.getElementById(' + "'" + 'justshow' + "'" + ').style.display=' + "'" + 'block' + "'" + '; } " title="Calendar to top">📅</a>' + sufmore + ' '; } else if (document.getElementById('precalendar')) { var echoices=document.getElementById('precalendar').title.split('__'); var ibis=echoices[0]; for (var koup=0; koup<echoices.length; koup++) { if (('' + document.getElementById(echoices[koup]).style.display).toLowerCase().indexOf('block') != -1) { document.getElementById(echoices[koup]).style.display='none'; if (koup == eval(-1 + echoices.length)) { ibis=echoices[0]; } else { ibis=echoices[eval(1 + koup)]; } } } document.getElementById(ibis).style.display='inline-block'; setTimeout(steakknives, 5000); } }
… is recursive (via the Javascript setTimeout timer function), the continuing job of that function being to determine one emoji to be style=’display:inline-block;’ while all the other nested emojis are style=’display:none;’

Can you see this as another idea for a menu?

Stop Press

To include the Search Widget … or not to include the Search Widget .. that is the question? We decided to include it, but we didn’t clone it (like the other widgets) this time, rather, we just hashtag navigate the user to the Search Widget. Why the difference? Cloning more suits scenarios where the ID is not crucial, and though cloning may work for the Search Widget, it is not worth it, in our books (nor our December pamphlette). It will be good for a mobile user to include the Search Widget in the thinking though, because it can be way down the bottom of the webpage otherwise.

Anyway, in amended code above look for the Search Widget specific itallic code snippets.

Previous relevant WordPress Link to Iframe via Calendar Widget Above the Fold Tutorial is shown below.

WordPress Link to Iframe via Calendar Widget Above the Fold Tutorial

As a web application programmer, it may seem a pretty obvious aim (or User Experience (UX) stratagem) in programming life, to seek to place functionality “above the fold” (ie. within an initial screen height and width view). The “above the fold” comes from the days when large spreadsheet newspapers needed to be folded in half to read on busy trains and buses, the “above the fold” content being that content above that fold within eyesight, at the time you are interested in.

Am totally in agreement with all this as well (though am a bit biassed here?!), though there are complications here …

often a single piece of functionality content “look” (that is large enough to read) can’t fit in the one initial screen (height and width) … and one we often come across as a programmer …
we only want to make some new functionality “very obvious” (“above the fold”) when we are ready to release it, because we feel that it is non-buggy enough to “go live”

… and this second point may be irrelevent in many scenarios, such as those where you …

have a test case scenario separate to the “go live” environment, on which you can fully test everything, ahead of deploying it (ie. going live with it)
can still test live with a “backdoor approach” that only you, the programmer (yooooooo hooooooo) know above for a short time while tests are carried out
an IDE controls your deployment to the live environment

… and for us with this current project, we used a bit of the middle option above, but were up until today, still sheepish with the incomplete look of our WordPress Blog Calendar Widget extended “Iframes Up the Top” functionality.

Taking a look at the parts of this WordPress Blog webpages just to the right of the blog title, you’ll have gathered we like to use “Emoji Buttons”, the size of which can be controlled by font-size:40px; (within new added code) to be that little bigger than usual, to suit their importance as buttons …

… and note the /calendar_wrap/g Javascript “replace all” regex syntax that we introduced to start being able to “clone” these Calendar Widgets, rather than physically move the original one. This idea is possible because, apart from the outer layer HTML div element of this WordPress (TwentyTen theme) Calendar widget, it lacks ID’ed HTML elements, so in that way all we need is to uniquify that one outer layer HTML div (in its outerHTML property form) to “slap it” up to the top using that onclick event logic you can see above.

To trace back through the context of this job during the “lack of very obvious above the fold logic” you can read from yesterday’s WordPress Link to Iframe via Calendar Widget Mobile Tutorial and on, down.

Previous relevant WordPress Link to Iframe via Calendar Widget Mobile Tutorial is shown below.

WordPress Link to Iframe via Calendar Widget Mobile Tutorial

Try controlling the size of an HTML iframe in tight confines on a mobile platform, and perhaps you get the feeling of trying to tame a brumby. We tried some horse whispering for an hour but got precisely nowhere, and so used “plan B”, that is to make the content smaller, while still adding knowledge. How about adding the blog posting title for the day of the month currently shown in the WordPress TwentyTen theme Calendar widget? And if they’ve clicked one of these links, take them straight to that whole blog posting rather than the “middle~~man~~person” precis. The Javascript (DOM) (including lots of inline CSS styling) became …

… for a codebase that suits both mobile and non-mobile platforms, the latter of which were catered for well by yesterday’s WordPress Link to Iframe via Calendar Widget Primer Tutorial.

Two aspects of interest here are …

mobile platform detection via … if (navigator.userAgent.match(/Android|BlackBerry|iPhone|iPad|iPod|Opera Mini|IEMobile/i)) {
// mobile platform specific Javascript goes here
}
checking in Javascript for hashtag navigation via … if ((location.hash + ”).indexOf(‘content’) != -1 && (document.URL.indexOf(‘?m=’) != -1 || document.URL.split(‘/’).length >= 4)) {
// #content hashtag navigation code goes here
}

Previous relevant WordPress Link to Iframe via Calendar Widget Primer Tutorial is shown below.

WordPress Link to Iframe via Calendar Widget Primer Tutorial

Calendar functionality in web applications can be very useful. To organize data in a chronological order makes a lot of sense given the lives we live here on Earth where we are able to rely on the sun rising every day. At this blog, for example, we post once every Sun rising (somewhere on Earth) every day.

The WordPress TwentyTen theme has a Calendar widget you can choose to use on your blog, and we decided to do that here at this blog. If this Calendar widget had been a …

Text Widget we could have added to its functionality with today’s “WordPress Link to Iframe via Calendar” directly in the code of the Text Widget … and then you could get inside the native PHP and use …
WordPress Codex approach to native code amendments … or, at least for us, here, with our …
TwentyTen theme’s header.php gets changed to add in the new “WordPress Link to Iframe via Calendar” functionality, working off what the widget already provides via document.body onload event Javascript DOM code

We like the look of WordPress TwentyTen theme’s Calendar widget, so why not start with its outerHTML property value as used in the (Javascript DOM) code …

… called via document.body onload event Javascript DOM code call in the PHP’s HTML …

<body onload=" postcalendar(); ">

… manifested (and used) by one additional button added to the end of the Calendar widget labelled “Iframes Up Top”.

Did the “justshow” (HTML, within header.php) bit …

<div id="justshow" style="position:absolute;top:0;left:0;display:none;z-index:23;"></div> <div id="main">

… remind you of another WordPress blog change? Take a read of WordPress Blog Posting Thread Content Summary Tutorial. We hope this helps you out.

Previous relevant WordPress Blog Posting Thread Content Summary Tutorial is shown below.

WordPress Blog Posting Thread Content Summary Tutorial

Yesterday’s WordPress Blog Posting Content Summary Primer Tutorial used the reveal HTML5 “stars” …

details tag … and its nested …
summary

… to allow for “scrunched up” presentations of multiple blog posts so really only had huge impactive use with the WordPress Blog document root index.php call of it, where several of the latest blog postings are shown to the user. However, in the way we go about it here, we construct these …

Blog Posting Threads

… that call on and contain blog postings related to it (from the recent past, usually, but doesn’t have to be). These “lead in” blog postings are presented in full separated from the new blog posting content by our home (CSS) styled …

<hr />

… horizontal rule elements. Today, we make use of that “habit” we have to introduce new …

details tag … and its nested …
summary

… “pairings” to scrunch these up, when the user has decided to generally “scrunch up” (though we are going to think about doing it all the time after seeing what it’s like, for a while).

Not much new here, you might say, but there is something new about what we do navigation wise in these scenarios. We have another “habit” with our blog posting creations for these “blog posting threads”. Invariably, we’re pretty sure, we provide within the new blog posting, an HTML a hashtagging link (eg. #wpbpcspt to get to blog posting “thread” member below, often “yesterday’s”). We want it to be that if the user uses one of these a hashtagging links that causes any (new) “closed” details/summary “guardians against verbosity” to open up. How is that done? We maintain a global …

var nohlist=";";
… which gets to be accessed and used in a new Javascript function …
function checknohlist() { if (('' + location.hash).indexOf('#') != -1) { if (nohlist.indexOf(';#' + location.hash.split('#')[1] + ';') != -1) { document.getElementById('ds_' + location.hash.split('#')[1]).setAttribute('open', true); nohlist=nohlist.replace(';#' + location.hash.split('#')[1] + ';',';'); } } if (nohlist.replace(';','') != '') setTimeout(checknohlist, 3000); }
… using the hashtagging “flagger” location.hash … the bits of a URL after and including the # character, as relevant … that is hashtagging, to us … and this new function is now used in amended function from yesterday as per …
function details_summary(mou) { var other_bits=[], hrother_bits=[], ihrb=0, fb='', fbids=[], thatidis='', hrp=''; var dbitssare=document.body.innerHTML.split('<div class="entry-content">'); var dbitseare=document.body.innerHTML.split('<div class="entry-utility">'); if (document.URL.indexOf('detailssummary=') != -1 || mou != 0) { if (dbitssare.length > 1 && dbitssare.length == dbitseare.length) { var dbih=document.body.innerHTML, idbih=1; for (var idb=0; idb<dbitssare.length; idb++) { if (('' + dbitssare[eval(1 + idb)]).indexOf('<p>') != -1) { if (('' + dbitssare[eval(1 + idb)]).split('<p>')[idbih].split('</p>')[0] == '') { if (('' + dbitssare[eval(1 + idb)]).split('<p>').length >= eval(1 + eval(idbih))) { idbih++; } } dbih=dbih.replace('<div class="entry-content">','<details class="gendetails" title="Click me to toggle open/close ... ' + ('' + dbitssare[eval(1 + idb)]).split('<p>')[idbih].split('</p>')[0].replace(/\'/g,'`').replace(/\"/g,'`').replace(/\>/g,'>').replace(/\</g,'<') + '"><summary></summary><div title="entry-content" class="entry-content">'); } else { dbih=dbih.replace('<div class="entry-content">','<details class="gendetails" title="Click me to toggle open/close"><summary></summary><div title="entry-content" class="entry-content">'); } if (document.URL.indexOf('andmorehr=') != -1 || 1 == 1) { other_bits=dbih.split('<div title="entry-content" class="entry-content">'); hrother_bits=other_bits[eval(-1 + other_bits.length)].split('<div class="entry-utility">')[0].split('<hr '); hrp='<hr '; for (ihrb=1; ihrb<hrother_bits.length; ihrb++) { if (hrother_bits[ihrb].indexOf('</p>') != -1 && hrother_bits[ihrb].indexOf('If this was interesting you may be interested') == -1) { thatidis=''; fb=hrp + hrother_bits[ihrb].split('>')[0] + '>'; fbids=(hrp + hrother_bits[ihrb]).split(fb)[1].split('</p>')[0].split('<p id="'); if (fbids.length <= 1) { fbids=(hrp + hrother_bits[ihrb]).split(fb)[1].split('</p>')[0].split("<p id='"); if (fbids.length > 1) { thatidis=fbids[1].split("'")[0]; } } else { thatidis=fbids[1].split('"')[0]; } if (nohlist.replace(';','') == '' && thatidis != '') { setTimeout(checknohlist, 3000); } if (thatidis != '') { nohlist+='#' + thatidis + ';'; dbih=dbih.replace((hrp + hrother_bits[ihrb]), (fb + '<details id="ds_' + thatidis + '" class="innerdetails" title="Click me to toggle open/close"><summary>' + (hrp + hrother_bits[ihrb]).split(fb)[1].split('</p>')[0] + '</p></summary>' + (hrp + hrother_bits[ihrb]).split((hrp + hrother_bits[ihrb]).split('</p>')[0] + '</p>')[1] + '</details>')); } else { dbih=dbih.replace((hrp + hrother_bits[ihrb]), (fb + '<details class="innerdetails" title="Click me to toggle open/close"><summary>' + (hrp + hrother_bits[ihrb]).split(fb)[1].split('</p>')[0] + '</p></summary>' + (hrp + hrother_bits[ihrb]).split((hrp + hrother_bits[ihrb]).split('</p>')[0] + '</p>')[1] + '</details>')); } } hrp='<hr '; } } dbih=dbih.replace('<div class="entry-utility">','</details><div title="entry-utility" class="entry-utility">'); } document.body.innerHTML=dbih; } if (document.URL.indexOf('detailssummary=') != -1 && mou == 0) { document.getElementById("eds").innerHTML = "➕"; document.getElementById("eds").title = "Open up blog posting contents now"; document.getElementById("eds").style.visibility='visible'; } } else if (mou == 0 && dbitssare.length > 1 && dbitssare.length == dbitseare.length) { document.getElementById("eds").style.visibility='visible'; } }

So if you try today’s live run and “motor down” to one of the “blog posting threads” we have … and a lot are … you’ll see those new details/summary pairings “guarding against verbosity” unless you use some of those hashtagging links into these “lead in” blog posting thread submembers, or if you click the details element yourself.

Previous relevant WordPress Blog Posting Content Summary Primer Tutorial is shown below.

WordPress Blog Posting Content Summary Primer Tutorial

We really like WordPress.org for the basis of this blog’s design (and recognize WordPress.com as a great idea for those not wanting to host their own Apache/PHP/MySql domain). And am sure you would not be surprised that I am not alone. Take a read of the excellent WordPress information by Websitebuilder.org and, reading closely, you’ll see how popular this blogging platform is, and mention of a number of famous people using it.

I’ve never had much trouble with WordPress, so, not all the time, but occasionally, I tweak it. For this, we suggest, as WordPress would, to use their Codex PHP (with MySql) coding advice, and on a personal level, though, you’ll see, reading this blog, that we also like the direct approach of, mainly, changing the header.php PHP code that sits in, for our case of a theme called TwentyTen (“twentyten” in lowercase) …

[documentRootOfWordPressWebsite]/wp-content/themes/twentyten/

Today’s tweak of header.php relates to a matter dear to our hearts. The desire to cater for mobile users with small screens, yet not be dumbing blog posting content down just for the sake of it. Today we channel just about our favourite reveal based idea you can read more about at HTML5 Details Summary Primer Tutorial to harness the goodies that came with HTML5 in the form of the …

details tag … and its nested …
summary

Implementing this in header.php went like this …

added into …
<body onload=" changeasfordownload(); if (cafd == cafd) { cafd=0; } else { cafd=true; } checkonl(); setTimeout(initpostedoncc, 3000); widgetcon(); precc(); courseCookies(); cookie_fonts(); is_mentioned_by(); calendar_pass(); prejustshow(); details_summary(0);">
added a new emoji button up near the top …
document.getElementById('site-title').innerHTML+='<a id="avs" style="text-decoration:none;" href=# onmouseover="getVisualSynopsis(event);" onmouseout="yehbut();" ontouchstart="getVisualSynopsis(event);" ontouchend="yehbut();" onclick=" uptop(); " title="... you can wait for the long hover functionality about Visual Synopsis (Slideshows)">🎦</a> <a style="cursor:pointer;text-decoration:none;" onclick="popselid();" title="Filter Content via Div ID">➗</a> <a style="cursor:pointer;text-decoration:none;visibility:hidden;" title="Blog post contents reduced to summary" id="eds" onclick="pre_details_summary();">➖</a>' + printscreen(0);
then added these two new Javascript functions to suit those events defined above …
function pre_details_summary() { var idos=0,dos=[]; if (('' + document.getElementById("eds").title) == 'Blog post contents reduced to summary') { if (document.body.innerHTML.indexOf('<summary></summary>') == -1) { details_summary(1); } else { dos=document.getElementsByTagName('details'); for (idos=0; idos<dos.length; idos++) { if (dos[idos].className == "gendetails") { dos[idos].removeAttribute('open'); } } } document.getElementById("eds").innerHTML = "➕"; document.getElementById("eds").title = "Open up blog posting contents now"; } else { dos=document.getElementsByTagName('details'); for (idos=0; idos<dos.length; idos++) { if (dos[idos].className == "gendetails") { dos[idos].setAttribute('open', true); } } document.getElementById("eds").innerHTML = "➖"; document.getElementById("eds").title = "Blog post contents reduced to summary"; } } function details_summary(mou) { var dbitssare=document.body.innerHTML.split('<div class="entry-content">'); var dbitseare=document.body.innerHTML.split('<div class="entry-utility">'); if (document.URL.indexOf('detailssummary=') != -1 || mou != 0) { if (dbitssare.length > 1 && dbitssare.length == dbitseare.length) { var dbih=document.body.innerHTML, idbih=1; for (var idb=0; idb<dbitssare.length; idb++) { if (('' + dbitssare[eval(1 + idb)]).indexOf('<p>') != -1) { if (('' + dbitssare[eval(1 + idb)]).split('<p>')[idbih].split('</p>')[0] == '') { if (('' + dbitssare[eval(1 + idb)]).split('<p>').length >= eval(1 + eval(idbih))) { idbih++; } } dbih=dbih.replace('<div class="entry-content">','<details class="gendetails" title="Click me to toggle open/close ... ' + ('' + dbitssare[eval(1 + idb)]).split('<p>')[idbih].split('</p>')[0].replace(/\'/g,'`').replace(/\"/g,'`').replace(/\>/g,'>').replace(/\</g,'<') + '"><summary></summary><div title="entry-content" class="entry-content">'); } else { dbih=dbih.replace('<div class="entry-content">','<details class="gendetails" title="Click me to toggle open/close"><summary></summary><div title="entry-content" class="entry-content">'); } dbih=dbih.replace('<div class="entry-utility">','</details><div title="entry-utility" class="entry-utility">'); } document.body.innerHTML=dbih; } if (document.URL.indexOf('detailssummary=') != -1 && mou == 0) { document.getElementById("eds").innerHTML = "➕"; document.getElementById("eds").title = "Open up blog posting contents now"; document.getElementById("eds").style.visibility='visible'; } } else if (mou == 0 && dbitssare.length > 1 && dbitssare.length == dbitseare.length) { document.getElementById("eds").style.visibility='visible'; } }

Of course, this is most of benefit when you are not already honing in on the one WordPress blog posting, but there’s more fun to come, we reckon!

If this was interesting you may be interested in this too.

Your Numbers Game
Get clue	Your answer	Your Score
Clue?		Score 0/0

WordPress Calendar Widget Above the Fold Cut to the Chase Tutorial

Leave a Reply Cancel reply

Numbers Guessing Game

Your Numbers Game

Recent Posts

Categories

Meta

Your Background Image

OnTopList

Recent Comments

WordPress Calendar Widget Above the Fold Cut to the Chase Tutorial

Leave a Reply Cancel reply

Numbers Guessing Game

Your Numbers Game

Recent Posts

Categories

Meta

Tags

Your Background Image

OnTopList