drag-and-drop awesomeness turns out to be smoke-and-mirrors :-(

I’ve been spending some time and effort on how to organize my convoluted chunk hierarchy... so I’ve been playing with the drag/drop features more than I had previously been. I was just dragging chunks from one folder to another, when I realized that the "green light" icon (which indicates an allowable landing place to "drop" an element) was lit up when I was passing over OTHER CHUNKS. Like so:


So I released the mouse button, and what do you know... it worked! Suddenly I was seemingly able to make chunks containers for other chunks. Totally Awesome! In no time flat, I had organized my chunk structure in exactly the logical manner I had been yearning for:


I was about to stand up and do the happy dance, when I hit the refresh button (a "pinch me, I’m dreaming" gesture), and everything reverted to the way it had been.

Based on this experience, I draw one of the two following conclusions:

• This behavior is purely a bug, and chunks-as-containers was never meant to be a feature
• chunks-as-containers was meant to be a feature, and the fact that this state doesn’t "stick" is the bug

I’m probably over-simplifying. But, let me go on the record as saying that allowing elements (at least chunks and templates) would make MODx 10,000x more awesome than it already is.

Just sayin’.

Quote from: jrotering at Apr 30, 2010, 09:50 AM

• This behavior is purely a bug, and chunks-as-containers was never meant to be a feature

I’m probably over-simplifying. But, let me go on the record as saying that allowing elements (at least chunks and templates) would make MODx 10,000x more awesome than it already is.
Just sayin’.

Haha. While a cool idea, that is definitely not a feature, and is definitely a bug. Can you make a JIRA ticket for it?

While it would be cool in looks...I’m not sure about the implications of making an Element heirarchical. Might have some unwanted side-effects...Maybe for 2.1.

Actually, on 2nd thought, dont file a bug, this has already been fixed in SVN.

FWIW, this is actually a planned feature from the original Revolution prototype, except that not only will it be an organizational feature, it will also allow for processing of child Elements. The applications of both the additional organizational and behavioral features this will make possible are, at least in my vision, awesome.

"It’s not a bug, it’s a (sneak preview of an awesome forthcoming) feature."

Just to clarify for those reading - this will not be in the Revolution 2.0.0 release, especially since we’re in RC status currently.

It is definitely in the mix for 2.1 and beyond, as are many other cool features. Getting to 2.0.0, and getting people using Revo, will help get us on a good foundation to start adding features like this.

Revo, in short, provides us a much stronger foundation to move forward on.