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-22 21:15:14 -05:00
parent 740167606d
commit ccc2aa3c77
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -282,7 +282,7 @@ Later, after viewing the remaining videos and the chapters that accompany each i
// No direct access to this file // No direct access to this file
defined('_JEXEC') or die('Restricted access'); defined('_JEXEC') or die('Restricted access');
*** ***
## \com_demo\demo.php ## \demo.php
## NetBeans Debug Trace ## NetBeans Debug Trace
* index.php.{main}:49 * index.php.{main}:49
* libraries/src/Application/CMSApplication.php.Joomla\CMS\Application\SiteApplication->execute:195 * libraries/src/Application/CMSApplication.php.Joomla\CMS\Application\SiteApplication->execute:195
@@ -292,7 +292,7 @@ defined('_JEXEC') or die('Restricted access');
* libraries/src/Component/ComponentHelper.php.Joomla\CMS\Component\ComponentHelper::executeComponent:382 * libraries/src/Component/ComponentHelper.php.Joomla\CMS\Component\ComponentHelper::executeComponent:382
* components/com_demo/demo.php.require_once:35 * components/com_demo/demo.php.require_once:35
We see from the NetBeans XDEBUG Trace exactly what line numbers are being reused from the Joomla! core (a myriad of code is behind most), to initiate the entry point for the JCB Demo component, demo.php in the last line, which eventually, using th e same Hoomla! API, which are located in the indictaed paths next, to display the looks view and edit button: We see from the NetBeans XDEBUG Trace exactly what Joomla! class file line numbers are being reused from the Joomla! core (a myriad of code is behind most), culminating with requiring the entry point for the JCB Demo component, demo.php in the last line. It then uses the same Joomla! API and classes from class files indicated in the path shown next, that display the looks view and edit button:
Custom Script Custom Script
Add PHP (after getting the items)* Add PHP (after getting the items)*
@@ -327,7 +327,6 @@ Target (array) $items values *
## Editing the Site View ## Editing the Site View
http://localhost/demo/administrator/index.php?option=com_componentbuilder&view=dynamic_get&layout=edit&id=36 http://localhost/demo/administrator/index.php?option=com_componentbuilder&view=dynamic_get&layout=edit&id=36
Some below and previously may be outdated. For example, the Joomla! Platform documentation is no longer maintained and Platform 14 is outdated plus obsolete and the Joomla! 2.5 API Index may also appear. It is in the links since it has not been removed from current Joomla! documentation; many classes in use have early origins as stated in the documentation. Joomla! has some extensive changes though involving namespaces with Joomla! 4 which relies on it heavily. Locations of class files vary by release, made a bit more elusive with Joomla! 4 name space changes. But their is current backwards compatibility and hence alias list do exist as we shall see next. Some below and previously may be outdated. For example, the Joomla! Platform documentation is no longer maintained and Platform 14 is outdated plus obsolete and the Joomla! 2.5 API Index may also appear. It is in the links since it has not been removed from current Joomla! documentation; many classes in use have early origins as stated in the documentation. Joomla! has some extensive changes though involving namespaces with Joomla! 4 which relies on it heavily. Locations of class files vary by release, made a bit more elusive with Joomla! 4 name space changes. But their is current backwards compatibility and hence alias list do exist as we shall see next.
Since deprecated classes in Joomla 3.8.x will be removed in Joomla! 5 it is wise to use the new ones, aliased starting with Joomla! 3.8. Be sure you note and observe any changes in the current or future versions of Joomla! as code may break if the Joomla! team removes it. If a class for example or design pattern is obsolete now and deprecated it is indicated very clearly. These and [other changes](https://developer.joomla.org/news/703-joomla-3-8-beta-released-for-testing.html) should be reviewed in preparation for Joomla! 4. For now, class names that eventually will raise exceptions and error messages in your component code are facilitated; backwards compatibility exists until Joomla! 5. Since deprecated classes in Joomla 3.8.x will be removed in Joomla! 5 it is wise to use the new ones, aliased starting with Joomla! 3.8. Be sure you note and observe any changes in the current or future versions of Joomla! as code may break if the Joomla! team removes it. If a class for example or design pattern is obsolete now and deprecated it is indicated very clearly. These and [other changes](https://developer.joomla.org/news/703-joomla-3-8-beta-released-for-testing.html) should be reviewed in preparation for Joomla! 4. For now, class names that eventually will raise exceptions and error messages in your component code are facilitated; backwards compatibility exists until Joomla! 5.