[Neos] [Team] NodeTypes in TYPO3.Neos.NodeTypes
aske at moc.net
Fri Jul 26 14:12:01 CEST 2013
An easy way to see the result is using ./flow configuration:show --type NodeTypes, and this command could be improved with information on where the specific configuration is last set, which would greatly improve all configuration debugging. Good documentation is a better way to go IMO.
But it's true that you have to look in multiple packages to find how everything is configured, although this will be the case anyway when we will start to have packages defining additional node types. So in my opinion that's not reason enough to keep it all in one package.
Concerning the disabled flag I think we need to discuss that on a great level since we will have a lot of different configuration that needs to be able to be disabled or in a way unset, but currently we done have common concept for that.
On 26/07/2013, at 11.18, Carsten Bleicker wrote:
> would it be a good idea to introduce a flag in the yaml settings of a node to enable/disable it?
> so you dont have to worry about wich nodetype is delivered or not.
> Am 26.07.2013 um 11:16 schrieb Carsten Bleicker:
>> right at this point i have to figure out how NodeTypes works and how they are configured.
>> and to get an overview of all given types i have to switch between several packages.
>> it was a little barrier to keep in mind wich node is configured in wich package.
>> ts2, yaml, templates etc.
>> Am 26.07.2013 um 07:19 schrieb Christian Müller:
>>> Hi Robert,
>>> that was my reasoning as well when I started the package and put everything in there. The question is what NodeTypes need to be delivered with Neos and which can optional. I think Page could move to TYPO3.Neos.NodeTypes (again) ;)
>>> Robert Lemke wrote:
>>>> Hi team,
>>>> using node types more frequently, I realize that it will likely be some
>>>> hassle for users to memorize which node types are part of the TYPO3.Neos
>>>> package and which ones are in the TYPO3.Neos.NodeTypes namespace.
>>>> As far as I remember, you moved types like "Page" to the Neos package
>>>> for dependency reasons. But wouldn't you think that, from a user's point
>>>> of view, it's much easier to have all (Neos) node types in
>>> Neos mailing list
>>> Neos at lists.typo3.org
> Neos mailing list
> Neos at lists.typo3.org
More information about the Neos