[Neos] NodeType.yaml visibility options for properties
aske at moc.net
Mon Jan 27 21:29:21 CET 2014
Sure this makes sense, but I don't see this feature any time soon though since you're the first to mention it.
That doesn't mean that anyone is free to implement it since I'm sure we'll want it in the core. If one needs support finding a good solution I'm sure the team would love to help out.
On Jan 10, 2014, at 9:21 AM, Dominic Garms <djgarms at gmail.com> wrote:
> On 09/01/14 21:34, Aske Ertmann wrote:
>> Hey Dominic
>> I'm not sure I fully understand what you mean here. Do you want to show/hide certain properties depending if they have set reloadIfChanged to TRUE? Because that just means that if the value is changed the page has to be re-rendered in order for the change to take affect. How do you propose the state of a property would enable/disable the property editor in the inspector? Could you please elaborate?
>> Best regards
>> On Jan 8, 2014, at 4:05 PM, Dominic Garms <djgarms at gmail.com> wrote:
>>> It would be great if properties only would be visible (and active), if other properties have a certain state. Currently it is possible to set "reloadIfChanged: TRUE" and now it would be helpful for my yaml config file to show/hide certain properties because of this value.
>>> Is this somehow possible or are there any thoughts about this already?
>>> Neos mailing list
>>> Neos at lists.typo3.org
> Hello Aske,
> I would like to set dependencies between properties, it was possible in TYPO3 CMS via Flexforms through display conditions like:
> It was possible to show certain properties through dependent fields with other properties. The reloadIfChanged would be the action on the dependent property to reload the yaml configuration. It was very helpful for a more complex configuration scenario.
> Neos mailing list
> Neos at lists.typo3.org
More information about the Neos