From 750b36c28c5af7289b50d33aa99f3d631ec5b036 Mon Sep 17 00:00:00 2001 From: Mike Gabriel Date: Fri, 8 Dec 2017 14:45:35 +0100 Subject: Fix executable/project name (indicator-datetime -> ayatana-indicator-datetime) at various locations. --- README.md | 4 ++-- src/engine-eds.cpp | 8 ++++---- tests/CMakeLists.txt | 2 +- tests/manual | 30 +++++++++++++++--------------- tests/manual-test-snap.cpp | 2 +- tests/test-snap.cpp | 2 +- 6 files changed, 24 insertions(+), 24 deletions(-) diff --git a/README.md b/README.md index d5bb91e..785f3f9 100644 --- a/README.md +++ b/README.md @@ -121,8 +121,8 @@ LiveActions for production and MockActions for testing). Exporter exports the Actions and Menus onto the DBus, and also emits a - signal if/when the busname is lost so indicator-datetime-service knows - when to exit. + signal if/when the busname is lost so + ayatana-indicator-datetime-service knows when to exit. include/datetime/menu.h
include/datetime/actions.h
diff --git a/src/engine-eds.cpp b/src/engine-eds.cpp index 30aad1a..f1db6aa 100644 --- a/src/engine-eds.cpp +++ b/src/engine-eds.cpp @@ -215,7 +215,7 @@ private: if (error != nullptr) { if (!g_error_matches(error, G_IO_ERROR, G_IO_ERROR_CANCELLED)) - g_warning("indicator-datetime cannot show EDS appointments: %s", error->message); + g_warning("ayatana-indicator-datetime cannot show EDS appointments: %s", error->message); g_error_free(error); } @@ -294,7 +294,7 @@ private: if (error) { if (!g_error_matches(error, G_IO_ERROR, G_IO_ERROR_CANCELLED)) - g_warning("indicator-datetime cannot connect to EDS source: %s", error->message); + g_warning("ayatana-indicator-datetime cannot connect to EDS source: %s", error->message); g_error_free(error); } @@ -344,7 +344,7 @@ private: else if(error != nullptr) { if (!g_error_matches(error, G_IO_ERROR, G_IO_ERROR_CANCELLED)) - g_warning("indicator-datetime cannot get View to EDS client: %s", error->message); + g_warning("ayatana-indicator-datetime cannot get View to EDS client: %s", error->message); g_error_free(error); } @@ -1017,7 +1017,7 @@ private: if (!e_cal_client_modify_object_finish (E_CAL_CLIENT(gclient), res, &error)) { if (!g_error_matches(error, G_IO_ERROR, G_IO_ERROR_CANCELLED)) - g_warning("indicator-datetime cannot mark one-time alarm as disabled: %s", error->message); + g_warning("ayatana-indicator-datetime cannot mark one-time alarm as disabled: %s", error->message); g_error_free(error); } diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt index 8c58b06..717784e 100644 --- a/tests/CMakeLists.txt +++ b/tests/CMakeLists.txt @@ -18,7 +18,7 @@ set_directory_properties (PROPERTIES set_source_files_properties (gschemas.compiled GENERATED) # GSettings: -# compile the indicator-datetime schema into a gschemas.compiled file in this directory, +# compile the ayatana-indicator-datetime schema into a gschemas.compiled file in this directory, # and help the tests to find that file by setting -DSCHEMA_DIR set (SCHEMA_DIR ${CMAKE_CURRENT_BINARY_DIR}) add_definitions(-DSCHEMA_DIR="${SCHEMA_DIR}") diff --git a/tests/manual b/tests/manual index 95e5401..56906fb 100644 --- a/tests/manual +++ b/tests/manual @@ -1,19 +1,19 @@ -Test-case indicator-datetime/unity7-items-check +Test-case ayatana-indicator-datetime/unity7-items-check
Log in to a Unity 7 user session
Go to the panel and click on the DateTime indicator
Ensure there are items in the menu
-Test-case indicator-datetime/unity7-greeter-items-check +Test-case ayatana-indicator-datetime/unity7-greeter-items-check
Start a system and wait for the greeter or logout of the current user session
Go to the panel and click on the DateTime indicator
Ensure there are items in the menu
-Test-case indicator-datetime/unity8-items-check +Test-case ayatana-indicator-datetime/unity8-items-check
Login to a user session running Unity 8
Pull down the top panel until it sticks open
@@ -22,14 +22,14 @@ Test-case indicator-datetime/unity8-items-check
The menu is populated with items
-Test-case indicator-datetime/timestamp-wakeup +Test-case ayatana-indicator-datetime/timestamp-wakeup
Unplug the phone from any USB connection and put it to sleep
Reawaken the device.
The indicator should be showing the correct time.
-Test-case indicator-datetime/new-alarm-wakeup +Test-case ayatana-indicator-datetime/new-alarm-wakeup
Create and save an upcoming alarm in ubuntu-clock-app
Unplug the phone from any USB connection and put it to sleep
@@ -38,7 +38,7 @@ Test-case indicator-datetime/new-alarm-wakeup
If the device supports haptic feedback, confirm the alarm vibrates.
-Test-case indicator-datetime/disabled-alarms +Test-case ayatana-indicator-datetime/disabled-alarms
Create and save an upcoming alarm in ubuntu-clock-app
Confirm that the alarm icon appears next to the current time in unity's indicator display
@@ -48,7 +48,7 @@ Test-case indicator-datetime/disabled-alarms
When the alarm is enabled, the alarm icon should reappear.
-Test-case indicator-datetime/disable-one-time-alarms-after-notification +Test-case ayatana-indicator-datetime/disable-one-time-alarms-after-notification
Create and save an upcoming nonrepeating alarm in ubuntu-clock-app
Confirm that the alarm icon appears next to the current time in unity's indicator display
@@ -64,7 +64,7 @@ Test-case indicator-datetime/disable-one-time-alarms-after-notification
Confirm that the repeating alarm is not disabled after the notification is shown. NOTE: due to a refresh bug in clock-app you may need to refresh its alarms page (by swapping back to the main page, then the alarm page again, this is tracked in #1362341) in order to see the alarm change from enabled to disabled.
-Test-case indicator-datetime/calendar-event-notification +Test-case ayatana-indicator-datetime/calendar-event-notification
In the calendar app, create and save a new upcoming calendar event that will occur in the next few minutes.
The datetime indicator's event list should update itself to show this new event.
@@ -74,7 +74,7 @@ Test-case indicator-datetime/calendar-event-notification
The notification should disappear after a moment without requiring user intervention.
-Test-case indicator-datetime/alarm-timezone +Test-case ayatana-indicator-datetime/alarm-timezone
In ubuntu-system-settings, change your timezone to a zone you're not in
In ubuntu-clock-app, create and save an upcoming alarm
@@ -83,7 +83,7 @@ Test-case indicator-datetime/alarm-timezone
The indicator's menu should still show the alarm to click at the specified time
-Test-case indicator-datetime/snooze +Test-case ayatana-indicator-datetime/snooze
Create and save an upcoming alarm in ubuntu-clock-app
When the alarm goes off, press the 'Snooze' button
@@ -92,7 +92,7 @@ Test-case indicator-datetime/snooze
This time when the alarm is dismissed, it should not reappear.
-Test-case indicator-datetime/edited-alarm-wakeup +Test-case ayatana-indicator-datetime/edited-alarm-wakeup
Edit an alarm that's already passed. (see previous test)
Unplug the phone from any USB connection and put it to sleep
@@ -101,7 +101,7 @@ Test-case indicator-datetime/edited-alarm-wakeup
If the device supports haptic feedback, confirm the alarm vibrates.
-Test-case indicator-datetime/tell-snap-decision-to-dismiss +Test-case ayatana-indicator-datetime/tell-snap-decision-to-dismiss
Set an alarm and wait for it to arrive.
Alarm should go off at the specified time
@@ -110,7 +110,7 @@ Test-case indicator-datetime/tell-snap-decision-to-dismiss
Sound should stop at the same time, rather than playing til the end of the file.
-Test-case indicator-datetime/change-alarm-sound +Test-case ayatana-indicator-datetime/change-alarm-sound
Open the clock app
Swipe up from the bottom
@@ -124,7 +124,7 @@ Test-case indicator-datetime/change-alarm-sound
The newly-selected sound should play, rather than the previous sound.
-Test-case indicator-datetime/silent-mode +Test-case ayatana-indicator-datetime/silent-mode
Set an alarm and wait for it to arrive.
From the sound indicator, turn on silent mode.
@@ -137,7 +137,7 @@ Test-case indicator-datetime/silent-mode
The calendar event notification should play a sound.
-Test-case indicator-datetime/manual-time +Test-case ayatana-indicator-datetime/manual-time
In System Settings > Time & Date, manually change the time to an arbitrary time.
The indicator's timestamp should change right after the time manual time is set.
diff --git a/tests/manual-test-snap.cpp b/tests/manual-test-snap.cpp index 12d34f3..04ba2c3 100644 --- a/tests/manual-test-snap.cpp +++ b/tests/manual-test-snap.cpp @@ -93,7 +93,7 @@ int main(int argc, const char* argv[]) auto settings = std::make_shared(); settings->alarm_volume.set(volume); - auto notification_engine = std::make_shared("indicator-datetime-service"); + auto notification_engine = std::make_shared("ayatana-indicator-datetime-service"); Snap snap (notification_engine, settings); snap(a, a.alarms.front(), on_snooze, on_ok); g_main_loop_run(loop); diff --git a/tests/test-snap.cpp b/tests/test-snap.cpp index ae4c4e1..ef42583 100644 --- a/tests/test-snap.cpp +++ b/tests/test-snap.cpp @@ -42,7 +42,7 @@ using namespace ayatana::indicator::datetime; namespace { - static constexpr char const * APP_NAME {"indicator-datetime-service"}; + static constexpr char const * APP_NAME {"ayatana-indicator-datetime-service"}; } using namespace ayatana::indicator::datetime; -- cgit v1.2.3