cuba-platform / cuba-dnd Goto Github PK

• Fix formatting according to https://confluence.haulmont.com/display/COM/README+and+Documentation
• Explain installation without cloning and building from source, like it is in https://github.com/cuba-platform/cuba-zk
• Remove "Build from source" section

Can this component be used to handle the drag&drop of external objects?

I mean, using this to handle dropping a file over a control on the screen.

I was thinking of a drop-in control to use with this component: mariodavid/cuba-component-attachable, so that the user could either upload a file with the usual file browser dialog, OR simply drag&drop a file from the desktop to a control on the page.

Hello,
I have a question about the previewing of eligable drop locations. When I have a target layout with some items already present, I expect a preview between those items when I hover over the drop location while holding a draggable item. This works find when the items already present are leaf components (e.g. buttons). However, when they are composite components (e.g. a vbox or hbox) I find some unusual behaviour: the previewer also previews drop locations between subcomponents of those items.

For example, provided the following descriptor:

<dnd:dndCssLayout id="dashboard"
    dragMode="CLONE"
    height="AUTO"
    width="100%"
    stylename="min-height">
    <vbox>
        <button caption="1"/>
        <button caption="2"/>
    </vbox>
    <vbox>
        <button caption="3"/>
        <button caption="4"/>
    </vbox>
</dnd:dndCssLayout>

...I can still drag items between the subcomponents of the vbox.

In my application, the items in my drop target are highly composite with many nested subcomponents. The current preview behaviour results in a very glitchy UI. How can I make sure that only locations are previewed between root elements of the target layout?

I have some troubles with installing the addon. I download and open it as project in Studio, when i try to add it in my main project as Custom component, I get error that artifact not found

Update the "Usage" section of readme.md: describe how to install the component using Add-ons Marketplace