{"id":56407,"date":"2022-07-16T03:01:30","date_gmt":"2022-07-15T17:01:30","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=56407"},"modified":"2022-07-15T15:55:05","modified_gmt":"2022-07-15T05:55:05","slug":"notification-api-active-scheduling-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/notification-api-active-scheduling-tutorial\/","title":{"rendered":"Notification API Active Scheduling Tutorial"},"content":{"rendered":"
\"Notification<\/a>

Notification API Active Scheduling Tutorial<\/p><\/div>\n

The recent Channel Messaging API Notification Tutorial<\/a> “tinkered with” its Notifications API<\/a> based partner functionality.<\/p>\n

Today we continue “tinkering” all the way to “tweaking” that Notifications supervisor (permissions granted, that is<\/a>) to add some scheduling functionality which operates as long as a “surfing the net” incarnation of the web application webpage is showing a new button …<\/p>\n


\n<input type=button onclick='rwso();' value='Regularly While Still Open' style='background-color:orange;'><\/input>
\n<\/code><\/p>\n

… calling on new Javascript logics …<\/p>\n


\nvar every=-1;
\nvar fromnow=-1, fromfirst;
\nvar everytext='';
\n
\nfunction woclose() {
\n window.close();
\n}
\n
\nfunction evstrwso() {
\n fromfirst='' + new Date();
\n if (fromfirst.indexOf(':' + ('0' + every).slice(-2) + ':') != -1) {
\n if (fromnow == -1) {
\n \/\/document.title=' yes ' + fromfirst + ' ' + every;
\n setTimeout(evstrwso, 59800);
\n } else {
\n \/\/document.title=' Yes ' + fromfirst + ' ' + every;
\n setTimeout(strwso, fromnow);
\n }
\n window.open('https:\/\/www.rjmprogramming.com.au\/HTMLCSS\/notifications_ideas.html?scheduledblurb=' + encodeURIComponent(everytext), '_blank', 'top=500,left=500,width=200,height=200');
\n } else {
\n \/\/document.title=' no ' + fromfirst + ' ' + every;
\n setTimeout(evstrwso, 59800);
\n }
\n}
\n
\nfunction strwso() {
\n setTimeout(strwso, fromnow);
\n window.open('https:\/\/www.rjmprogramming.com.au\/HTMLCSS\/notifications_ideas.html?scheduledblurb=' + encodeURIComponent(everytext), '_blank', 'top=500,left=500,width=200,height=200');
\n}
\n
\nfunction rwso() {
\n everytext=prompt('What text goes onto notification?', '');
\n if (everytext == null) { everytext=''; }
\n if (everytext.trim() != '') {
\n var tt=prompt('How often to do in minutes (where + prefix means do it with that exact minute every hour)? Optionally comma separate a starting at minute value', '');
\n if (tt == null) { tt=''; } else if (tt == '+') { tt=''; }
\n if (tt.trim().indexOf('+') == 0) {
\n every=eval('' + tt.trim().substring(1));
\n setTimeout(evstrwso, 59800);
\n } else if (tt.trim().indexOf(',') != -1) {
\n every=eval(('' + tt.trim()).split(',')[1]);
\n fromnow=eval(eval(('' + tt.trim()).split(',')[0]) * 60000);
\n setTimeout(evstrwso, 59800);
\n } else if (tt.trim() != '') {
\n fromnow=eval(eval(('' + tt.trim()).split(',')[0]) * 60000);
\n setTimeout(strwso, fromnow);
\n }
\n }
\n}
\n<\/code><\/p>\n

… in the tweaked and tinkered with<\/a> notifications_ideas.html<\/a> HTML and Javascript client side Notifications API<\/a> based window.open popup notifying functionality with a “scheduled, immediately, blurb”<\/a> which could be configured here, for example<\/a>.<\/p>\n

\n

\n

Previous relevant Channel Messaging API Notification Tutorial<\/a> is shown below.<\/p>\n

\"Channel<\/a>

Channel Messaging API Notification Tutorial<\/p><\/div>\n

In order to introduce another new Javascript API called “Channel Messaging API”<\/a> …<\/p>\n

\nThe Channel Messaging API allows two separate scripts running in different browsing contexts attached to the same document (e.g., two IFrames, or the main document and an IFrame, two documents via a SharedWorker, or two workers) to communicate directly, passing messages between one another through two-way channels (or pipes) with a port at each end.\n<\/p><\/blockquote>\n

… into the mix, today, we wanted to combine …<\/p>\n