First, who is going to submit a search at the same time as they're moving some individual items to arbitrary folders and a group of others to yet another place? Allowing that sort of multiple action just ....

The combination is absolutely required. I want to be able to search for messages based on a set of criteria and then organzie them into folders. Not allowing that sort of multiple action means that I wouldnt be able to do that. Which would defeat the whole purpse of this patch.

To rephrase: the idea is that you can select a set of criteria to find some messages and then have the ability to move them around as needed. If you can't combine the various parts then you have severly crippled the implementation. What good is it to me to be able to find a bunch of nodes but not be able to do something useful with them?

Some responses:

  1. No it doesnt. That would take up too much room. People can have up to 99 different folders if they like. How do you plan to fit them all on one line.
  2. Its possble ill remove the from/to option and maybe change it to some other control. I'm not aware of why you say "Comboboxes are the least usable UI control by far; avoid whenever possible." Seems to me to be a good way to avoid confusion as it shows only the option selected and doesnt distract with the options not selected.
  3. No comment. You don't seem to have grasped that _every_ view of the message inbox is a "search" of some sort. You _can't_ seperate the action of searching from the action of viewing a folder as thats how the latter is accomplished.
  4. Patches welcome.
  5. I might change the drop down folder. I might just add a delete radio button so folks with not so many messages don't need to use it. But your claim that this feature cant be useful IMO is not correct, I find it useful, in fact I wrote it because sorting out my inbox without it was proving to be incredibly annoying. And again regarding your comment about "apply actions to the result of the search", any view of your inbox is a result of a search.
  6. Yes i might lose the distinction between "trash" and "deleted". But there is no way to show how long a message has until irreversible deletion. The script is unaware of the logic that controls the deletion and only knows the "state" of the record. (FYI -3 is "user cant see the node as its deleted", -2 is "trash-bag", -1 is "deleted", 0 is "general/inbox", 1 is Archived, 2+ are user defined. This value is stored for both the sender and the receiver. When the record is in state -3 for both it is actually deleted.

Anyway, you are pmdev, put together some patches that you think improves the situation, and if they don't impact on what i feel are the requirements then ill put them into play. So lets see your improvements as a patch ok?

update: I'd like to add that I realize my comments above might sound a little testy. If so im sorry, I appreciate the time you took to feedback, and Ill do what I can with the time I have to smooth out some of the rough edges. But patches would be appreciated as they are a lot easier to evaluate than text descriptions or little ascii pictures are. (Not to say diagrams and descriptions arent useful, just patches are more so.) For all I know I've misunderstood some of your points anyway, which would be pretty difficult with code.

---
$world=~s/war/peace/g

In reply to Re^4: Searchable Inbox by demerphq
in thread Searchable Inbox by demerphq

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.