[TYPO3-mvc] Tree in backend and frontend

[Christian Baer]

Hi Michael,

in the last days I experimented a litte with a ExtJS-Tree in the 
Backend, this one:

http://dev.sencha.com/deploy/dev/examples/tree/check-tree.html
or other trees: http://dev.sencha.com/deploy/dev/examples/#sample-8


The call is quite simple:


var tree = Ext.tree.TreePanel({
	...
	dataUrl: 'check-nodes.js',
	...
});


I called it in a JS-File which I included with the fluid-template 
<f:be.container includeJs="...">

I stopped so far. The next step would be to generate the 
"check-nodes.js" dynamically.



Regards
Christian Baer



Am 18.04.11 20:55, schrieb Michael Knoll:
> Hi Franz,
>
> at first, it's not directly related to Extbase - at a second glance it
> is... seems like there is kind of a routing mechanism for extJs stuff
> (with which the tree is made) but there seems to be no bridge to couple
> this with Extbase... so I'll go to the DEV List with the first question
> but leave the other question here: What can I do to bring Extjs Routing
> and Extbase together?
>
> Any ideas - or has somebody made this work yet!
>
> Thanks a lot!
>
> Greetings
>
> Mimi
>
>
>
> Am 18.04.11 00:52, schrieb Franz Koch:
>> Hey Michael,
>>
>>> I'm currently implementing a category system based on nested sets.
>>> Everything works so far - now I wanted to know what is best practice if
>>> you want to render a JS tree (like the page tree for example) in Backend
>>> (and Frontend later)?
>>>
>>> Is the page tree usable as a standalone library and can I fill it with
>>> arbitrary hierarchical data - or is is restricted to pages and needs the
>>> DB structure used in TYPO3 to manage hierarchical data? I do not have a
>>> parent_id or things like that...
>>>
>>> I already looked at cps_tcatree but this comes with its own JS - I would
>>> like to use something already being there...
>>
>> don't get me wrong, but how is this related to Extbase? You might get
>> best answers for this on the DEV list.
>>
>> But since TYPO3 4.5 there is the possibility to render select fields as
>> a tree in BE forms. Just have a look at the current documentation (or
>> probably pending docs).
>>
>