[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 312445] New: Pallet Panel concept, Somewhat like Recent Folder Panel/ action history/ Macro,  u
From:       Aaron Peterson <alpeterson () gmail ! com>
Date:       2012-12-31 22:42:01
Message-ID: bug-312445-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=312445

            Bug ID: 312445
           Summary: Pallet Panel concept, Somewhat like Recent Folder
                    Panel/ action history/ Macro,  undo redo in a scratch
                    pad.
    Classification: Unclassified
           Product: dolphin
           Version: 2.0
          Hardware: MS Windows
                OS: MS Windows
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-null@kde.org
          Reporter: alpeterson@gmail.com

This is a concept I have not seen implemented exactly this way before so please
bear with we.

I would like to have a panel that says what actions I have done.
 MV: 2 files Music
MV: 3 Files to Documents
CP: 3 files to ProjectRepo1

Mouse over, or expanding chevron could  give details:
  MV: 2 files Music  
  - from /home/bob/AmazonIN
     - to /var/media/Music  (ReadableByGroupTrusted)
     - GoldFrapp.mp3
     - SP-Adore.wma  
MV: 3 Files to Documents  (PermissionsKeptasReadableByOthers)
CP: 3 files to ProjectRepo1  (Permissions adjusted to same as folder)


There are many other features that would be immediately usefull, such as
clearly expressing the permissions of the files.

The pallet capability could be basically setting up a macro to be done if I
were to click on it while files were selected.
Such as, Copy to Flash Drive  (Which could included detection to make sure it
is the right flash drive, and ensure it is mounted and such.

So the reason why this is held as one feature request, when it could probably
be two, is that It could be neat to make a macro directly out of history.

I could have a bulk rename utility action register an event in the action
history, and even be repeatable from that history entry.

Also, undo should be implementable from this if a good history is kept.
Windows has a scary undo where I could hit undo accidentally and undo something
that I needed to do, so it is important to not do it this way.


Reproducible: Always




Dolphin is better than VISTA's file mangler... and I couldn't even find one in
windows8.
So thank you very much!

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]