[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 494: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 113: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 5312: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3925)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 5312: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3925)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 5312: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3925)
Tiny Tiny RSS • Android client: if only I could unread the sdk - Page 8
Page 8 of 18

Re: Official Android client

Posted: 04 Nov 2014, 21:12
by sancho1234
Hi Fox!

I found two bugs (or request?) in the Android version of ttrss app.

1.) The processing/refreshing animation line lost in material design from the top of the app while waiting for the loading articles from my server. The page is blank, and I don't know that is it waiting for interaction for start of refreshing, or no more articles in my feeds, or it has other problem.

2.) I always use the All articles menu. The app sorting of articles by feed groups, not by date. I would like to read articles by absolutely date sorting. How? :)

Thank you for your works!

Re: Official Android client

Posted: 04 Nov 2014, 21:25
by fox

Re: Official Android client

Posted: 04 Nov 2014, 21:25
by fox

Re: Official Android client

Posted: 04 Nov 2014, 21:31
by fox

Re: Official Android client

Posted: 04 Nov 2014, 21:40
by fox
btw I hope some sperg is currently raging because of different spacing between horizontal lines in the hamburger and sort icons.

(both icons are from google, of course)

Re: Official Android client

Posted: 04 Nov 2014, 22:28
by jah

Re: Official Android client

Posted: 05 Nov 2014, 02:55
by hubersan
(if this isn't the right area, please let me know)

Android client 1.62 - I dig the new interface, but it loses the functions that I've used the most.. (so I'm asking if there's something in the preferences that can maybe help me out) -

1: I have feeds organized by category, but occasionally I'll browse the individual feeds under a category (e.g. I may want to mark an entire feed read for some reason). I used to click on the 3 lines next to the category, which would give me the option to browse the feeds in that category. Is there a way to do that now?

2: In the article view, the most used button (by me) was the 'mark as unread' button - it's now gone! I know it's in the menu, but it's right next to the "mark above read" option, and I've been screwed more than once by hitting that by accident. Is there a way to get that back?

Thanks for humoring my questions.. it's a great product, so don't mistake this for gripes...

Re: Official Android client

Posted: 05 Nov 2014, 07:00
by tagno25
Posting just to say that I like most of the new layout. But I prefer the way the back button was used before (go up a level and exit on top level) and having a mark as unread button. If the reason you removed the mark as unread button was because you added the <-, then I think the share button would be better moved to the dot menu.

But that is just my personal opinion.

Re: Official Android client

Posted: 05 Nov 2014, 08:56
by fox

Re: Official Android client

Posted: 05 Nov 2014, 09:07
by fox

Change in android app back button behavoir

Posted: 05 Nov 2014, 17:23
by crimsoncor
I notice that in the latest android app version, the behavior of the back button has changed. It used to be when you were on a list of articles in a feed, the back button would take you back to the list of feeds and a second press back to the list of categories. Now a press of the back button from the list of articles causes TinyTinyRSS to quit. So as far as I can tell, the only way to access the list of feeds when you're in the article list is through the menu in the upper-left corner (if there is another way that I'm missing, then please ignore the rest of this).

The upper-left corner is the least ergonomic place to put a frequently accessed menu item, since it is basically impossible to reach on any decently-sized smart phone that is being used one-handed. Having the back button perform all the navigation in TinyTinyRSS was convenient because it meant you did not have to distort your hand position when switching between feeds. I was wondering if you would consider having the behavior of the back button be an option, so that those of us who prefer to have it take us back the list of feeds/categories can still have that behavior.

thank you.

Re: Change in android app back button behavoir

Posted: 05 Nov 2014, 17:36
by fox
pls read dedicated android app thread

Re: Official Android client

Posted: 05 Nov 2014, 18:05
by crimsoncor
Thanks for the pointer to this thread. Sorry for posting in the other forum; I missed this was here. Might be worth having a link to this thread from the Android app wiki page so that people like me who actually read the wiki end up in the right place.

I understand the problems in 2) and why the solution in 3) is the most consistent with the android ui.

Is it necessary to have the feed and category lists in a drawer? I'm not sure if this is different on a tablet, but on the phone version I do not see an advantage to the drawer. When I'm reading an article, I've got the back arrow in the upper-left, so I can't get to the drawer. When I'm back in the list of articles, I get the menu icon, so I can get to the drawer, but popping up the drawer blocks all the interaction with the article list, so it might as well not be there. It seems like having the list of feeds and categories be full-windowed lists like the list of articles would avoid any of this messiness with the drawer at all and lead to consistent back-button semantics. I seem to remember this being the case in an older version of the app. I assume it changed for some reason to do with google?


cheers

Re: Official Android client

Posted: 05 Nov 2014, 18:08
by fox
(sorry this topic was locked for a bit, I fucked up with phpbb buttons)

Re: Official Android client

Posted: 05 Nov 2014, 18:23
by fox
Anyway, to actually answer the above, I think that new drawer is an overall improvement. It looks better and it works better if you aren't going deep diving in the sublevels which really wasn't all that great previously either. If I regularly needed to go 5 levels down to read some feed, I'd place a shortcut for it or something, idk.

Stretched to the whole huge-ass modern android screen fullscreen feed list just looked dumb imo.

Also, the whole point about usability and stuff should probably be better directed to mountain view, as far as I could figure from their shit instructions that's how things are actually supposed to generally work. They don't do multilevel navigation but other than that...

Also you don't need to use the button just swipe from the left.