Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • If you bash out some requirements (like how you want to use it, how much information you're likely to be wanting, whether you'll be wanting alerts, prioritising (by importance, by time it has been on the list, by function of the previous two, whatever), and all that sort of stuff), then we could be near a start.

    I'm tempted to do the 'start a committee' approach, make a mailing list (can do myself; with web archive), invite people and see what people want in a TODO program. I, for one, also wouldn't mind on
    --
      ---ict / Spoon
    • I'll put more thought into a an additonal comment later, but to expand...

      One reason I tend to email myself so many little
      notes is I have a custom CLI mailer I wrote
      (http://web.mit.edu/belg4mit/bin/mailer)
      It ought to be about that easy to add an entry.
      (I should add the ability to invoke EDITOR)

      So there might be multiple interfaces, given
      the requirements of incredible ease of use,
      and access form anywhere. I'd guess a web interface, and some kind of CLI that might
      map over it.

      Another thing is that management
      --
      Were that I say, pancakes?
      • A quick bit, if a CLI is a handy wrapper
        over a web interface (security in the web
        (outside of exploits) is left to the end user)
        then one needs to take some kind of security
        into consideration. Entering a user/pass
        everytime could be optional, but is not
        convenient (or even say path to a key).
        Probably an INI File for storing the info.
        Likewise, perhaps the ability to bypass the
        web interface if the database is local,
        or the database is listening to an
        socket that is accessible from the client.
        Hrmm, ssh-tunnel?

        I suppose it seems I'm getting wrapped up on tangential details... Or maybe this is simply
        quite an involved thing to do well, which while
        not a problem, might explain why there are
        few solutions.
        --
        Were that I say, pancakes?