emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jeff Filipovits <jrfilipovits@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: Reposting Elgantt announcement
Date: Thu, 23 Jul 2020 10:05:16 -0400	[thread overview]
Message-ID: <87eep2iaxv.fsf@gmail.com> (raw)
In-Reply-To: <87ft9iwdae.fsf@ucl.ac.uk>

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> A quick question, however.  My projects tend to be multi-year. 
> Does the
> graphical presentation provide optional control of the date 
> information
> along the top?  We often use each year as a major divider with 
> Q1..Q4
> subdivisions for quarterly views of multi-year projects.  Even 
> just
> years with month labels (JFMA...D) would be good enough but full
> month/day breakdowns as you currently have in the demo would be
> unwieldy/ugly.

Not currently an option but would not be hard to implement. Some 
of the code relies on the months to be displayed but they could be 
hidden in a text property somewhere. The vertical lines between 
months are important though, so there’s no way to get rid of 

Adding an option to hide the number line for the dates should not 
be difficult. 

If you gave me an idea of what you want it to look like I could 
figure out a way to make the top lines customizable in a way that 
could accommodate it.

Jeff Filipovits
Spears & Filipovits, LLC
1126 Ponce de Leon Avenue
Atlanta, GA 30306
678.237.9302 (direct)

All emails confidential to the fullest extent of the law.

  reply	other threads:[~2020-07-23 14:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 11:45 Reposting Elgantt announcement Russell Adams
2020-07-22 15:00 ` Jeff Filipovits
2020-07-22 15:12   ` Russell Adams
2020-07-23 13:50   ` Eric S Fraga
2020-07-23 14:05     ` Jeff Filipovits [this message]
2020-09-10 13:53 ` Bastien

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:

  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=87eep2iaxv.fsf@gmail.com \
    --to=jrfilipovits@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \


* 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


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).