emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Leo Ufimtsev <lufimtse@redhat.com>
To: Xavier Maillard <xavier@maillard.im>
Cc: Rainer Stengele <rainer.stengele@online.de>, emacs-orgmode@gnu.org
Subject: Re: lots of CLOCK lines displayed when opening a TODO
Date: Thu, 12 Mar 2015 10:12:09 -0400 (EDT)	[thread overview]
Message-ID: <776285585.20509925.1426169529129.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <86ioe6ephn.fsf@kcals2.maillard.im>

>> (org-drawers
>>    (quote
>>     ("FURTHER_READING" "THEORY" "TASKS" "INFO" "TIP" "NOTE" "EG" "LINKS" "APPENDIX" "DETAILS" "PROPERTIES" "CLOCK" "LOGBOOK" "RESULTS" "TASKARCHIVE" "SOURCE" "TROUBLESHOOTING")))

>OMG ! All of them are used ?
:-D,  I need to consolidate some of those. Many are left overs from the distant past. 


My todo list is publicly viewable:
leoufimtsev.github.io./org/dev.org

But below might be a more "typical" task.  
You might notice that most of my time stamps are ~30mins long. That's because I work in 30 minute time blocks (like pomodoro with 5 mins extra).
I use org-pomodoro with some customizations (e.g notifications upon completion, stop/continue functionality etc..). 


I then have a 'last week' report that shows me what I've done the week before so I can use that to make my weekly reports.
#+BEGIN: clocktable  :tstart "<-6d>" :tend "<now>" :scope agenda-with-archives :narrow 85 :formatter my-org-clocktable-notodo :maxlevel 3 :fileskip0

|---------+---------------------------------------------------------------------------------------+---------+-------+------|
| dev.org | *File time*                                                                           | *15:29* |       |      |
|         | Dev                                                                                   |   12:55 |       |      |
......
#+END:
(the formatter function trims out 'TODO' keywords). 




*** HOLD [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=461616][Bug 461616 – {GTK3} Combo improvements in background/foreground for gtk3]]
SCHEDULED: <2015-03-23 Mon>
:LOGBOOK:  
- Note taken on [2015-03-11 Wed 12:38] \\
  changed bits as per Alex's comments. Awaiting Alex approval.
CLOCK: [2015-03-11 Wed 11:57]--[2015-03-11 Wed 12:27] =>  0:30
CLOCK: [2015-03-11 Wed 11:48]--[2015-03-11 Wed 11:49] =>  0:01
- Note taken on [2015-03-10 Tue 14:25] \\
  awaiting review by alex.
CLOCK: [2015-03-10 Tue 13:45]--[2015-03-10 Tue 14:15] =>  0:30
CLOCK: [2015-03-10 Tue 11:59]--[2015-03-10 Tue 12:29] =>  0:30
CLOCK: [2015-03-10 Tue 11:25]--[2015-03-10 Tue 11:55] =>  0:30
CLOCK: [2015-03-09 Mon 16:52]--[2015-03-09 Mon 17:41] =>  0:49
CLOCK: [2015-03-09 Mon 16:01]--[2015-03-09 Mon 16:35] =>  0:34
CLOCK: [2015-03-09 Mon 15:21]--[2015-03-09 Mon 15:51] =>  0:30
CLOCK: [2015-03-09 Mon 14:33]--[2015-03-09 Mon 15:03] =>  0:30
CLOCK: [2015-03-09 Mon 11:50]--[2015-03-09 Mon 12:52] =>  1:02
CLOCK: [2015-03-09 Mon 11:11]--[2015-03-09 Mon 11:41] =>  0:30
CLOCK: [2015-03-06 Fri 16:31]--[2015-03-06 Fri 17:01] =>  0:30
CLOCK: [2015-03-06 Fri 14:19]--[2015-03-06 Fri 14:49] =>  0:30
CLOCK: [2015-03-06 Fri 13:45]--[2015-03-06 Fri 14:15] =>  0:30
CLOCK: [2015-03-06 Fri 10:53]--[2015-03-06 Fri 12:56] =>  2:03
CLOCK: [2015-03-05 Thu 16:43]--[2015-03-05 Thu 17:30] =>  0:47
CLOCK: [2015-03-05 Thu 16:01]--[2015-03-05 Thu 16:31] =>  0:30
CLOCK: [2015-03-05 Thu 14:25]--[2015-03-05 Thu 15:00] =>  0:35
CLOCK: [2015-03-05 Thu 12:43]--[2015-03-05 Thu 13:13] =>  0:30
CLOCK: [2015-03-05 Thu 12:12]--[2015-03-05 Thu 12:42] =>  0:30
CLOCK: [2015-03-05 Thu 11:56]--[2015-03-05 Thu 12:04] =>  0:08
CLOCK: [2015-03-05 Thu 11:11]--[2015-03-05 Thu 11:41] =>  0:30
CLOCK: [2015-03-04 Wed 16:01]--[2015-03-04 Wed 16:07] =>  0:06
CLOCK: [2015-03-04 Wed 15:35]--[2015-03-04 Wed 15:37] =>  0:02
CLOCK: [2015-03-04 Wed 15:07]--[2015-03-04 Wed 15:35] =>  0:28
CLOCK: [2015-03-04 Wed 13:47]--[2015-03-04 Wed 14:17] =>  0:30
CLOCK: [2015-03-04 Wed 12:35]--[2015-03-04 Wed 13:04] =>  0:29
:END:      
:PROPERTIES:
:Effort:   4:00
:END:      
- [X] Write/find test cases.
  - Info: Test_*Control : test_setForeground... tests bits.
   :DETAILS:
#+BEGIN_SRC java
	Color color = new Color(control.getDisplay(), 255, 0, 0);
	control.setForeground(color);
	assertEquals(color, control.getForeground());
	control.setForeground(null);
	assertTrue(!control.getForeground().equals(color));
	color.dispose();
#+END_SRC 
:END:
- [X] change the setForeground method so that it doesn't use gdkcolor. 
  - [X] either an if/else gtk3 block, or refer to widget's implementation.
- [X] Add color test cases to combo's junit test suite.
- [-] fix background color error on Junit on GTK3.
  - [-] Looks on gtk3:
    - [X] Before my change:
      - [X] SWT.NONE   [[./img/img_2015_03_05__16_17_00.png]] (entries are not colored) Backgrounds don't match. 
      - [X] SWT.READ_ONLY   [[./img/img_2015_03_05__16_19_45.png]] (entries not coloured) Backgrounds match.
    - [ ] After my fix:
      ....

- [X] Try to make all g_object_set functinos dynamic. 
  - [X] Try to find other dynamic functions that are overloaded. 
  - [X] overload all g_object_set. *didn't work*
    - [X] inspect os.c

- Investigate if backgruonds match in GTK2 before my fix.

- [X] Add custom g_object_set_gtk3 Function to os_custom.h and os_custom.c that translates to GdkRGBA
  - [X] Added swt_custom_leo_function to os_custom.c and os_custom.h
        that works differently depending on os. 
  - [X] Write custom g_object_set_gtk3 function that does translation.


 
- [X] investigate pre-launch warning messages?
  - [X] Seem to occur. Try running snippet without printing messages.

- [X] pass criteria:
  - [X] All text is red on gtk2/gtk3. 

- [ ] weed out PRE_GTK3 and styleIsReadOnly








Let me know if you have any questions.


Leo Ufimtsev | Intern Software Engineer @ Eclipse Team

----- Original Message -----
From: "Xavier Maillard" <xavier@maillard.im>
To: "Leo Ufimtsev" <lufimtse@redhat.com>
Cc: "Rainer Stengele" <rainer.stengele@online.de>, emacs-orgmode@gnu.org
Sent: Thursday, March 12, 2015 1:47:32 AM
Subject: Re: [O] lots of CLOCK lines displayed when opening a TODO

Hello Leo,

Leo Ufimtsev <lufimtse@redhat.com> writes:

> I log everything into the logbook. Clocktimes, state changes, dated notes when I put an item on hold.
> I found it too tedious to move things around.

Would you mind producing a "typical" TODO to see how it looks like ?
This is a topic where I am not (yet) very comfortable with. I tend to
put notes and so on here and there in my TODOs and my todo list is
slowly going crappy :)

> (org-drawers
>    (quote
>     ("FURTHER_READING" "THEORY" "TASKS" "INFO" "TIP" "NOTE" "EG" "LINKS" "APPENDIX" "DETAILS" "PROPERTIES" "CLOCK" "LOGBOOK" "RESULTS" "TASKARCHIVE" "SOURCE" "TROUBLESHOOTING")))

OMG ! All of them are used ?

Regards
-- Xavier.

  reply	other threads:[~2015-03-12 14:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 15:46 lots of CLOCK lines displayed when opening a TODO Rainer Stengele
2015-03-05  5:14 ` Richard Lawrence
2015-03-05  8:02 ` Loris Bennett
2015-03-11 14:58   ` Rainer Stengele
2015-03-12  8:03     ` Loris Bennett
2015-03-12 12:14       ` Nick Dokos
2015-03-12 14:17         ` Leo Ufimtsev
2015-03-12 12:59       ` Rainer Stengele
2015-03-12 13:39         ` Loris Bennett
2015-03-13 12:12           ` Rainer Stengele
2015-03-05 15:11 ` Leo Ufimtsev
2015-03-12  5:47   ` Xavier Maillard
2015-03-12 14:12     ` Leo Ufimtsev [this message]
2015-03-14  5:49       ` Xavier Maillard

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=776285585.20509925.1426169529129.JavaMail.zimbra@redhat.com \
    --to=lufimtse@redhat.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rainer.stengele@online.de \
    --cc=xavier@maillard.im \
    /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).