unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Wiegley <johnw@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: John Task <q01@disroot.org>,  emacs-devel@gnu.org
Subject: Re: Extending timeclock.el
Date: Sat, 06 May 2023 11:35:30 -0700	[thread overview]
Message-ID: <m2jzxl1f65.fsf@newartisans.com> (raw)
In-Reply-To: <83ild6gc54.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 06 May 2023 10:19:35 +0300")

>>>>> Eli Zaretskii <eliz@gnu.org> writes:

>> I'll eventually contact the original author as well, but I wanted to know
>> of any other opinions here first.

> John Wiegley, the original author is somewhat busy these days, but we can
> add him to this discussion right away. Here, done.

Hi fellow John, I'm happy to hear you're thinking of extending timeclock. It
only ever strived to be the most basic form of data collection possible, with
the hope that other functionality and UIs could be built on top of it. My
ledger tool, for example, directly reads timelog files in order to provide
reports summarized by week, month, account, etc.

If you do extend the _format_, it's likely you may break some of the other
tools that process timelog data. So if you choose to make an enriched format,
it would be useful if you provided a way to export this data back to flat
timelog form (such as by stripping comments). Then I could go from
timeclock-modern format -> timeclock format -> ledger, for example.

Otherwise, I'm available here by e-mail, and always happy to provide context
that may help with your decision making. Best of luck with getting this new
code ultimately into Emacs or ELPA!

--
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2



  reply	other threads:[~2023-05-06 18:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05 19:15 Extending timeclock.el John Task
2023-05-06  6:09 ` Philip Kaludercic
2023-05-06  7:19 ` Eli Zaretskii
2023-05-06 18:35   ` John Wiegley [this message]
2023-05-06 18:48     ` Ihor Radchenko
2023-05-06 18:48       ` John Wiegley
2023-05-06 19:02         ` Ihor Radchenko
2023-05-06 19:00           ` John Wiegley
2023-05-06 19:09       ` Eli Zaretskii
2023-05-06 19:22         ` Ihor Radchenko
2023-05-06 19:23           ` John Wiegley
2023-05-06 22:10   ` Mike Kupfer
2023-05-09 16:44     ` Mike Kupfer
  -- strict thread matches above, loose matches on Subject: below --
2023-05-06 15:47 John Task
2023-05-06 16:53 ` Eli Zaretskii
2023-05-06 16:46 John Task
2023-05-06 18:35 John Task
2023-05-06 19:21 John Task

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=m2jzxl1f65.fsf@newartisans.com \
    --to=johnw@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=q01@disroot.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.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).