[Neos] FYI: Summary of todays "Technical Meeting"
Bastian Waidelich
bastian at typo3.org
Tue Jun 10 17:43:57 CEST 2014
Hi all,
here's the summary of todays technical meeting (see
http://wiki.typo3.org/TYPO3_Neos-DiscussionMeetings):
Participants: Jacob Floyd, Christian Müller, Marc Neuhaus, Bastian
Waidelich
= Todos/Updates from the previous meetings =
(Name in brackets refers to the contributor that brought up the issue)
* Dynamic configuration of selector elements (dropdowns in Neos
inspector) (Søren Malling):
-> No updates, see http://forum.typo3.org/index.php/t/203184/
* Improved handling for TargetNotFound exceptions (Georg Ringer, Bastian
Waidelich):
-> Bastian pushed a basic implementation, reviews wanted:
https://review.typo3.org/28502
* Optimize database step in setup (Aske Ertmann):
-> No updates, see http://forum.typo3.org/index.php/t/203261/
* Case insensitive search in TYPO3CR (Christian Müller):
-> No updates, see http://forum.typo3.org/index.php/t/203261/
* How to make editing more configurable (Christian Müller):
-> We had a dedicated meeting, see
http://forum.typo3.org/index.php/t/203662/ &
http://forum.typo3.org/index.php/t/203504/
* "Party decoupling" task (Adrian Föder):
-> No updates, see
https://review.typo3.org/#/q/status:open+topic:PartyDecoupling,n,z &
http://forum.typo3.org/index.php/t/203504/
* "Rules" workflow concept (Søren Malling):
-> We'll have a dedicated meeting, see
http://forum.typo3.org/index.php/t/203794/
* Collation issue in migrations (Christian Müller):
-> No updates, see http://forum.typo3.org/index.php/t/203794/
* Rest/Http/Exception Handling Concepts (Carsten Bleicker):
-> No updates, see http://forum.typo3.org/index.php/t/203794/
* Global Fluid namespaces (Bastian Waidelich):
-> Bastian will provide a patch asap according to the suggestions
from the previous meeting, see http://forum.typo3.org/index.php/t/203794/
= Summary of the last meeting (10th June 2014) =
== add better interaction capabilities to the commandController ==
* Initiator(s): Marc Neuhaus
=== Background: ===
There's a wide variety of interaction possibilities that can greatly
improve commandControllers
like (examples from Symfon/Console):
* easy output coloring through "<error>Warning!</error>"
* TableHelper to render a formatted table
* ProgressHelper to render and advance and progress bar
* DialogHelper with numerous types of questions like: select, ask,
confirm, askHidden, etc
Helpers/Methods like this would improve the usability of quite some
commands greatly.
For example:
* The DoctrineMigration command can ask after generation if you want to
move the Migration to a package
(http://dl.dropboxusercontent.com/u/314491/Screenshots/sjhezep2vvxm.png)
* Ask for required arguments instead of errors like "Required argument
"foo" is not set."
(http://dl.dropbox.com/u/314491/Screenshots/-q-0c-35youl.png)
Here's a issue i opened for that a while ago:
http://forge.typo3.org/issues/49016
=== Possible discussions: ===
* Should we change the output of the CommandController to use
Symfony/Console (Did that already here:
https://github.com/mneuhaus/Famelo.Common/blob/master/Documentation/AbstractInteractiveCommandController.md)
* Should we reimplement/copy those helper methods into flow
=== CONCLUSIONS ===
As we already have a hard dependency to *Symfony/Console* we decided to
extend the existing *\TYPO3\Flow\Cli\CommandController* to use the
Symfony console internally.
The API will be backwards compatible with one exception:
$this->output() and $this->outputLine() will no longer buffer the output
until the end of the request but render content *directly* to the
console. This is a desired side-effect that enables features like
progress bars.
Marc will push a review request based on
https://github.com/mneuhaus/Famelo.Common/blob/master/Classes/Famelo/Common/Command/AbstractInteractiveCommandController.php
== Re-evaluate shortcut menu item state ==
* Initiator(s): Christian Müller
=== Background: ===
Currently shortcut pages get the state '''CURRENT''' if the node they
point to is being rendered. This makes it impossible to render shortcuts
as *ACTIVE* (see http://forge.typo3.org/issues/59204).
=== CONCLUSIONS ===
* Only one (document) node can be '''CURRENT''' at a time, it's the one
that is being rendered
* All parent nodes of the current one are '''ACTIVE''' independently
from it's type (e.g. including shortcuts, no matter where they point to)
* All other nodes have a state '''NORMAL''''
For marking a a node active that is *not* in the current "rootline" we'd
need to be able to create "alias nodes" (or reference nodes) via the UI.
--
Bastian Waidelich
More information about the Neos
mailing list