Hello Magnolia Developers,

I wanted to mention a few thoughts in relation to the point FLuiD / Drag n' 
Drop Support:

We've implemented Drag n' Drop for paragraph moves in the custom 
templating-components module we created for our customer.
We implemented it using jquery-ui "draggable" & "droppable" for moving 
paragraphs around, as well as jquery-ui "sortable" for sorting lists of stuff.

It works really well, but has one *major* shortcoming: the jquery-ui based 
stuff only ever works "within one page".

However, I think it would be a really, really, (really, really) cool use-case 
to enable editors to open two browser windows, say to separate pages of the 
site, and be able to drag paragraphs from one page to another, i.e. dragging 
between the 2 browser windows.

Further use cases might be to enable dragging image-files from the desktop into 
content-areas, or the dms tree, things like that.

In my investigations, this kind of thing is possible with HTML5 drag & drop 
support. We unfortunately did not have time to implement it within the scope of 
our project, but it's on my personal "TODO" list...

Regards from Vienna,

Richard



-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]] 
Im Auftrag von Philipp Bärfuss
Gesendet: Montag, 19. September 2011 13:49
An: Dev-List Magnolia
Betreff: [magnolia-dev] Product Team Protocol (2011.09.19)




2011.09.19
        Build
                update pom with snapshots?
                only if we start/plan to work on the module
                Ondrej's responsabilities
        FLuiD
                drag and drop
                        tough
                        issue
                                from outer frame to the inner iframe
                        discuss the technical consequences
        Migration
                commercial - EntropySoft Content ETL
                OpenMigrate - reverse engineering various CMS systems
                CMIS/Apache Chemistry based 
                        somebody is trying to build this
        STK 2.0
                migration is in progress
                main concepts are now understood
                set of groovy classes
                should blog about the changes
                        meeting with Gregory
                        Timo will also blog
                                HTML 5
                                mobile
        Magnolia 4.5
                no update
        Maintenance
                Magnolia 4.4.5
                        changelog
                        release notes
                        99 issues solved
                        released
                activation (MAGNOLIA-3837)
                        not a blocker
                        difference with CE/EE?
                        exception is shown in the inbox
                        no consequences for the content on a public instance
                        we have a fix
                                apply it
                        activation really needs a rewrite
                security issues (SUPPORT-XXXX)
                        tickets are created
                                but private
                        work in progress
                        going to be in 4.4.6
                cache header negotiation (MAGNOLIA-3699)
                        will solve MGNLFORM-93
                        starts to be critical
                        scheduled for 4.4.6
                Form
                        release independently against 4.4
                Shop
                        release independently against 4.4

- philipp



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to