joomla/Component-Builder
40
26
Fork 12
Code Issues 80 Pull Requests 2 Projects 4 Wiki Activity

Updated 4a. JCB Demo Component Directory, Folders and Files (markdown)

Joseph Geller
2018-09-20 15:51:55 -05:00
parent 84f1603876
commit 8846ba6b88
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
4a.-JCB-Demo-Component-Directory,-Folders-and-Files.md

@@ -284,7 +284,8 @@ 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 with dumps of variables in code accompanied by even more information.
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 with dumps of variables in code accompanied by even more information. 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 including its own code that supplies the features and functionality you choose to accompany your own custom code snippets in JCB.
* index.php.{main}:49
* libraries/src/Application/CMSApplication.php.Joomla\CMS\Application\SiteApplication->execute:195
* libraries/src/Application/SiteApplication.php.Joomla\CMS\Application\SiteApplication->doExecute:233
@@ -293,7 +294,7 @@ 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 found in
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.
- [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