* Add EmojiCompat
* EmojiCompat doesn' replace all emojis anymore
* This app should be now capable of loading a EmojiCompat-font located in a file somewhere inside the device's storage
* Should now replace all emojis
* Add EmojiCompat support to EditTextTyped
* Provide EmojiCompat fonts
* The app won't crash anymore when no emoji font is available.
Emoji font should now be located at [Private external app directory]/files/EmojiCompat.ttf
* Removed BundledEmojiCompat dependency
Since this EmojiCompat-implementation does not rely on BundledEmojiCompat, there's no reason to have it enabled.
* Update EditTextTyped.kt
Since connection isn't assigned to (I tried doing so), it can be declared final/val again.
* Update README.md
* Add some non-working emoji preferences
* Add a short font list for testing
* Finished implementation
* Add Twemoji to font list
* Update documentation, more comments
* Delete AssetEmojiCompat which is obsolete now
* Update the font list
* Update the font list
* Fix font list & add Exception handling for malformed JSON files (hopefully)
* More fixes. It should work now...
* Removed AssetEmojiCompat (again)
* Add most of the changes
* Improved the EmojiCompat dialog's style
* The font list is now based on a static layout without external files
* Re-add the real font URL for Twemoji
* Emoji-font captions are now translatable
* Removed one unused String (loading)
* Removed emoji fonts from this repo
* Applied changes from the PR change requests
* The correct emoji font will be selected after cancelling a change
* Add details on the EmojiCompat fonts available (not shown yet)
* Add licensing information on Twemoji and Blobmoji
* Reworked some strings
* Moved FileEmojiCompat to its own library
* Update FileEmojiCompat to the latest version (1.0.3)
* EmojiCompat bug should be fixed
* Better handling of failed downloads
* Removed one TODO
Signed-off-by: Constantin A <10349490+C1710@users.noreply.github.com>
* Update emoji attribution strings
Signed-off-by: Constantin A <10349490+C1710@users.noreply.github.com>
* Fixed some misspelled strings
Signed-off-by: Constantin A <10349490+C1710@users.noreply.github.com>
* Add tests for search functionality in SFragment
* Parameterize url matching tests
* Clean up / compartmentalize search tests
* Make SFragmentTest filesystem location match package name
* Query instance for toot character limit
Fixes#393
* Move maximumTootCharacters to instance field
* Add caching for maximum toot characters, expanding on the emoji list storage
* Update formatting per review feedback
* Fix compose activity tests
* Rename mastodon api point for nicer interaction with kotlin
* Default emoji list to empty list instead of null, to appease json converters in failure cases
* Add test coverage for custom toot character limit setting
* Fix compiler warnings
* View links to statuses inside Tusky
* Only attempt to open links that look like mastodon statuses
* Add support for pleroma statuses
* Move "smells like mastodon" url check to click handler
* Add bottom sheet to notify users of post query status
* Improve architecture for managing search status
* Push everything into SFragment
* Add external lookup for non-locally-resolved account links
* Clean up copypasta from LinkHelper.setClickableText
* Apply PR feedback
* Migrate bottom sheet wrappers to CoordinatorLayout
* inject MastodonApi into LoginActivity
* inject AccountManager into MainActivity
* inject AccountManager into SplashActivity, convert to Kotlin
* inject AccountManager into AccountActivity
* inject AccountManager into LoginActivity
* inject AccountManager into NotificationsFragment and NotificationClearBroadcastReceiver, fix MainActivity
* ooops
* use same OkHttpClient for Retrofit & Picasso
* fix ordering of okhttp interceptors
* remove dependencies on TuskyApplication
* bugfix
* Query instance for toot character limit
Fixes#393
* Move maximumTootCharacters to instance field
* Add caching for maximum toot characters, expanding on the emoji list storage
* Update formatting per review feedback
* Fix compose activity tests
* Rename mastodon api point for nicer interaction with kotlin
* Default emoji list to empty list instead of null, to appease json converters in failure cases
* Use empty list helper
* Fix database migration
* do not add media urls to status text
* add scrolling to content
* add arrow icon and animation to replying-to toggle
* remove unnecessary compose_button_colors.xml
* improve toot button
* improve bottom bar, add bottom sheet for compose options, dedicated cw button
* fix crash on Android < API 21
* move media picking from dialog to bottom sheet
* add small style tootbutton
* fix colors/button background for light theme
* add icons to media chose bottom sheet
* improve hide media button, delete unused styles
* fix crash on dev build when taking photo
* consolidate drawables
* consolidate strings and ids, add tooltips to buttons
* allow media only toots
* change error message to show max size of upload correctly
* fix button color
* add emoji
* code cleanup
* Merge branch 'master' into compose_activity_refactoring
# Conflicts:
# app/src/main/java/com/keylesspalace/tusky/ComposeActivity.java
* fix hidden snackbar
* improve hint text color
* add SendTootService
* fix timeline refreshing
* toot saving and error handling for sendtootservice
* restructure some code
* convert EditTextTyped to Kotlin
* fixed pick media button disabled color
* force sensitive media when content warning is shown
* add db cache for emojis & fix tests
* reorder buttons to match mastodon web
* add possibility to cancel sending of toot
* correctly delete sent toots
* refresh SavedTootActivity after toot was sent
* remove unused resources
* correct params for toot saving in SendTootService
* consolidate strings
* bugfix
* remove unused resources
* fix notifications on old android for SendTootService
* fix crash
* Initial implementation of regex feed filtering
Mimics Mastodon web's functionality, but in a simpler form; a single
regular expression is shared across the home, local and federated feeds.
Strings are currently only provided in English and will need to be
translated.
* Fix buggy behaviour on filter regex update
* Validate regex filter input
Fixes buggy behaviour on inputting a regular expression feed filter by
testing the expression continuously as the user types, displaying an
error and disabling the 'OK' button of the dialog at any time it's not a
valid regular expression. Disables spelling suggestions in the input to
make the experience less frustrating and error prone.
Also fixes some generally buggy behaviour upon preference change,
specifically in cases where no Matcher was set prior to a new pattern
being set, which would cause the app to crash.
* Apply regex filter to spoiler text
* Get rid of empty catch block in regex filter code
* Make regex filter error string translatable
* Use the entire content warning text + button as the hitbox for the "Show more/less" toggle
* Move the content warning toggle button to its own line and give it a little more space
* Move content warning elements into parent layout, remove now-superfluous FlowLayout
* Use marginTop/Bottom instead of Vertical, which is only in sdk 26+
* Update minimum width for content warning toggle button
* correctly filter notifications on Api >= 26, other fixes and refactoring
* use correct areNotificationsEnabled method in MainActivity
* change notification led color
* basic implementation
* improve LoginActivity
* darken drawer background image
* add current avatar in ComposeActivity
* add account name to logout dialog
* multi account support for notifications
* multi account support for notifications
* bugfixes & cleanup
* fix bug where somethings notifications would open with the wrong user
* correctly set active account in SFragment
* small improvements
* Split theme definitions into day and night
* Add support for Night Mode in code
* Add theme chooser in preferences
* Fix translations
* Adjust IDs
* Adjust preferences for custom themes
* UI tweaks for custom theme support
* Added code for custom theme support 🍅
* Fixed resource display in Kotlin 🍅
* Restored styles
* Updated strings
* Fixed getIdentifier() to fit into setTheme()
* Removed redundant resources
* Reset default theme to "Dusky"
* Fixed night mode handler to maintain compatibility
* Refactor functions to use helper methods
* Added license block
* Added preview to theme selector
* Added color identifier getter helper method
* Fixed reference in AccountMediaFragment
* Cleanup
* Fixed navbar foreground not changing color
* Fix fallback theme switch(){}
* Enable location-based daylight trigger
* Cleanup
* Modified theming strategy to reduce clutter in preferences
* Updated translations for latest version
* Removed "Default" theme flavor from settings
* Updated Polish translations 🇵🇱
* Modified TwilightManager handling code to support Android M's UiModeManager features and moved it to its own function
* Updated Polish translations 🇵🇱
* Cleanup; Fixed hardcoded string
* Added missing escape in string
* Removed permission request dialog.
As we now use native UiModeManager APIs that don't need special permission for Android 6.0 and above, we no longer need to bother user with Android M+ specific location permission request dialog.
* Increased readability of ThemeUtil class
* Refactored ThemeUtils.setAppNightMode method
* Cleanup
This change allows the user to manually enter an unauthenticated proxy
configuration to be used for all API connections. This is mainly
intended for using Tusky with Tor (via Orbot or a local proxy).
* Refactor ComposeActivity intent. Fix bug with URLs
When user saved toot link was removed from the text field itself,
not only from the text to be saved.
* Show what you reply to
Closes#119
The problem was that Tusky kept sending requests for autocompletion
while writing toots even when the user wasn't typing a username
anymore. As it happened very often we would exceed the API request
limit and user wouldn't be able to send the toot.
This happened because Tokenizer is not used as expected. In fact,
during testing, findTokenEnd() and terminateToken() were never called.
I've tried setting a Validator but it wasn't used either. I'm not
sure what is the reason.
I am afraid it still may work incorrectly for the full nicknames
(ones with the instance name, like @name@isntance) because
the search may happen for the instance name but it's not as
critical.
