{"id":6297,"date":"2014-02-12T05:03:54","date_gmt":"2014-02-11T18:03:54","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/wordpress\/?p=6297"},"modified":"2014-02-12T05:03:54","modified_gmt":"2014-02-11T18:03:54","slug":"javascript-object-oriented-more-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/javascript-object-oriented-more-tutorial\/","title":{"rendered":"Javascript Object Oriented More Tutorial"},"content":{"rendered":"
\"Javascript<\/a>

Javascript Object Oriented More Tutorial<\/p><\/div>\n

Today’s tutorial builds on previous Javascript Object Oriented Approach Primer Tutorial<\/a> (as shown below) to start to explore an Object Oriented design approach for data objects in Javascript and shows the use of an array of these data object data members (not the objects themselves). The subject matter of the resultant program is a Book Catalogue. The Javascript handles the storage of this Book information in keeping with your web browser session as shown with the originally written javascript_next_object_oriented.html<\/a> where the salient Javascript method of interest is Array push<\/a>. As you might imagine, a book catalogue can get big, and you may get sidetracted<\/strike> sidetracked and you may want to resume where you left off. In order to do this, continuing on with just HTML\/Javascript you could use Cookies<\/a> but for our tutorial today we are going to use PHP called javascript_next_object_oriented.php<\/a>. What’s new today is the introduction of a TableSpreadsheet class, which will be developed to have some Excel spreadsheet types of qualities, and maybe later we’ll extend it to cater for inhouse SQL functionality (the woooorld’s our oyster). So how we got from a single Book class to a Book and TableSpreadsheet class is shown here<\/a>.<\/p>\n

As you can see Javascript is a very flexible language able to handle a variety of coding practices and forms and can easily be used to maintain an Object Oriented<\/a> coding approach, (which we head towards today), as well. So this tutorial has come some way towards making the Book Catalogue practically more useful, and there is more that can be done. We will probably revisit this project later. Programmers may use an OOP approach all the time, never, sometimes, or just for big projects. It’s all very subjective really … chortle, chortle. JSON usage with Javascript OOP is an interesting topic<\/a> too.<\/p>\n

Found this link<\/a> very helpful … thanks.<\/p>\n

Now let’s see how a functional approach might change to end up as an approach towards OOP here<\/a> (for PHP\/HTML\/Javascript) and here<\/a> (for (HTML\/Javascript).<\/p>\n

Please enjoy our live run tutorial<\/a> (a reduced-functionality live run of just HTML\/Javascript is available here<\/a>). Finally, if you want a “seeded” live run of the books of the picture above, to see the functionality of TableSpreadsheet class straight away (which normally relies on a Saved list of books) click here<\/a> and the books will be shown in a new window.<\/p>\n