To pique Martin's interest, I'll just say that I like the original JUMP "Task" terminology. The problem with "Project", IMO is that the word is confused with the idea of "projections", at least in English. Lots of other other software uses the term "Project" too, which can be both good and bad (bad to me). I had never heard of an application using the term "Task" to describe a collection of objects, but I thought it was immediately intuitive to anyone who heard it.
regards, Larry Becker /8/07, Sunburned Surveyor <[EMAIL PROTECTED]> wrote: > Martin, > > In a message from May you wrote: "(BTW, sSometime I should write up > our original idea for the model of Projects and Tasks - I think > there's some confusion about why we chose the terminology we did.)" > > Is there any chance you would have a couple of minutes to provide a > brief explanation of the distinction between a task and a project? > > The Sunburned Surveyor > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > -- http://amusingprogrammer.blogspot.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
