<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>Op 26-jan-2007, om 15:48 heeft Ken Rickard het volgende geschreven:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">Let me redirect a little back to the original post. <BR><BR>Any discussion other than UI expectations is premature.<BR> <BR>The original question is still primarily about user expectations, not the code used to implement.<BR><BR>Using Interface for jQuery seems a logical start, but is not a requirement. (And the dual MIT/GPL license of Interface issue is noted here: <A href="http://groups.drupal.org/node/2512">http://groups.drupal.org/node/2512</A>).<BR><BR>It seems that we may have a significant number of contrib modules (and some core) that would benefit from a Drag-and-Drop UI. Given that, it seems wise to have some common guideliness, so that users don't face different UI for each implementation. <BR><BR>Personally, I like Drag-and-Drop-and-Save (automated), but I don't want to implement that if Panels or Menus or Blocks uses Drag-and-Drop-and-Click-to-Save.<BR></BLOCKQUOTE>I *do* like the drag-drop-and-save (automated) method to, but while in all other form area's we also use submit_buttons to submit form data. So, for consistency i would go for the drag-drop-and-click-to-save method.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Yours sincerely,</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Steef</DIV><BR></BODY></HTML>