From 92d907d12e8cf855f1abd9716bb0505469a64cef Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Erick=20P=C3=A9rez=20Castellanos?= <erick.red@gmail.com>
Date: Sun, 7 Oct 2012 11:26:43 -0400
Subject: [PATCH] Updated docs and configure.ac

---
 TODO            |  2 ++
 configure.ac    |  1 +
 doc/Assumptions | 12 +++++++-----
 3 files changed, 10 insertions(+), 5 deletions(-)

diff --git a/TODO b/TODO
index 9c425026..c0d57c33 100644
--- a/TODO
+++ b/TODO
@@ -5,6 +5,8 @@ TODO
    surpass 31 days), when drawing(maybe mark in other color) and selecting, etc.
  !!! Fix GcalMonthView to take into account 31 days when in need of 42 cells
    instead of 35.
+ - Review all-day checkbox and date/time fields interaction in GcalEditDialog
+ - Check width of read-only layer in GcalEditDialog
  - Review the real need of GcalFloatingContainer
  - Review/check the adding of a new source live.
  - Review size/resize of GcalEventView widget
diff --git a/configure.ac b/configure.ac
index 9dfcfa12..1a348280 100644
--- a/configure.ac
+++ b/configure.ac
@@ -104,6 +104,7 @@ echo "
 
         prefix:    ${prefix}
         compiler:  ${CC}
+	flags:     ${CFLAGS} ${CPPFLAGS} ${CALENDAR_CFLAGS} ${LDFLAGS} ${CALENDAR_LIBS} ${LIBS}
 
         Now type 'make' to build $PACKAGE
 "
diff --git a/doc/Assumptions b/doc/Assumptions
index 5c9b1ce5..c4859f4b 100644
--- a/doc/Assumptions
+++ b/doc/Assumptions
@@ -1,17 +1,19 @@
 # Some words about how do we work so far #
 
-1. We load calendar sources from Online Accounts.
-   (So we'll need a view for adding sources, since I refuse
-   to read some gconf key from evolution to load some others.
-   Maybe that's will be the way eventually, but well)
+1. We load calendar sources from Online Accounts, and the default sources.
+   (So we'll need a view for adding sources)
 
 2. Using sexp for getting objects between two dates:
    (occur-in-time-range? (make-time "20001116T230000Z") (make-time "20001217T230000Z") "America/Havana")
 
 3. We'll merge all the description from `e_cal_component_get_description_list`
-   into one big description for an event.
+   into one big description for an event. Actually the thing is for now we'll just handle E_CAL_COMPONENT_EVENT
+   any other VType will cause unknown behavior
 
 4. I've done a lot of simplication from what the API of e-d-s offers to how we
    show alarms of events. The code is marked with comments inside GcalManager.
    Among other stuff we'll show only reminders set before the event, and just
    before the start time of the event.
+
+5. All-day events are those that fall under one of these conditions:
+   - Both, start date and end date are marked with is_date, so doesn't have time specified