Login
Neu hier? Registrieren.
Roadmap
Die aktuelle Roadmap findet man hier. Hier sollen einige wichtige Punkte übersetzt werden (aktuelle Roadmap für Version 0.97).
Object-oriented core – Rewritten from the ground up using xPDO
Improved API – A new object-oriented API features increased coverage of MODx core objects using a more consistent architecture.
Die Core-Files werden überarbeitet und auf den neuen Datenbank-Layer xPDO gebracht. Dieser verspricht schnellere Verarbeitung von Queries sowie einfacher zu gestaltene Datenbankabfragen (API).
New Manager - We're losing the frameset and bringing you fully customizable manager templates complete with AJAX connectors for flexible validation and processing. A fresh new interface driven by the new MODx core + Smarty + Ext + MooTools.
Der Manager, also das Backend von MODx wird überarbeitet. Die in 0.96 noch vorhandenen Frames werden ersetzt. Es wird einfach möglich sein, den Manager nach eigenen Bedürfnissen zu gestalten. Hierfür wird die Template Engine Smarty genutzt, als Ajax-Bibliothek kommen die mootools zum Einsatz.
Unified User and Security Model – Manager users and web users become simply users, manager user/document groups and web user/document groups simply become user and document groups.
Die momentane Trennung von Manager User und Web User wird aufgehoben, es gibt nur noch User und Usergruppen. Die fein granulierbaren Rechteeinstellungen bleiben natürlich erhalten.
Improved caching – New core and partial-page caching techniques help reduce overall cache file-size as well as server resource loads on cache directories by organizing cache files into a hierarchical folder structure.
Caching wird weiter verbessert.
Simplified, concise terminology – Some core MODx concepts changed to be more intuitive and more concise, in accordance with modern accepted web terminology. The most important of these changes are:
- Web Resources – (formerly Documents and Web Links) represent any content managed by MODx that is directly accessible via a URL.
- Content Elements – (formerly MODx “resources”) represent components that define source content managed within the MODx content database which can be processed and optionally return output.
- Content Tags – New name for existing and new tags that are parseable, but that are not content elements; i.e. they do not define their source content within the MODx content database.
Die Terminologie wird überarbeitet und vereinheitlicht:
- "Dokumente und Weblinks" werden zu Web Ressourcen. Sinnvoll, da ein Dokument mehr sein kann als bloßer Inhalt.
- Die bisherigen "Ressourcen" (Snippets, Plugins etc.) werden zu Content Elementen, das heißt Element, die den Inhalt in irgendeiner Form verarbeiten und das Ergebnis zurückliefern.
- Content Tags - Tags, die geparst werden können, aber nicht in der MODx Datenbankverwaltet werden.
Content Filtering – New Input Filters and Output Filters are PHP classes which replace the current concepts of MODx Widgets and @bindings, as well as the extensions provided by the PHx add-on. It further expands on PHx, allowing the features to apply to any Content Element.
- Input filters – Mutate source content and properties/parameters before processing
- Output filters – Mutate output content after processing
Neues Filterkonzept (ersetzen bisherige Widgets und @bindings):
- Input Filter: Erlauben, den Inhalt vor dem Verarbeiten zu beeinflussen
- Output Filter: Erlauben den Inhalt nach dem Verarbeiten zu beeinflussen
Improved Content Parser – Features fully recursive, source-order processing without reliance on less efficient and less flexible regular expression patterns currently used. To quote Jamie Zawinski, "Some people, when confronted with a problem, think “I know, I'll use regular expressions.” Now they have two problems."
- Any element represented by a tag can be cached per page using the ! Token; e.g. [[!snippet]] or [[!$chunk]] or [[!*content]].
- Embed tags of the same type; embedded tags are processed before the containing tag; e.g. [[~[[++site_start]]]] or [[!snippet? &tpl=`[[!getTemplate]]` &msg=`[[*introtext]]`]]
Um es kurz zu machen: Die Parser-Logik wird erweitert. Abfragen, Bedingungen und mehrere (Snippet, Chunk, TV etc.-) Tags in einem Aufruf können rekursiv verarbeitet werden.
Simplified, unified tag format – To simplify parsing logic, improve parsing performance and avoid confusion with many new adopters, all tags are now of a single format, differentiated by a token or a set of tokens which appear before a string which identifies the Content Element or Content Tag to be processed; e.g. [[tokenIdentifier]].
Das Tag Format wird überarbeitet und vereinheitlicht. Übersicht:
Ähm, ja. Weitere Flexibilität, weitere Möglichkeiten die Core-Funktionalitäten zu überschreiben u.v.m.Even more extensible; even less hacking - The new object-oriented core allows you to provide your own custom implementations of many core features without ever hacking the core code. This helps protect your upgrade path.
- Web Resources – Easily define your own classes to define and implement custom resources, from web services, to AJAX processors, to rich-media content handlers, or even integrate third-part templating applications (e.g. Smarty).
- Content Elements and/or Tags – Define your own content elements that define custom or integrate external source content from a database, processes it however you want, and returns an output. Use them like you would any content element. You can even define tag tokens to allow a custom tag representation to be used or just extend the Content Tag base class directly for simpler custom elements that don't need a database table; e.g. [[-bobsCustomElement]].
- Content Parser – Provide your own custom parser class to override and/or extend the core parsing capabilities.
- Request handling – Extend or override the core request handling methods.
- Response handling – Extend or override the core response handling methods.
- Session handling – Provide your own custom class to handle user sessions per PHP standards.
- Error handling – Provide your own custom class to handle PHP errors.
- Partial-page caching – Provide your own custom cache capabilities globally or via custom Web Resource and/or Content Elements/Tags.
- Database result-set caching – Provide your own database result-set caching implementation.