|
pokeyman posted:This is a bit humbling to admit, but if anyone's curious, this happens because I can't figure out exactly what string encoding the Forums use. It seems like everything I try is wrong. Our current strategy is to try like four different ones until something works. The site's encoding is definitely annoying, but like lucky says, it's "windows-1252". That's the only encoding that exactly matches up on weird characters like "–" (en-dash). Beyond that you just need to support HTML-escaped UTF8, which isn't too bad since webkit does it for ya. Character encoding was a total pain in awful.apk, I feel your pain.
|
#
¿
Oct 23, 2012 22:28
|
|
|
|
| # ¿ May 2, 2024 04:55 |
|
|
pokeyman posted:Followup question: what string encoding should we use for replies? What we end up doing is a bit of a hack, but it seems to work pretty well. We unescape the HTML encoded characters into native java strings (which fully support UTF-8 internally). That allows the user to see quoted text properly. The website reply window shows the escaped characters, (try replying to this post on your desktop). The app, however, shows the actual characters. Then when they go to post, it'll convert anything outside the the ASCII range back into escaped characters. We use the Apache common-lang library and a regex to convert the characters. The common-lang handles the edge-case HTML excaping stuff (like > = & gt;, < - & lt;, ect), and the regex just replaces any characters with a codepoint in the UTF range with the HTML-escaped equivalent. The text you send back should be windows-1252 compliant, since anything outside the first 127 characters will end up HTML escaped.
|
|
#
¿
Oct 24, 2012 01:22
|
|
|
I'm probably going to steal that option for the android app. It makes total sense to disable the scroll-jump if you are only showing new posts. Handling the initial scroll position is a total pain in the rear end, I don't have a proper way to avoid the scroll-back you get when images pop in. It's really weird that mobile webkit has this issue since Chrome's webkit fixed it a long time ago. Maybe the forums use some hack I'm not aware of.
|
|
#
¿
Oct 27, 2012 22:07
|
|
|
pokeyman posted:gently caress me. Guess what was in my spam folder. I'm sorry I didn't respond, and thanks for following up. I don't like the permanent sidebar in landscape either, it's too easy to accidentally hit another thread while reading. One way to handle the consoldated threads thing is the sort-by-unread option that SALR and the Android app has, where it sorts threads with zero new replies to the bottom of the list but otherwise leaves the order alone. That way you get all the threads you care about at the top and it still preserves the relative order. It also means you can just start at the top, click a thread to see the new posts, then that thread will drop down in the list and you won't have to scroll.
|
|
#
¿
Nov 5, 2012 17:55
|
|
|
The Dave posted:It's tough because some people have a wall of text with their avatar that could make the template look ridiculous if they post a short message. The ... is the context hint that tapping the user bar will reveal the post menu + avatar text. For the newer tablet ui you tap the avatar to reveal the text. Showing the text depending on length is kinda weird, dunno if it would work that well.
|
|
#
¿
Nov 6, 2012 18:03
|
|
|
Jedi Knight Luigi posted:Put me in the "in-app browser > safari" camp as well. In-app browser is definitely useful on iPhone, I don't really care either way on iPad due to the three-finger swipe.
|
|
#
¿
Nov 11, 2012 20:13
|
|
|
pokeyman posted:Not our lucky day apparently, we're stuck in the slow queue. Sorry everyone. I think the review team shut down for a week during xmas, they sent an email out about it a while ago. You're probably stuck at the end of a really long queue. I wish we got some kind of advanced notice for this kind of change.
|
|
#
¿
Jan 2, 2013 20:52
|
|
|
pokeyman posted:It's possible I did a bad job advocating for an expedited review. Not much else to do now but wait. Don't blame yourself; given how lovely the forum layout is, the code required to parse it almost has to be poo poo. As long as we get a stable API this won't be an issue again. This app is crazy high-quality. Hell, most mobile dev companies would charge serious cash to make something this nice. Be proud! I use this way more than the android app.
|
|
#
¿
Jan 8, 2013 00:22
|
|
|
obi_ant posted:I immediately pulled my dick out and started slapping it on my cellphone. It must be conveniently sized to make that post without any typos.
|
|
#
¿
Jan 8, 2013 23:59
|
|
|
Chuck Bartowski posted:What?! There's probably a delay before all phones will see it. Android apps don't show up for 30 minutes to 6 hours.
|
|
#
¿
Jan 9, 2013 00:02
|
|
|
Tab8715 posted:I don't understand how you guys are getting this to update - when I search for the app I see the application but nothing else. When I look in the App Store that last time it was updated was back in September and there's no update option. Do you have an older device with iOS 4? The newer version requires iOS 5.
|
|
#
¿
Jan 12, 2013 04:56
|
|
|
Liar Lyre posted:Hey there is a new "It's Time To Rumble" thread tag. Thought I'd let you guys know before another update is submitted. They can add new icons between updates now, it's a really clever workaround to the app store process. It's all hosted on their GitHub account and the app checks to see if there are new icons to use.
|
|
#
¿
Jan 24, 2013 04:50
|
|
|
Does the iOS image view only show the first frame of the GIF like it does in Android? The images themselves are actually pretty small, around 3-10kb each. Some kind of grid view would work pretty well. It would be especially nice if you have a filter text input so you could start typing the emote and find the one you want.
|
|
#
¿
Jun 8, 2013 04:24
|
|
|
goku chewbacca posted:I'd love to have access to smilies and VBulletin script. Still, I can see Awful app slowing to a crawl no matter how you choose to display all the smilies. That's webkit slowing down due to the animation, if those gifs are shown as static images outside webkit they don't have any performance hit. GIF threads on the other hand; good luck. Ain't no fix for that. I put a lot of blood and sweat into fixing that on awful.apk, and the current workaround isn't working out like I hoped.
|
|
#
¿
Jun 8, 2013 08:44
|
|
|
kloa posted:Does anyone still have the frog icons, or can get the ones from the android app? Why, exactly? I'm not a huge fan of it. It's just annoying that we can't use the standard grenade.
|
|
#
¿
Sep 1, 2013 07:36
|
|
|
pokeyman posted:
Is this just a coredata thing? It shouldn't be hard to make the forum/thread ID unique in a standard db.
|
|
#
¿
Jun 6, 2014 00:29
|
|
|
|
| # ¿ May 2, 2024 04:55 |
|
|
DNK posted:While this is a niche case, I know I'd find it comforting if Awful checked an independent source to see if somethingawful.com is down (assuming your internet connection is working). Relying on an external site isn't a great idea, they tend to go down or make breaking changes. AFAIK There is actually code in the app to parse known error types, but the outage today used a weird generic template site. Hopefully this is just a weird case since it's the new forum coders first day, as long as they use the standard error messages it won't be an issue.
|
|
#
¿
Aug 13, 2014 22:43
|
|