From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: John Task Newsgroups: gmane.emacs.devel Subject: Re: [NonGNU Elpa] New package: ETT Date: Wed, 03 May 2023 14:14:50 -0300 Message-ID: <86a5ylbadn.fsf@disroot.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40023"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 03 19:46:07 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1puGYI-000AEa-SG for ged-emacs-devel@m.gmane-mx.org; Wed, 03 May 2023 19:46:06 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1puGXT-0000Tu-KE; Wed, 03 May 2023 13:45:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1puG8i-00044B-Fs for emacs-devel@gnu.org; Wed, 03 May 2023 13:19:41 -0400 Original-Received: from knopi.disroot.org ([178.21.23.139]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1puG8f-0003yg-FR; Wed, 03 May 2023 13:19:40 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 8D798401A5; Wed, 3 May 2023 19:19:34 +0200 (CEST) X-Virus-Scanned: SPAM Filter at disroot.org Original-Received: from knopi.disroot.org ([127.0.0.1]) by localhost (disroot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DWD-vOK5pW76; Wed, 3 May 2023 19:19:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1683134373; bh=LWB36K86f4MtwEJHOTLuldjtOsjPREmUpIgWNnpCUzs=; h=From:To:Cc:Subject:In-Reply-To:Date; b=PzuQ7bagLZXTq8/PymkhQbRWa0MarEQXOl85LWJ0R+71lgbdgVFyvEeeORh0VCvlG uIr70rEq93ZhSfXxuHMbyaxktHYmmD8D2kBLn/9BdHLzkEGFYFmRnWC4gdGQBGZorO uUm7zbvWAe3XCFflkRBUvTO3koydmPKo3DJhXW096x8uclG/+AsA6yweAb91ZxojiF 5stFBSNzi6uOCldhB2a8lxD7ggFK52Ee66moQyoG612eG2rXEP+olwYwQvUE0iumGI jwfmoKRjsRV+AvmCVu+7Hkc2W1sz7ykU1J3oCvNS3x4ayE75z2lQCRl2yJPW2kOnIL QI4dwdumsf/fw== In-Reply-To: 831qjxmmtu.fsf@gnu.org Received-SPF: pass client-ip=178.21.23.139; envelope-from=q01@disroot.org; helo=knopi.disroot.org X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Wed, 03 May 2023 13:45:13 -0400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:305795 Archived-At: Eli Zaretskii writes: > Anyway, did you consider extending existing packages with those modern > features, instead of making a completely new separate package? Honestly, I didn't consider it. However, I'm seeing what timeclock.el currently does, as it is the most similar to my package, and I think I would gain very little by using it as a starter point. I'll explain why. 1. Design principles timeclock has not the same design principles. It tries to address the problem of tracking work time; that's why it has "projects", as well as functions such as timeclock-when-to-leave-string, timeclock-workday-remaining-string, et cetera. ETT tries to track time in general; it can be used in order to track what do you do on a workday, but it's also designed to track what do you read on vacations, when do you eat, and so on. 2. Conflicts Following point 1, a lot of features from timeclock and ETT conflict with each other at a basic level because of how they are designed. On ETT, there's no "clock-out", because the idea is to track everything, or everything possible at least. On timeclock, you have to leave a message when you clock-out, which doesn't make sense on ETT, not only because there's no clock-out at all but also because if you just finished eating, leaving a message is pointless. 3. Features Again, ETT has a different goal, and tries to approach it in its own way. ETT has tags; tags are not needed in timeclock and I don't really want to change that in order to support something timeclock was not designed for. ETT has goals. ETT has a parser that takes into account all the oddities of its very own .ett file. Implementing all of this for timeclock would be less efficient and would definitely break most (if not all) existent workflows. I get your intentions, but all things considered, I think everything is better as is. Best regards.