lp:gtg

Created by Izidor Matušov on 2014-03-30 and last modified on 2015-05-28
Get this branch:
bzr branch lp:gtg

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Gtg developers
Project:
Getting Things GNOME!
Status:
Mature

Import details

Import Status: Reviewed

This branch is an import of the HEAD branch of the Git repository at https://github.com/getting-things-gnome/gtg.git.

The next import is scheduled to run in 12 minutes.

Last successful import was 5 hours ago.

Import started 5 hours ago on pear and finished 5 hours ago taking 20 seconds — see the log
Import started 11 hours ago on pear and finished 11 hours ago taking 20 seconds — see the log
Import started 19 hours ago on pear and finished 19 hours ago taking 20 seconds — see the log
Import started on 2015-05-28 on pear and finished on 2015-05-28 taking 25 seconds — see the log
Import started on 2015-05-28 on pear and finished on 2015-05-28 taking 20 seconds — see the log
Import started on 2015-05-27 on russkaya and finished on 2015-05-27 taking 30 seconds — see the log
Import started on 2015-05-27 on pear and finished on 2015-05-27 taking 20 seconds — see the log
Import started on 2015-05-27 on pear and finished on 2015-05-27 taking 20 seconds — see the log
Import started on 2015-05-27 on pear and finished on 2015-05-27 taking 25 seconds — see the log
Import started on 2015-05-26 on pear and finished on 2015-05-26 taking 25 seconds — see the log

Recent revisions

105. By Izidor Matušov on 2015-05-28

Merge pull request #110 from jakubbrindza/headerbar

Headerbar implementation into GTG!

104. By Izidor Matušov <email address hidden> on 2015-05-23

Ignore closed subtasks for get_urgency_date

Let's have a task tree:

 - A (due: 2013-12-17)
 -- B (closed, due: 2013-12-05)
 - C (due: 2013-12-07)

Unless closed subtasks are ignored, urgent date for A is 2013-12-05 and is more urgent than C. However, after B is closed, the urgent date is only 2013-12-17 and it is false.

This commit fixes the issue and cleans get_urgent_date method.

See original Launchpad bug: https://bugs.launchpad.net/gtg/+bug/1258451

Fixes #69

103. By Àlex Magaz on 2015-05-23

Increase the days limit of the Closed tasks remover plugin to high enough one.

Fixes #83, #84

102. By Izidor Matušov <email address hidden> on 2015-05-22

Refactor access to configuration

The code is now simpler and are covered by unit tests. Yay!

101. By Izidor Matušov on 2015-05-21

Refactor translations, directories & CoreConfig

All of that functionality was hidden in GTG/__init__.py and
GTG/core/__init__.py that it makes hard to find it for newcomers.
Provided features are non-trivial and should be in separate files:

  - translations are now in GTG.core.translations
  - CoreConfig is now in GTG.core.config
  - directories are now in GTG.core.dirs

CoreConfig was breaking single responsibility principle as it was
providing configuration, constants for directories and various other
constants. CoreConfig is now clean:

   - it handles only configuration
   - all information about directories is stored in single place
     (GTG.core.dirs)
   - TAG constants were moved to GTG.core.tag

100. By Izidor Matušov <email address hidden> on 2015-05-21

Ignore vim temp files and local liblarch version

99. By Izidor Matušov <email address hidden> on 2015-05-21

Handle changing tasks/deleting tasks via liblarch

Browser and editor were asking manager to change status of a task/delete
a task. That approach doesn't scale as there are other ways how to
change that (e.g. via DBUS). Proper solution is to subscribe to liblarch
callbacks for everytime when a task is modified or deleted.

Result is manager object that has one less responsibility and thus
resulting in cleaner architecture.

98. By Izidor Matušov <email address hidden> on 2015-05-21

Pass arguments like -d to ./scripts/debug.sh

97. By Izidor Matušov <email address hidden> on 2015-05-12

Fix PEP8 and pyflakes errors

96. By Izidor Matušov on 2015-05-12

Fix infinite loop when openining up an editor

In the newer Gtk (tested on 3.14 that is included in Ubuntu 15.04), there was a slight change in semantics of forward_word_end. If there is a trailing white space, forward_word_end doesn't move to the end of buffer as it is not a word per se, but returns an error (value False).

The following script runs in infinite loop under new Gtk:

```python

from gi.repository import Gtk

buf = Gtk.TextBuffer()
buf.set_text("word ")
it, end = buf.get_bounds()

while (it.get_offset() < end.get_offset()) and (it.get_char() != '\0'):
    it.forward_word_end()
    prev = it.copy()
    prev.backward_word_start()
    print('word: "{}"'.format(buf.get_text(prev, it, True)))
```

Fix is to check the return value of it.forward_word_end() in while loop:

```python
while it.forward_word_end():
    prev = it.copy()
    prev.backward_word_start()
    print('word: "{}"'.format(buf.get_text(prev, it, True)))
```

Fixes #90

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.