#245 User-selectable flags for dir compare items

open
nobody
Usability (267)
5
2013-05-24
2004-01-20
Anonymous
No

I am sure most people use WinMerge when they are
reconciling their source to some repository and so may
need to deal with a directory diff of over 50 files. It
would be nice to have a checkbox or some other way
to "mark" files and be able to load up a previous diff of
directories and have the "marks" show up so I can do
multi-session diff reviews more easily.

Discussion

  • Anonymous - 2004-01-20
    • labels: 104277 -->
    • milestone: 102449 -->
     
  • Anonymous - 2004-01-20

    Logged In: YES
    user_id=60964

    This obviously doesn't belong on the bug list. Moving to
    Feature Request list.

     
  • Kimmo Varis

    Kimmo Varis - 2004-01-20

    Logged In: YES
    user_id=631874

    Agreed, this is a good idea.

    But instead of adding couple of new hard-coded columns to
    directory compare, I'd like to see user-definable columns.
    Hard-coded columns should be ones containing data read from
    files and data retrieved from diff engine.

    But user definable columns could have user-defined set of
    values. Maybe just two types, checkbox for on/off values and
    list of values selectable from dropdown list.

    On/off values could have these hide/show, working/completed
    statuses. And lists could have more specific statuses like
    draft, under review, ready, or priorities low, middle and
    high...

    And then "Views" (RFE #879781 Customisable views for
    directory compare) could be used to select which
    states/statuses to show/hide. Just imagine what you could do
    with WinMerge after that...

    Storing these "view only" statuses are problem. I think only
    way is to add per directory file containing that data.

     
  • Kimmo Varis

    Kimmo Varis - 2004-01-20
    • labels: --> 572065
     
  • Kimmo Varis

    Kimmo Varis - 2004-01-20

    Logged In: YES
    user_id=631874

    Actually date persisting sessions must be saved to project
    files. After somebody implements project files that is...

     
  • Anonymous - 2004-01-20

    Logged In: YES
    user_id=60964

    re: I think only way is to add per directory file containing
    that data.

    Well, as you often point out, we can't always write to the
    directory. We could store these in a per-user settings database?

     
  • Kimmo Varis

    Kimmo Varis - 2004-01-20

    Logged In: YES
    user_id=631874

    True.

    I was first thinking (too fast) about something like
    PaintShop Pro's browse files. But its a lot easier to have
    projects or views saved in user profile directory. One
    place, easy to manage.

     
  • Jordi Vilar

    Jordi Vilar - 2004-07-26

    Logged In: YES
    user_id=382143

    And why not using the filesystem provided metadata support?
    NTFS supports it (and future WinFS in longhorn...). This
    enables sharing all the metadata accessible from the windows
    shell (explorer, file properties, summary) and add WinMerge
    custom metadata if needed. The persistence is then handled
    by the OS. Of course, this doesn't work for Win 9x and for
    samba shares... In this case, I propose an xml file per folder,
    (shared data for all users, and no leaked data for deleted
    files/folders)
    See function StgOpenStorageEx
    (http://msdn.microsoft.com/library/en-
    us/stg/stg/stgopenstorageex.asp) and "IPropertySetStorage-
    NTFS File System Implementation"
    (http://msdn.microsoft.com/library/en-
    us/stg/stg/ipropertysetstorage_ntfs_file_system_implementatio
    n.asp) in msdn. When no such fantastic feature is available,
    the xml fall-back approach can be used.

     
  • Kimmo Varis

    Kimmo Varis - 2004-07-29

    Logged In: YES
    user_id=631874

    Some of problematic cases with this metadata (in file or in
    filesystem):
    - network shares (with slow connection)
    - read-only medias (CD-ROM, DVD-ROM)
    - flash-memories (usually FAT or FAT32)
    - read-only directories

     
  • Kimmo Varis

    Kimmo Varis - 2004-07-29
    • labels: 572065 --> Usability
     
  • Jordi Vilar

    Jordi Vilar - 2004-07-29

    Logged In: YES
    user_id=382143

    Of course, this is an enhancement, not a requirement, so,
    when not possible/available/feasible, WinMerge cannot make a
    miracle! When/Where it can be done, I think, this will be a
    nice enhancement, but WinMerge is a comparing/merging tool,
    not a filesystem metadata manager.

     
  • Kimmo Varis

    Kimmo Varis - 2004-07-29

    Logged In: YES
    user_id=631874

    I worded my last comment to sound too negative for your
    suggestion. I just meant to list some (commonly) problematic
    cases.

    Yes, that per directory metadata can be one part of solution
    here, but its not enough. Remember we compare two files or
    directories. So I can write metadata to say 'ignore these
    files in this directory'. But I cannot write (per
    file/directory) metadata to say 'I've already compared this
    file against another file in another directory'. And
    multi-session compare requires just that info.

     
  • Jordi Vilar

    Jordi Vilar - 2004-07-29

    Logged In: YES
    user_id=382143

    And what's wrong with storing this information in project files?

    I think it makes sense to store not only the files/folders to
    compare, but also the state for each file or any other
    interesting flag or user metadata, in a per project basis,
    instead of a per user basis (as you proposed) or global (as I
    proposed)

    This enables creating projects with metadata for any kind of
    media, read-only or read-write. It can be shared by sharing
    the project file (as filesystem managed metadata) or private
    to a single user (as storing in the user profile)

    I don't know the details about project files, maybe a project
    file contains both branches to compare, or maybe a project
    file contains only a branch and then you compare two
    projects... In any case, a project file can store such fags and
    user metadata. (I really like the idea of project files, when will
    they be available?)

     
  • Kimmo Varis

    Kimmo Varis - 2004-07-30

    Logged In: YES
    user_id=631874

    Nothing wrong in project files. Its just how we desing and
    define our project files. There's couple of suggestions in
    RFE '#785415 Project Files'. And I submitted patch '#1000020
    Simple project files (no GUI)'. Its only for paths to
    compare for now, but expanding to other data is easy later.
    GUI is the problem. But I hope to apply my patch to CVS soon
    (next week).

    I rather see project file having info about whole
    comparison, comparison/UI/whatever settings and other data
    we may need than part of compare (just other side).

    Ideas about what to put into project files or implementation
    or whatever (and patches!) are very welcome. :)

     
  • Kimmo Varis

    Kimmo Varis - 2005-08-11

    Logged In: YES
    user_id=631874

    I'm modifying summary for what really is requested:
    user-selectable flags.

     
  • Kimmo Varis

    Kimmo Varis - 2005-08-11
    • summary: review oriented GUI --> User-selectable flags for dir compare items
     
  • wolfing1

    wolfing1 - 2013-05-24

    I want to add that I want this functionality to allow the user to perform operations (copy/move) for the flagged files. The minimum usage I need from this enhancement is basically to mark files that are to be copied/moved. Right now I can do that with 'ctrl-click/shift-click' and the right click menu, problem is, as soon as I click on any file, the selection is obviously lost. With flags/checkmarks, you could read each file with differences in the folder compare screen, and when finished, copy everything that you flagged to the destination folder.

     
    Last edit: wolfing1 2013-05-24

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks