A suggestion: keep each of these changes as separate patches, makes them easier to review and merge into trunk
You are right. But it is easier and faster for me to work in several features at the same time. If somebody is interested in only one of them, I can make separate patches for those features. I'll add the CTRL+DragAndDrop and the one dealing with creating/deleting group icons. The visual changes have very close code so I don't know if it will be possible to separate them. Also, I found a little bug with returning error messages. I'll update right now.
It's not about "somebody interested in them". It's about actually being able to sensibly deal with it; thus if you're really interested in making a contribution which should (somewhen) hit the main development branch, Eddi's suggestion to split it up into its single constituents is essential. Doing it from the start keeps it simple as well. As a monolithic patch... it's unlikely that one even can bring up the motivation to review it as reviewing single patches with a single purpose and change is MUCH easier and MUCH less time-consuming.
Using something like mercurial queues
it's also nothing which requires much of work to keep it separately. Actually on the contrary. And you still work on all features concurrently. Also generally, I can only recommend patch authors to have a look at mercurial (or maybe git).
Using svn when dealing with patches seems to be quite inferior to either of hg or git.
And yes, the intentions of these patches sound reasonable (I didn't yet look at any details, though)