Reminders for Events

.gitignore

@@ -1 +1,3 @@
-objects*/
+main/objects*/
+daemon/objects*/
+Calendar.pld

daemon/Makefile

@@ -0,0 +1,146 @@
+## Haiku Generic Makefile v2.6 ##
+
+## Fill in this file to specify the project being created, and the referenced
+## Makefile-Engine will do all of the hard work for you. This handles any
+## architecture of Haiku.
+##
+## For more information, see:
+## file:///system/develop/documentation/makefile-engine.html
+
+# The name of the binary.
+NAME = CalendarDaemon
+
+# The type of binary, must be one of:
+#	APP:	Application
+#	SHARED:	Shared library or add-on
+#	STATIC:	Static library archive
+#	DRIVER: Kernel driver
+TYPE = APP
+
+# If you plan to use localization, specify the application's MIME signature.
+APP_MIME_SIG = application/x-vnd.CalendarDaemon
+
+#	The following lines tell Pe and Eddie where the SRCS, RDEFS, and RSRCS are
+#	so that Pe and Eddie can fill them in for you.
+#%{
+# @src->@
+
+#	Specify the source files to use. Full paths or paths relative to the
+#	Makefile can be included. All files, regardless of directory, will have
+#	their object files created in the common object directory. Note that this
+#	means this Makefile will not work correctly if two source files with the
+#	same name (source.c or source.cpp) are included from different directories.
+#	Also note that spaces in folder names do not work well with this Makefile.
+SRCS = \
+	src/CalendarDaemon.cpp \
+	../main/src/model/Event.cpp \
+	../main/src/model/Category.cpp \
+	../main/src/utils/ColorConverter.cpp \
+	../main/src/utils/ResourceLoader.cpp \
+	../main/src/db/QueryDBManager.cpp
+
+
+#	Specify the resource definition files to use. Full or relative paths can be
+#	used.
+RDEFS = src/CalendarDaemon.rdef
+
+
+#	Specify the resource files to use. Full or relative paths can be used.
+#	Both RDEFS and RSRCS can be utilized in the same Makefile.
+RSRCS =
+
+
+# End Pe/Eddie support.
+# @<-src@
+#%}
+
+#%}
+
+#	Specify libraries to link against.
+#	There are two acceptable forms of library specifications:
+#	-	if your library follows the naming pattern of libXXX.so or libXXX.a,
+#		you can simply specify XXX for the library. (e.g. the entry for
+#		"libtracker.so" would be "tracker")
+#
+#	-	for GCC-independent linking of standard C++ libraries, you can use
+#		$(STDCPPLIBS) instead of the raw "stdc++[.r4] [supc++]" library names.
+#
+#	- 	if your library does not follow the standard library naming scheme,
+#		you need to specify the path to the library and it's name.
+#		(e.g. for mylib.a, specify "mylib.a" or "path/mylib.a")
+LIBS = be tracker shared localestub sqlite3 bnetapi network netservices $(STDCPPLIBS)
+
+#	Specify additional paths to directories following the standard libXXX.so
+#	or libXXX.a naming scheme. You can specify full paths or paths relative
+#	to the Makefile. The paths included are not parsed recursively, so
+#	include all of the paths where libraries must be found. Directories where
+#	source files were specified are	automatically included.
+LIBPATHS =
+
+#	Additional paths to look for system headers. These use the form
+#	"#include <header>". Directories that contain the files in SRCS are
+#	NOT auto-included here.
+SYSTEM_INCLUDE_PATHS = \
+	$(shell findpaths -e B_FIND_PATH_HEADERS_DIRECTORY private/interface) \
+	$(shell findpaths -e B_FIND_PATH_HEADERS_DIRECTORY private/netservices) \
+	$(shell findpaths -e B_FIND_PATH_HEADERS_DIRECTORY private/shared) \
+	$(shell findpaths -e B_FIND_PATH_HEADERS_DIRECTORY private/support)
+
+#	Additional paths paths to look for local headers. These use the form
+#	#include "header". Directories that contain the files in SRCS are
+#	automatically included.
+LOCAL_INCLUDE_PATHS =
+
+#	Specify the level of optimization that you want. Specify either NONE (O0),
+#	SOME (O1), FULL (O3), or leave blank (for the default optimization level).
+OPTIMIZE := FULL
+
+# 	Specify the codes for languages you are going to support in this
+# 	application. The default "en" one must be provided too. "make catkeys"
+# 	will recreate only the "locales/en.catkeys" file. Use it as a template
+# 	for creating catkeys for other languages. All localization files must be
+# 	placed in the "locales" subdirectory.
+LOCALES = en
+
+#	Specify all the preprocessor symbols to be defined. The symbols will not
+#	have their values set automatically; you must supply the value (if any) to
+#	use. For example, setting DEFINES to "DEBUG=1" will cause the compiler
+#	option "-DDEBUG=1" to be used. Setting DEFINES to "DEBUG" would pass
+#	"-DDEBUG" on the compiler's command line.
+DEFINES =
+
+#	Specify the warning level. Either NONE (suppress all warnings),
+#	ALL (enable all warnings), or leave blank (enable default warnings).
+WARNINGS =
+
+#	With image symbols, stack crawls in the debugger are meaningful.
+#	If set to "TRUE", symbols will be created.
+SYMBOLS :=
+
+#	Includes debug information, which allows the binary to be debugged easily.
+#	If set to "TRUE", debug info will be created.
+DEBUGGER :=
+
+#	Specify any additional compiler flags to be used.
+COMPILER_FLAGS =
+
+#	Specify any additional linker flags to be used.
+LINKER_FLAGS =
+
+#	Specify the version of this binary. Example:
+#		-app 3 4 0 d 0 -short 340 -long "340 "`echo -n -e '\302\251'`"1999 GNU GPL"
+#	This may also be specified in a resource.
+APP_VERSION :=
+
+#	(Only used when "TYPE" is "DRIVER"). Specify the desired driver install
+#	location in the /dev hierarchy. Example:
+#		DRIVER_PATH = video/usb
+#	will instruct the "driverinstall" rule to place a symlink to your driver's
+#	binary in ~/add-ons/kernel/drivers/dev/video/usb, so that your driver will
+#	appear at /dev/video/usb when loaded. The default is "misc".
+DRIVER_PATH =
+
+## Include the Makefile-Engine
+DEVEL_DIRECTORY := \
+	$(shell findpaths -r "makefile_engine" B_FIND_PATH_DEVELOP_DIRECTORY)
+include $(DEVEL_DIRECTORY)/etc/makefile-engine

daemon/README.md

@@ -0,0 +1,2 @@
+# calendar_daemon
+A daemon app which will be responsible for sending reminders for the Calendar Application on Haiku OS

daemon/locales/en.catkeys

@@ -0,0 +1,22 @@
+1	English	application/x-vnd.CalendarDaemon	3971020027
+Couldn't restore the deleted event― you might want to look in the Trash to find this event and manually restore it.	QueryDBManager		Couldn't restore the deleted event― you might want to look in the Trash to find this event and manually restore it.
+Couldn't open event file because permission was denied. It usually means that you don't have read permissions to the event file or its parent directory, usually within the settings directory.Find out the file's location and try changing its permissions.	QueryDBManager		Couldn't open event file because permission was denied. It usually means that you don't have read permissions to the event file or its parent directory, usually within the settings directory.Find out the file's location and try changing its permissions.
+Event file	QueryDBManager		Event file
+{0, plural,=1{1 hour!}other{# hours!}}	Daemon		{0, plural,=1{1 hour!}other{# hours!}}
+OK	QueryDBManager		OK
+Birthday	QueryDBManager		Birthday
+Couldn't restore the deleted event― it seems that it couldn't be found or doesn't exist. You might want to look in the Trash to find this event and manually restore it.	QueryDBManager		Couldn't restore the deleted event― it seems that it couldn't be found or doesn't exist. You might want to look in the Trash to find this event and manually restore it.
+{0, plural,=1{1 second!}other{# seconds!}}	Daemon		{0, plural,=1{1 second!}other{# seconds!}}
+Couldn't open event file because the path is not specified. It usually means that the programmer made a mistake. There is nothing you can do about it. Sorry.	QueryDBManager		Couldn't open event file because the path is not specified. It usually means that the programmer made a mistake. There is nothing you can do about it. Sorry.
+{0, plural,=1{1 minute!}other{# minutes!}}	Daemon		{0, plural,=1{1 minute!}other{# minutes!}}
+Couldn't open category file because permission was denied. It usually means that you don't have read permissions to the event file or its parent directory, usually within the settings directory.Find out the file's location and try changing its permissions.	QueryDBManager		Couldn't open category file because permission was denied. It usually means that you don't have read permissions to the event file or its parent directory, usually within the settings directory.Find out the file's location and try changing its permissions.
+Restoring event	QueryDBManager		Restoring event
+Couldn't move the event to Trash― you might want to use a Tracker query to find this event and manually delete it.	QueryDBManager		Couldn't move the event to Trash― you might want to use a Tracker query to find this event and manually delete it.
+Category file	QueryDBManager		Category file
+Couldn't open category file because the path is not specified. It usually means that the programmer made a mistake. There is nothing you can do about it. Sorry.	QueryDBManager		Couldn't open category file because the path is not specified. It usually means that the programmer made a mistake. There is nothing you can do about it. Sorry.
+Couldn't move the event to trash― it seems that the event couldn't be found or doesn't exist. You might want to use a Tracker query to find this event and manually delete it.	QueryDBManager		Couldn't move the event to trash― it seems that the event couldn't be found or doesn't exist. You might want to use a Tracker query to find this event and manually delete it.
+Default	QueryDBManager		Default
+There is not enough memory available on your system to save the  category file. If you want to have event updates saved, try closing a fewapplications and try again.	QueryDBManager		There is not enough memory available on your system to save the  category file. If you want to have event updates saved, try closing a fewapplications and try again.
+Calendar notification!\n\nEvent:\t%eventName%\nPlace:\t%eventPlace%\n\nThe event starts in 	Daemon		Calendar notification!\n\nEvent:\t%eventName%\nPlace:\t%eventPlace%\n\nThe event starts in 
+There is not enough memory available on your system to save the event file. If you want to have event updates saved, try closing a few applications and try again.	QueryDBManager		There is not enough memory available on your system to save the event file. If you want to have event updates saved, try closing a few applications and try again.
+Moving to Trash	QueryDBManager		Moving to Trash