[Neos] NodeType.yaml visibility options for properties
aske at moc.net
Tue Feb 4 18:20:23 CET 2014
Well I’m talking in terms of the team as well. There hasn’t been any of us needing this feature enough to prioritize it compared to other things.
However it’s cool that you need it so much you’re willing to implement it. It’s probably a quite complex topic though, since it involves configuration syntax definition/concept, a lot of rules based on other editor and complexity of having to do it client side or is that’s not the case then reload VIE schema’s for the specific element/case.
There isn’t any documentation regarding this component since that would be very specific and likely be outdated quickly, but we should be able to find a way to help you get started with some guidance from one from the team though. I think this is required anyway for making sure the solution fits the product in general so it can go into the core.
I don’t know if you’re already in the #typo3-neos channel on freenode, but if not feel free to come and ask questions there.
Regarding the other things you mention, we want to have help there as well but again a prioritization thing. Same goes for the initial collapse state of the group.
On 31/01/2014, at 06.21, Marcin Ryzycki <marcin at ryzycki.com> wrote:
> On 2014-01-27 08:29:21 pm +0000, Aske Ertmann said:
>> Hey Dominic
>> 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.
> Hi Aske,
> He's not the first - but the others are quiet ;-)
> It's definitely a functionality which I'm missing a lot. There are often scenario in each app, that once you set value X and then you need set few extra fields, which only make sense when X is set. Or the other way around.
> In fact it's so important to me that I was planning to have a look at the code how this can be achieved. There's few more things which I'm really missing in UI inspector: possibility to add help (icon) there, possibility to set initial status collapsed/expaneded for group. But that's separate discussion I guess.
> BTW Are there any draft documents about how to start developing for UI inspector? Apart of that http://docs.typo3.org/neos/TYPO3NeosDocumentation/DeveloperGuide/ ? Or shall I just have a look at the code?
> Neos mailing list
> Neos at lists.typo3.org
More information about the Neos