During the change from xajax to xajax php 7 an xajax to jybrid there was a lot of significant changes. The characteristic of xajax was migrated to jybrid. The source-code from old xajax javascripts and old php was nearly completely changed and refactured. Thats the reason why jybrid was created as replacement for xajax.
@see also used scripts from other developers
more then one form unobtrusive form submission unobtrusive button hashing so in html tags only data-jybrid-btn="hashValue", the execution command will set into an "execution stack" adding an jybrid.Exe before and after handler, writing directly the task-message into the Jybrid.Exe command such as "Requesting new Username" with response [Successs,Failed,Error,Warning] ..whatever Node-Skeleton Templates with an response command that sends back an json object with "create nodes". alternative send back ajax-response command which is handling an complete node/html-tag generation on submit ajax command, get dynamically other form-field-values (or other attribute values) js setValue, getValue because input-fields can not handle setAttribute(ele,'value','myInputValue') after change the value while typing into the inputfield auto-get form-field values as parameter (perhaps you have build some tabs or accordions, the state should be automatic submittable )
Jybrid Inline-Skript beim Laden der Einstiegsseite können gecached werden und als externe Javascript-Datei automatisch in die Webseite eingebunden werden. Alternative kann dieses gecachte Initial-Script als Inline-Script eingebunden werden.
Jybrid inline scripts can be cached when loading the start page and automatically integrated into the website as an external javascript file. Alternatively, this cached initial script can be included as an inline script.
Jybrid Inline-Skript beim Laden der Einstiegsseite erhalten das "nonce" attribute. Jybrid inline script when loading the start page get the "nonce" attribute.
<script nonce="static-id"></script> <script nonce="dynamic-id"></script>..are already the default Javascript configuration options and no longer need to be set via Javascript init script.
ide-stubs will be follow
Jybrid needs an ajax-upload. But with the full functionality of the jybrid framework. Lets start now ;-)
Append js snippet onto renderOn @param null|string $onMethod default on null is "onclick" @param null|string $append optional append a string after the button expression public function renderOn(?string $onMethod = null, ?string $append = null): string
Button-Scripts from 0.7.9.3 can be configured with public function renderOn(?string $onMethod = null): string; if the $onMethod = null automatically jybrid uses the onclick=""
@deprecated addParameter @replaced with Add @deprecated addParameters @replaced with Adds @deprecated addParametersArray @replaced with Adds
The respective Jybrid unobtrusive tag can now be clicked with childtags, as they are often set for example with fontawesome. Up to 5 childNodes in the Jybrid unobtrusive tag are now possible. Der jeweilige Jybrid unobtrusive Tag kann nun mit Childtags, wie sie zum beispiel mit fontawesome gerne gesetzt werden, geklickt werden. Bis zu 5 Verschachtelungen im Jybrid unobtrusive tag sind nun möglich
unobtrusiveAdd was moved to class Unobtrusive. It is easier to handle.
From:
Jybrid\Unobtrusive\Request::unobtrusiveAdd('.content');
To: Jybrid\Unobtrusive\Unobtrusive::unobtrusiveAdd('.content');
Zwecks der Vollständigkeit von jybrid wollte ich hier ein komplettes HTTP Header handling implementieren.
This Version is stepped over because the xajax HTTP-Header handling was not enough.
Seit der version 0.7.4 existieren die jybrid Emitters. Über das selbe javascript wurden nun auch die hmtl-dom events verfügbar gemacht. Diese dom-events erstetzen das alte xajax event handling mit eval-scripts. @see ajax-Dom-Events
@see Jybrid-Javascript-Snippets
Einführung der Javascript-Emitter um die alten Xajax-Event-Snippets zu entfernen. Die Emitter wurden in dieser Version für das Eventhandling direkt in jybrid bereit gestellt. @see Jybrid-Emitters
Anpassungen der Scripting-Engine
Integration der über die Jahre gesammelte Code-Fragemente die ich in Verwendung mit Xajax und Joomla verwendet habe
Erstes Ausmisten des alten Xajax - Quellcodes
Umstellung von Xajax auf Php 7
Letztes releases von Xajax
Joomla 1.5 implementation 28 Jan 2011 http://www.joomlaos.de/option,com_remository/Itemid,41/func,finishdown/id,6578.html