my typical workflow is to focus on a few specific categories then flip to fresh… each time i need to open menu > special > fresh. and to get back > menu > close special > pick one
i’d like to see fresh at the top level of the menu. maybe others don’t want that and rather starred or recently read
would you please consider letting users choose which of the special feeds live under the special branch and which are promoted to the top of the menu ?
nope, special category mirrors tt-rss proper, it’s exactly same virtual feeds. as a workaround (of sorts) you can make shortcuts for specific categories on the desktop.
yeah i tried that, i like the shortcuts. but for flipping between fresh & a category … one ends up closing and opening the app to switch. not any smoother then slogging through the menu.
in tt-rss proper, i’ve hacked it with CSS like #dijit__TreeNode_5 {display: none} but that only works in a browser
perhaps i should be asking for a little more flexibility on special feeds in tt-rss proper VS just in the app ?
this stuff is way too much of a special case to be considered for stock UI in my opinion.
there’s a way to add Special feeds via plugins (af_shared is one example which i think is bundled) so you could explore this angle. i’m not sure if API and android client support this, but they should.
switch to offline improvements: instead of an easily missable popup dialog a notification is shown tapping on which switches tt-rss into offline mode even if it was in background when syncing completed
if the app is in foreground snackbar is also shown which can be used to switch offline
I tried out the offline mode this morning.
I downloaded the minimum of 150 articles and read some in the train. It was a nice and fast experience.
After I arrived at work i switched to online mode and let it sync the changes.
In my webbrowser ttrss if could see that the articles were correctly marked as read, but the mark star wasn’t removed.
Is it not possible to mark/unmark articles while offline?
it’s currently half way there. setting starred or published is going to sync back but unstarring/unpublishing won’t.
there’s no way to know whether the articles were starred/published before, only the fact that the record was locally modified is tracked in offline database, this limitation avoids syncing hundreds of article ids every time you go online while possibly unmarking things that got set while device was offline.
it shouldn’t be that hard to add two more tracking fields for this i think.
First off thanks for making an offline mode. I recall back in the day your view was people should just get a data plan
Anyway I notice one small, low priority glitch.
After going offline if you press the android back button the left nav goes back to the pre offline state and shows that you are online. You then see all the articles, even the ones you have not downloaded. A restart of the app fixes this. I don’t know much about Android but this may be as easy to fix as purging history?
new beta build (1.259) is going to be up soon, the only change is hopefully reducing memory usage of loaded images, at least going by android studio profiler
PHONE_MODEL=XT1635-02
ANDROID_VERSION=8.0.0
BRAND=motorola
AVAILABLE_MEM_SIZE=8874569728
APP_VERSION_NAME=1.6
PRODUCT=addison
TOTAL_MEM_SIZE=25612496896 STACK_TRACE=java.lang.IllegalStateException: Apk needs to have both Schema.ApkTable.Cols.REPO_ADDRESS and Schema.ApkTable.Cols.NAME set in order to calculate URL [package: org.fox.ttrss, versionCode: 497, apkName: org.fox.ttrss-fdroid.apk, repoAddress: null, repoId: 7]
at org.fdroid.fdroid.data.Apk.checkRepoAddress(Apk.java:255)
at org.fdroid.fdroid.data.Apk.getCanonicalUrl(Apk.java:277)
at org.fdroid.fdroid.installer.InstallManagerService.queue(InstallManagerService.java:466)
at org.fdroid.fdroid.views.AppDetailsActivity.initiateInstall(AppDetailsActivity.java:397)
at org.fdroid.fdroid.views.AppDetailsActivity.installApk(AppDetailsActivity.java:379)
at org.fdroid.fdroid.views.AppDetailsActivity.installApk(AppDetailsActivity.java:332)
at org.fdroid.fdroid.views.AppDetailsRecyclerViewAdapter$3.onClick(AppDetailsRecyclerViewAdapter.java:1330)
at android.view.View.performClick(View.java:6259)
at android.view.View$PerformClick.run(View.java:24732)
at android.os.Handler.handleCallback(Handler.java:789)
at android.os.Handler.dispatchMessage(Handler.java:98)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6592)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:769)
try installing the APK manually, if it installs and works properly, it’s probably a f-droid client problem that should be reported to f-droid developers. if it doesn’t, i’ll take a look at it.
i have no idea what that is and honestly don’t care. i’m only using f-droid as a backup delivery mechanism, if they suddenly started requiring custom-built APKs i’ll just drop the repo and publish APK files directly.