On 08.01.2008, at 16:20, Jan Haderka wrote:

We are talking about 3.5.x, right?

Yes. 3.5.x
I don't think the data module existed officially before this.

Data TreeBrowser
        - Lists the nodes (especially also mgnl:contentNodes) on certain
repository (in our case "data")
did you try to specify "repository" property for your tree control? It
should work.

Sure, this works already. I'm just listing the features the TreeBrowser needs generally.

        - Lists only a certain type, i.e. "data" module type -> see config /
modules/data/config/types
Normally, you have your data organized in some structure so it is just a matter of configuring tree control to show only certain subtree of your
data repository.

Right. But you would definitely have to write a custom tree control, right?

                - At this point I'm not sure if the actual data node knows 
anything
about its type. I have not checked the meta data yet.
                - Maybe the type is defined by the path, so on should be able to
limit the TreeBrowser to a certain path as defined in /modules/data/
config/types/[my_type]/rootPath
        - Define which fields should be displayed (Only the "name" will
probably not do)

you can easily modify the dialog to add extra properties if adding
something to the data repository manually or implement ImportHandler to
add those extra properties when importing data into repository.

Sorry, I must clarify: Define which columns should be displayed in the TreeBrowser. Again this can be handled by the custom tree control. But it would be nice if one could configure this via the dialog settings of the control which opens the TreeBrowser.

        - Ability to filter, especially when there are many records?
        - Ability to sort?

In the repository browser directly or in the tree control for selecting
items?

Hm... both would be nice and useful, but lets start in the TreeBrowser for selecting items. In addition: I'm not sure if Magnolia Ltd. is interested in having these features in the CE since I think they are in the EE.

dataUuidLink Control
        - Allows the referencing of a single data node of a certain type
- Calls the TreeBrowser described above for the selection of the node
        - Acts like the uuidLink control
dataMultiselect Control
        - Allows the referencing of multiple data nodes of a certain type
- Calls the TreeBrowser described above for the selection of the node
        - Acts like a combination of the multiselect control and the
uuidLink control

should be possible with configuration of existing controls or by
extending them. I've done this already before just not remember exactly
how ... would have to dig in for examples.

I've looked at the code this afternoon. I think we would have to extend them. Any samples are warmly appreciated though.

Questions - also to the Magnolia staff:
1. Are these features not implemented somewhere yet?
2. Would you be interested if these features would be added? Is this
the right way to do it?
3. Who would like to help?

If you have extra controls to work with data repository and its content,
I'll be happy to review them and possibly include.

Great. Thanks.

To sum things up: It's not a huge task - most of it is there already. One has to extend a few things though. But for people like me who have not done anything similar yet, it's a lot of digging through code, if I have to do it on my own.

-Will

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------

Reply via email to