Merge branch 'Etar-Group/master' into test-merge

<manifest xmlns:android="http://schemas.android.com/apk/res/android"

    package="foundation.e.calendar"

    android:installLocation="auto"

    android:versionCode="15"

    android:versionName="1.0.13">

    android:versionCode="17"

    android:versionName="1.0.15">

<!--         android:sharedUserLabel="@string/app_label"> -->

    <!--

    <uses-permission android:name="android.permission.WAKE_LOCK" />

    <uses-permission android:name="android.permission.USE_CREDENTIALS" />

    <uses-permission android:name="android.permission.READ_SYNC_SETTINGS" />

    <uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />

    <uses-permission android:name="com.google.android.googleapps.permission.GOOGLE_AUTH.mail" />

                <action android:name="android.intent.action.TIME_SET" />

                <data android:scheme="content" />

            </intent-filter>

            <intent-filter>

                <action android:name="android.intent.action.BOOT_COMPLETED" />

            </intent-filter>

            <intent-filter>

                <action android:name="android.intent.action.LOCALE_CHANGED" />

            </intent-filter>

        <service android:name="com.android.calendar.alerts.SnoozeAlarmsService" />

        <service android:name="com.android.calendar.alerts.InitAlarmsService" />

        <!-- Declarations for the widget -->

        <receiver android:name="com.android.calendar.widget.CalendarAppWidgetProvider" android:label="@string/gadget_title">

        <!--receiver android:name="com.android.calendar.widget.CalendarAppWidgetProvider" android:label="@string/gadget_title">

            <intent-filter>

                <action android:name="android.appwidget.action.APPWIDGET_UPDATE" />

                <action android:name="com.android.calendar.APPWIDGET_UPDATE" />

        <service android:name="com.android.calendar.widget.CalendarAppWidgetService"

            android:exported="false"

            android:permission="android.permission.BIND_REMOTEVIEWS">

        </service>

        </service-->

        <service android:name="com.android.calendar.AsyncQueryServiceHelper" />

# Copyright (C) 2007 The Android Open Source Project

#

# Licensed under the Apache License, Version 2.0 (the "License");

# you may not use this file except in compliance with the License.

# You may obtain a copy of the License at

#

#      http://www.apache.org/licenses/LICENSE-2.0

#

# Unless required by applicable law or agreed to in writing, software

# distributed under the License is distributed on an "AS IS" BASIS,

# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

# See the License for the specific language governing permissions and

# limitations under the License.

#

# If you don't need to do a full clean build but would like to touch

# a file or delete some intermediate files, add a clean step to the end

# of the list.  These steps will only be run once, if they haven't been

# run before.

#

# E.g.:

#     $(call add-clean-step, touch -c external/sqlite/sqlite3.h)

#     $(call add-clean-step, rm -rf $(PRODUCT_OUT)/obj/STATIC_LIBRARIES/libz_intermediates)

#

# Always use "touch -c" and "rm -f" or "rm -rf" to gracefully deal with

# files that are missing or have been moved.

#

# Use $(PRODUCT_OUT) to get to the "out/target/product/blah/" directory.

# Use $(OUT_DIR) to refer to the "out" directory.

#

# If you need to re-do something that's already mentioned, just copy

# the command and add it to the bottom of the list.  E.g., if a change

# that you made last week required touching a file and a change you

# made today requires touching the same file, just copy the old

# touch step and add it to the end of the list.

#

# ************************************************

# NEWER CLEAN STEPS MUST BE AT THE END OF THE LIST

# ************************************************

# For example:

#$(call add-clean-step, rm -rf $(OUT_DIR)/target/common/obj/APPS/AndroidTests_intermediates)

#$(call add-clean-step, rm -rf $(OUT_DIR)/target/common/obj/JAVA_LIBRARIES/core_intermediates)

#$(call add-clean-step, find $(OUT_DIR) -type f -name "IGTalkSession*" -print0 | xargs -0 rm -f)

#$(call add-clean-step, rm -rf $(PRODUCT_OUT)/data/*)

$(call add-clean-step, rm -rf $(OUT_DIR)/out/target/common/obj/APPS/Calendar_intermediates)

# ************************************************

# NEWER CLEAN STEPS MUST BE AT THE END OF THE LIST

# ************************************************

![Etar Calendar](metadata/animation.gif)

## Why?

Well, I wanted a simple, material designed and state of the art open source calendar that anyone can make it better.

Well, I wanted a simple, material designed and state of the art open source calendar that anyone can make better.

## Special thanks

- Week, day & agenda view.

- Uses Android calendar sync. Works with Google Calendar, Exchange, etc.

- Material designed.

- Agenda widget.

- -Agenda widget.- (disabled until #373 and #374 are fixed. Use [Calendar Widget](https://f-droid.org/de/packages/com.plusonelabs.calendar/) as an alternative.)

## How to use Etar

Store your calendar on the phone only:

  - Use offline calendar to create a local calendar on your phone.

Sync your calendar to a server:

  - A cloud-synched calendar could be a google calendar, but you can also use

  any other public Caldav-server or even host your own (which would be the

  only way to keep full control over your data and still have ONE calendar

  usable from different devices.) To sync such a calendar to some server you

  need yet another app, e. g. DAVx5. That’s necessary because a Caldav client

  isn't included in Etar.

  The following [link](https://ownyourbits.com/2017/12/30/sync-nextcloud-tasks-calendars-and-contacts-on-your-android-device/) provides a tutorial how to use Nextcloud + DAVx5 + Etar.

### Technical explanation

On Android there are "Calendar providers". These can be calendars that are

synchronized with a cloud service or local calendars. Basically any app

could provide a calendar. Those "provided" calendars can be used by Etar.

You can even configure in Etar which ones are to be shown and when adding

an event to which calendar it should be added.

### Important permissions Etar requires

- READ_EXTERNAL_STORAGE & WRITE_EXTERNAL_STORAGE  

->import and export ics calendar files  

- READ_CONTACTS  

->allows search and location suggestions when adding guests to an event  

- READ_CALENDAR & WRITE_CALENDAR  

->read and create calendar events

## Contribute

### Translations in Google Play app description

You can update/add your own language [here](metadata). Also, all artwork files are available [here](metadata)

### Translations

Interested in helping to translate Etar? Contribute here: https://hosted.weblate.org/projects/etar-calendar/strings/

##### Google Play app description:

You can update/add your own language and all artwork files [here](metadata)

### Build instructions

Install and extract Android SDK command line tools.

```

tools/bin/sdkmanager platform-tools

export ANDROID_HOME=/path/to/android-sdk/

git submodule update --init --remote

git submodule update --init

gradle build

```

## License

Copyright (c) 2005-2013, The Android Open Source Project

Copyright (c) 2013, Dominik Schürmann

Copyright (c) 2015-, The Etar Project

Licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0

### How this was done

- see ``build.gradle`` and the modifications to ``AndroidManifest.xml``

- ``fix_strings_and_import.py`` was created to fix a build problem and rename imports of R.java

- get time zone data from http://www.iana.org/time-zones write ``backward`` and ``zone.tab`` to assets and to assets of https://github.com/dschuermann/standalone-calendar-timezonepicker

- comment out code in https://github.com/dschuermann/standalone-calendar-frameworks-ex

Google Play and the Google Play logo are trademarks of Google Inc.