emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Scott Jaderholm" <jaderholm@gmail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: Eddward DeVilla <eddward@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Duration Tally
Date: Tue, 19 Jun 2007 11:45:53 -0600	[thread overview]
Message-ID: <b2e202b30706191045p6ba385b5q7c5278b2425b095d@mail.gmail.com> (raw)
In-Reply-To: <ad8e80bfef52d434a21c479dee42455f@science.uva.nl>

On 6/19/07, Carsten Dominik <dominik@science.uva.nl> wrote:

> So the discussion must be about how you would like Org-mode to make
> use of such data.  Obviously it would be easy to write (as you
> suggest) a little function that returns all this data as, say,
> a property list.  But then you would still need to use it in
> some way.  Are you suggesting tis as a feature where some users
> (those who can write Lisp code) write their own extensions?
> That is certainly an option.  Are you also envisioning ways
> how Org-mode should use this?

I see a property list under each heading as a way of doing columns,
albeit in a less user friendly way. I can see this being useful
anywhere you have hierarchal data to which you would like to add
structure. Currently, I normally transfer it into a table, but it
would be nice to be able to leave things as a list and still define
some columns. See
http://www.omnigroup.com/images/applications/omnioutliner/features/multicolumn.jpg

Perhaps a property list has the advantage of being easier for the
programmers and being a better way to store the data in a text file,
but I think it would be really sweet if an interface were built on top
of it so that the user saw something similar to the picture above.

Carsten,
Have spreadsheet like columns for lists been discussed before, and if
so, what was the verdict?

--Scott

  parent reply	other threads:[~2007-06-19 17:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-13 13:47 Duration Tally Russell Adams
2007-06-13 15:33 ` Eddward DeVilla
2007-06-14  2:15   ` Russell Adams
2007-06-14 13:28   ` Jason F. McBrayer
2007-06-19  7:00   ` Carsten Dominik
2007-06-19 11:24     ` Russell Adams
2007-06-19 16:20     ` Eddward DeVilla
2007-06-19 17:45     ` Scott Jaderholm [this message]
2007-06-19 18:28       ` Eddward DeVilla
2007-06-22 15:56       ` Carsten Dominik
2007-06-22 19:06         ` Scott Jaderholm
2007-06-22 19:35           ` Eddward DeVilla
2007-06-13 21:58 ` Scott Jaderholm
     [not found]   ` <b71b18520706131837m42b32f5cs174d94c2b353d16d@mail.gmail.com>
2007-06-15  0:13     ` Fwd: " Eddward DeVilla
2007-06-15  6:21   ` Carsten Dominik
2007-06-19  2:16     ` Russell Adams
2007-06-19  7:02 ` Carsten Dominik
2007-06-19 11:21   ` Russell Adams
2007-06-19 13:10     ` Carsten Dominik
2007-06-19 17:12       ` Russell Adams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b2e202b30706191045p6ba385b5q7c5278b2425b095d@mail.gmail.com \
    --to=jaderholm@gmail.com \
    --cc=dominik@science.uva.nl \
    --cc=eddward@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).