This project is mirrored from https://git.typo3.org/typo3/typo3.git.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
- 13 Apr, 2021 1 commit
-
-
This patchs adds a new LitElement that invokes the update request of FormEngine if a field's value with such configuration changes. This replaces the current approach of huge onchange/onclick attributes rendered per affected field. A further patch will cleanup the necessity of TBE_EDITOR.fieldChanged(). Resolves: #93899 Releases: master Change-Id: I79aa5b6ab7cca9b555efaafcadabcc623567af64 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68756 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
core-ci <typo3@b13.com>
Tested-by: Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Richard Haeser <richard@richardhaeser.com> Reviewed-by:
-
- 19 Mar, 2021 1 commit
-
-
This change reduces the overhead of the d3 framework by using native CustomEvents on the actual Lit element of the SVG instead of d3-dispatch logic: * typo3:svg-tree:nodes-prepared (enrich node data) * typo3:svg-tree:expand-toggle (expand/collapse) * typo3:svg-tree:node-context (clickmenu) * typo3:svg-tree:node-selected (on-click) As shown in the patch, the actual logic of interacting with the outside framework (Persistent, ContextMenu, window.) is moved to the actual Lit components, making the SVG tree slimmer and easier to maintain. Resolves: #93782 Releases: master Change-Id: I6f5227579eb16ec218bbe67de2aecbcaaabb3fcc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68464 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Georg Ringer <georg.ringer@gmail.com> Tested-by:
-
- 18 Mar, 2021 1 commit
-
-
The SVG Tree class is now a lit element, allowing for further reduction of d3 usage in favor of native HTML5 APIs. Resolves: #93773 Releases: master Signed-off-by:
Benni Mack <benni@typo3.org> Signed-off-by:
Benjamin Franzke <bfr@qbus.de> Change-Id: I12fef793726f83e872a353901528516a589e48ab Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68309 Tested-by:
-
- 15 Mar, 2021 1 commit
-
-
Benni Mack authored
The SVG tree is now building the SVG elements and needed containers ("<g>") via lit-helper. In addition, the update() method is renamed to this.updateVisibleNodes() to easier integrate this as Lit element, as update() is a reserved protected method in lit. The initialize() method is much cleaner, as the event listener registration is now separated in a custom method. Resolves: #93724 Releases: master Change-Id: I945cd620f9900c6ea535dfe5f0d44ee5ced46f89 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68367 Tested-by:core-ci <typo3@b13.com>
Tested-by: Daniel Gorges <daniel.gorges@b13.com> Tested-by:
-
- 11 Mar, 2021 1 commit
-
-
This change optimizes the SVG Tree implementations (again), this time focussing on using proper constructors for SVG tree and its derivatives (SelectTree, PageTree, FileStorageTree). In addition, the search + filter logic is now moved into the base class, in order to reduce duplicate code, and to re-add features (next steps) that were not implemented in TYPO3 v9 when re-writing the page tree, such as highlighting filtered results. In addition, unused properties and settings are removed. This change marks one of the final changes for reworking the SVG Tree implementation, afterwards allowing us to move towards: * native DOM events in favor of d3-dispatch * custom elements instead of wrapper methods * decouple "top." and "document." based settings into the Container classes Resolves: #93701 Releases: master Change-Id: I55733b8c2d0a84ca263ac6e77d7d0bac30877e25 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68332 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 10 Mar, 2021 1 commit
-
-
This patch provides the following changes in order to have better abstractions and encapsulate the dependencies of each implementation. 1. SelectTree (Category Tree) The TreeToolbar is now clearly coupled into the SelectTree and built as LitElement inside the SelectTreeElement. SelectTree now contains all relevant functionality regarding selecting multiple items, and shows settings (SelectTreeSettings) which were only used in SelectTree. This is especially relevant for the multiple item selection, and the exclusiveKey handling. 2. PageTree + FileStorageTree Obsolete public methods are removed, and visibility is changed. Filtering is now separated in favor of a non-public property. By using Types (in e.g. PageTreeDragDrop) the visibility is also adapted Obsolete wrapper methods are removed. Resolves: #93692 Releases: master Change-Id: Ifead098bb80e37d5c7ad5e1d0eabda14aa7087ce Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68303 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 09 Feb, 2021 1 commit
-
-
This change migrates all left-over components of * SvgTree * SelectTree (a.k.a. CategoryTree) * and PageTree to TypeScript adding types in various places to make the code less error-prone. Resolves: #87678 Resolves: #85400 Releases: master Change-Id: Ibb4024d365857c44018a7a201c1cf75baa48179a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67662 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 04 Feb, 2021 1 commit
-
-
Benni Mack authored
This change migrate the TreeToolbar (used in FormEngine Category Tree for example) to TypeScript, removing effectively one RequireJS call and replacing it with a native TypeScript component. Removing the rest of the jQuery will be part of a separate effort. Resolves: #93432 Releases: master Change-Id: I3df66cd1c28d096c0f32982347dbd37c58834e4d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67640 Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
-
- 07 Jan, 2021 1 commit
-
-
Benjamin Franzke authored
SelectTreeElement makes use of $.param() without importing jquery via requireJS. Instead of adding the missing jquery import, we simply migrate to the native URLSearchParams, as it is available in all supported browsers. Furthermore we avoid decoding the datastructureidentifier json, as it is encoded to json server side. We do this, because URLSearchParams does not url encode nested objects. Resolves: #93200 Releases: master Change-Id: I0da98092da6e09d6576bbdb59112d738086be238 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67323 Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Oliver Bartsch <bo@cedev.de>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 09 May, 2020 1 commit
-
-
It's safe to use getElementById() instead of querySelector() in case an element is fetched by its ID. Numbers for nerds: getElementById() is nearly 1.5x faster than querySelector(). To be fair, both functions are really fast with executing multiple million operations per second, thus nobody will notice a performance impact. See https://www.measurethat.net/Benchmarks/ShowResult/106740 Resolves: #91254 Related: #91183 Releases: master Change-Id: I2ed590d20c9af66ce818f012ac73ec45c5c9fa55 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64384 Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
-
- 13 Apr, 2019 1 commit
-
-
This patch migrates FormEngine's SelectElementTree to TypeScript. Also, a terrible hack that puts the local tree initialitation callback into global scope has been removed. Resolves: #87987 Releases: master Change-Id: Ib34ae7fe4ac1e197af2183b8890cc72e13a900e9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60316 Tested-by:
Steffen Frese <steffenf14@gmail.com> Tested-by:
Frank Naegler <frank.naegler@typo3.org> Reviewed-by:
-
