{"id":38862,"date":"2018-06-17T03:01:53","date_gmt":"2018-06-16T17:01:53","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=38862"},"modified":"2018-06-17T18:31:22","modified_gmt":"2018-06-17T08:31:22","slug":"monthly-chronicler-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/monthly-chronicler-primer-tutorial\/","title":{"rendered":"Monthly Chronicler Primer Tutorial"},"content":{"rendered":"
\"Monthly<\/a>

Monthly Chronicler Primer Tutorial<\/p><\/div>\n

We’ve got a new web application for you today. We’re calling it a “Monthly Chronicler”, which is a web application like a “Calendar” or “Planner” or “Diary”, where the user can personalize the entries according to a date, with whatever information they want.<\/p\n\n\n\n

This idea is of limited applicability unless it is a bit accountable, and at this first draft, the accountability comes in the form of saving a user’s personalized data into HTTP Cookie<\/a> data form. As you might know from online shopping experience that you have, the use of HTTP Cookies can mean a web application can resume another call of the web application and load in your previous data, ideal for a “Monthly Chronicler”.<\/p>\n

Other features are …<\/p>\n