{"id":60440,"date":"2023-08-15T03:01:45","date_gmt":"2023-08-14T17:01:45","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=60440"},"modified":"2024-03-16T13:36:57","modified_gmt":"2024-03-16T03:36:57","slug":"event-calendar-php-bookmark-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/event-calendar-php-bookmark-tutorial\/","title":{"rendered":"Event Calendar PHP Bookmark Tutorial"},"content":{"rendered":"
\"Event<\/a>

Event Calendar PHP Bookmark Tutorial<\/p><\/div>\n

Client meets server today, allowing the PHP data storage talents in yesterday’s Event Calendar PHP Tutorial<\/a>‘s work to meet a “clientside” way to<\/font> …<\/p>\n


\nRecord to Remember via Bookmark<\/font>
\n<\/code><\/p>\n

… use the web browser Bookmarks<\/a> to help you recall an Events in Month report with long entries.<\/p>\n

Involving a Bookmark still needs those “get” ? and & arguments, and we allow the PHP to lookup for us the data underscoring an address bar URL such as …<\/p>\n


\nhttps:\/\/www.rjmprogramming.com.au\/HTMLCSS\/events_in_month.php?exactlabel=August__2023_00000__1<\/font>
\n<\/code><\/p>\n

… that mapping being possible, now, making use of a pseudo<\/i> hashtag arrangement … your Clayton<\/i><\/a>‘s hashtag, if you will!<\/p>\n

To start to use a hashtag<\/i> suits, as your hashtag navigation only makes sense in the “clientside” woooorrrrrllllddd, and even there, really using one only tries to position a webpage where an element with an ID matching the hashtag sits (and we are never going to have this ID element in our work)<\/font>, and in the meantime we’ve passed across from the child PHP to the parent HTML a valuable piece of information helping the link to the Bookmark system be possible. The Javascript codeline (you may have noticed) … <\/p>\n


\n var documentURL=document.URL<\/font>;
\n<\/code><\/p>\n

… as stupid and simple looking as it is, is crucial for us. We get child webpage parts (like our PHP) to change document.URL<\/font> to a far too long in normal circumstances address bar URL<\/i> the rest of the code feeds off. It’s just that now, that far too long in normal circumstances address bar URL<\/i> has a #[hashtag]<\/i> appended such as …<\/p>\n


\n#August__2023_00000__1<\/font>
\n<\/code><\/p>\n

… uniquifying a Month, Year<\/i> Events in Month identifier part with a version of the user’s IP address (so that they only see what is relevant to them).<\/p>\n

Address bar URLs such as “https:\/\/www.rjmprogramming.com.au\/HTMLCSS\/events_in_month.php?exactlabel=August__2023_00000__1<\/font>” are Bookmarkable<\/sub>, and so we allow for similar outcomes with less concern about how much data is being “recorded” and recallable (via that web browser’s Bookmark system).<\/p>\n

Also, today, a lot of CSS tweaks, so that the CSS styling now looks like …<\/p>\n


\n<style>
\n #eventcalendar {
\n background-color: #fcfcfc;
\n }
\n
\n td {
\n padding-top: 2px;
\n padding-left: 2px;
\n padding-right: 2px;
\n padding-bottom: 12px;
\n }
\n
\n .dayb {
\n color: white;
\n background-color: red;
\n padding: 5 5 5 5;
\n border-radius: 80px;
\n margin-bottom: 15px;
\n }
\n
\n .dow {
\n color: purple;
\n font-style: bold;
\n }
\n
\n .selday {
\n margin-left: 8px;
\n background-color: rgba(255,0,0,0.7);
\n display: inline-block;
\n width: 50px;
\n border-color: transparent;
\n text-overflow: ellipsis;
\n }
\n
\n .tablurb {
\n background: linear-gradient(to right, white, lightpink, pink);
\n }
\n
\n input[type=\"submit\"] {
\n margin-bottom: 3px;
\n border-radius: 180px;
\n }
\n
\n input[type=\"number\"] {
\n margin-left: 3px;
\n margin-right: 3px;
\n border-radius: 180px;
\n background-color: #f3f3f3;
\n padding: 2 2 2 2;
\n }
\n
\n #smonth {
\n margin-left: 3px;
\n margin-right: 3px;
\n border-radius: 180px;
\n background-color: #f9f9f9;
\n padding: 2 2 2 2;
\n }
\n
\n .boldtitle {
\n background-color: rgba(0, 211, 107, 0.2);
\n }
\n
\n .boldtitle + .tablurb {
\n margin-top: 8px;
\n }
\n

\n .selhistory {
\n border-radius: 180px;
\n background-color: lightpink;
\n padding: 2 2 2 2;
\n }
\n<\/style>
\n<\/code><\/p>\n

… and we thank this webpage<\/a> for the heads up regarding how to calculate week numbers within a year<\/i> data item displays now available in …<\/p>\n