From d56cf39c2ae1b36760395f0a15cf828e12899cd6 Mon Sep 17 00:00:00 2001 From: Joseph Geller Date: Thu, 20 Sep 2018 20:32:21 -0500 Subject: [PATCH] Updated 4a. JCB Demo Component Directory, Folders and Files (markdown) --- 4a.-JCB-Demo-Component-Directory,-Folders-and-Files.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/4a.-JCB-Demo-Component-Directory,-Folders-and-Files.md b/4a.-JCB-Demo-Component-Directory,-Folders-and-Files.md index a6742e5..e12a4a1 100644 --- a/4a.-JCB-Demo-Component-Directory,-Folders-and-Files.md +++ b/4a.-JCB-Demo-Component-Directory,-Folders-and-Files.md @@ -284,7 +284,7 @@ defined('_JEXEC') or die('Restricted access'); *** ## \com_demo\demo.php ## NetBeans Debug Trace -Joomla! Debug option, set in Joomla! Configuration will also provide this and now with Chrome XDEBUG mentioned earlier it has links to where the code resides. Also J!Dump boosts this using user suppiled commands in code that dump variables and even more information about their contents, type, etc. Note how many paths there are to the Joomla! API supplied automatically by JCB in the component's code it produces in the installed JCB Demo package. JCB supplies the code necessary and you trigger other code snippets to be written automatically as JCB supplies features and functionality you choose to accompany your own component. This includes the custom code snippets you added to it that are displayed by varying JCB views. +Joomla! Debug option, set in Joomla! Configuration will also provide this and now with Chrome XDEBUG mentioned earlier it has links to where the code resides. Also J!Dump boosts this using user supplied commands in code that dump variables and even more information about their contents, type, etc. Line numbers of where these Joomla! supplied classes, properties and methods may be found are at the end of each. Note how many paths there are to the Joomla! API supplied automatically by JCB in the component's code it produces in the installed JCB Demo package. JCB adds the code necessary and you trigger other code snippets to be written automatically by JCB to add features and functionality you choose to have in your own component. This includes the custom code snippets you added to it that are displayed in various JCB views as you build and edit a component. * index.php.{main}:49 * libraries/src/Application/CMSApplication.php.Joomla\CMS\Application\SiteApplication->execute:195 @@ -294,8 +294,8 @@ Joomla! Debug option, set in Joomla! Configuration will also provide this and no * libraries/src/Component/ComponentHelper.php.Joomla\CMS\Component\ComponentHelper::executeComponent:382 * components/com_demo/demo.php.require_once:35 -The code that follows has links to some Joomla! documentation that is outdated but file locations are still applicable. Also, it was a very good addition to the documentation as at times it is a bit tedious to find Joomla! paths for files containing its code. For example, the Joomla! Platform documentation is no longer maintained and Platform 14 is outdated plus obsolete. Yet it was a great tool and I wish it was still in the current documentation. Be sure you not any changes in the current version of Joomla! with all documentation and links. Nonetheless many are informative and many have constructs still in use and are not described in current documentation. But the archives are there and also state if something is deprecated very clearly. For example, class names are being changed so all are uniform so be aware of aliases introduced in Joomla! 3.8 and [other changes](https://developer.joomla.org/news/703-joomla-3-8-beta-released-for-testing.html) in preparation for Joomla! 4 and facilitate backwards compatibility and other reasons. - +The code that follows in the last bullet point in the above trace, demo.php has links to some Joomla! documentation that is outdated but file locations are still applicable. Joomla! has some extensive changes involving namespaces which it relies on heavily. Deprecated class names will be removed in Joomla! 5 so it is wise to use the new ones, aliased starting with Joomla! 3.8. Unfortunately, it is a bit tedious to find Joomla! paths for files containing its code at times. For example, the Joomla! Platform documentation is no longer maintained and Platform 14 is outdated plus obsolete. It is in the links since it has not been removed from current documentation and it is a great way to present it. Be sure you note and observe any changes in the current or future versions of Joomla! as code may break if Joomla! team removes it. Some links also point to older versions and archived material. Nonetheless, many are informative and many have constructs still in use and not described in current documentation. If a class for example or design pattern is obsolete now and deprecated it is indicated very clearly. For example, class names are being changed so all are uniform so be aware of aliases introduced in Joomla! 3.8 and [other changes](https://developer.joomla.org/news/703-joomla-3-8-beta-released-for-testing.html) in preparation for Joomla! 4 that facilitate backwards compatibility. + - [Add unobtrusive JavaScript support to keep a tab state.](https://api.joomla.org/cms-3/classes/JHtmlBehavior.html#method_tabstate) \libraries\cms\html\behavior.php - [Get a document object and set the component css/js.](https://api.joomla.org/cms-2.5/classes/JFactory.html#method_getDocument)