use Perl

• Requirements (Score:1)

  by koschei (147)

  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
  • Re:Requirements (Score:1)

    by belg4mit (967)

    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?
    • Re:Requirements (Score:1)

      by belg4mit (967)

      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 sup

      --
      Were that I say, pancakes?
      • Re:Requirements (Score:1)

        by koschei (147)

        Perhaps that means a solution should be developed?
        
        Hmm. Sod it. Mailing list time. subscribe [mailto], archive [anu.edu.au], post [mailto] --- closed to non-members (don't yet have SpamAssassin installed).
        
        

        --
          ---ict / Spoon
    • Re:Requirements (Score:2)

      by Matts (1087)

      FWIW, I've started using my POD Wiki for my Todo list. This enables me to add many different structures, and also allows me the freedom to create links from ideas to full blown project pages.
      
      I've only just started doing it, so I'll know better how it's going in about 6 months!
      • Re:Requirements (Score:2)

        by belg4mit (967)

        How well does it work?
        I haven't gotten much done with this project.
        
        I was just thinking about it today, and decided
        to start working on the transports soon. Had
        some other ideas too. Like using GPG. And maybe
        using MH mail as a possible backend/interface.
        

        --
        Were that I say, pancakes?
        • Re:Requirements (Score:2)

          by Matts (1087)

          It works well, depending on your expectations. Remember a Wiki is just a big notepad with hyperlinks. The one advantage it gives me is I can access and edit it from anywhere. (Of course being a Wiki, so could anybody else ;-)
• RT. Rocks. (Score:2)

  by Simon (89)

  RT [perl.org] will probably do what you want.
  • Re:RT. Rocks. (Score:1)

    by belg4mit (967)

    Unfortunately not. The interface is
    more than I am hoping for. It also
    seems to be lacking some of the other
    interfaces (mail etc.). What probably
    makes it seem like a good fit are
    things like priority and completion
    date, but those are not key features.
    thanks though.
    
    PS> When's the modulre request list coming?

    --
    Were that I say, pancakes?