[Neos] Adding own element to the inspector
soren.malling at gmail.com
Thu Oct 24 08:45:15 CEST 2013
I'm currently working on making Neos extensible in this regard, it's good
> to have some real usecase packages as an example.
I would love to put the taxonomy package in as a usecase package :-)
> I'll keep you posted here ok?
That's awesome :-)
> Søren Malling schreef op 10/23/13 11:58 :
>> I've lately been working on some implementation of Taxonomy into TYPO3
>> and TYPO3 Neos.
>> The current state can be found here
>> https://github.com/**sorenmalling/TYPO3.Taxonomy<https://github.com/sorenmalling/TYPO3.Taxonomy>(A Flow package)
>> https://github.com/**sorenmalling/TYPO3.Neos.**Taxonomy<https://github.com/sorenmalling/TYPO3.Neos.Taxonomy>(A Neos package)
>> Now I've stumbled upon the issue, that element for the inspector _has_ to
>> From what I've read a configuration based on either "map"  or "paths"
>>  would help us here - but does any of the requirejs people knows any
>> pros/cons on this topic?
>> I don't see it as _must have_ configuration for 1.0 bust then for 1.1
>>  http://requirejs.org/docs/api.**html#config-map<http://requirejs.org/docs/api.html#config-map>
>>  http://requirejs.org/docs/api.**html#config-paths<http://requirejs.org/docs/api.html#config-paths>
> Neos mailing list
> Neos at lists.typo3.org
More information about the Neos