|
Geekner posted:You could horizontally scroll in 1.6 since we used a ListView then, but there were a lot of restrictions so we had to move to a WebView. Either that or allow horizontal scroll in the webview, and allow individual post elements to break the horizontal width. We'd be scrolling the whole page, but it would work. Unless you managed to make standard width posts recentre on the page when it's h-scrolled using Javscript (although I think CSS might allow this too). That might work too.
|
| # ? Nov 13, 2011 20:53 |
|
|
| # ? May 23, 2013 14:24 |
|
Rohaq posted:It is possible to do iPhone/Android compatible horizontally scrolling elements in Javascript, but proper support for the CSS property would be better. I'm no webman, CSS is not my friend. V I would like to see an option to scale images if above a certain size. Or at least proper timg support, sometimes I come across a really large timg and several posts quoting it and it just kills my tablet. But I don't really know where to start on that. However, I can think of something I'd like to do right now, bring over the 'convert images to links in previously read posts' function from SALR. And finish thread-tags, heh.
|
| # ? Nov 13, 2011 21:14 |
|
Geekner posted:However, I can think of something I'd like to do right now, bring over the 'convert images to links in previously read posts' function from SALR. And finish thread-tags, heh. This is genius, do this. I must get salr...
|
| # ? Nov 13, 2011 22:35 |
|
Queston, is it possible to make SA smilies ignore the "load images" setting? I like the ability to prevent gigantic pictures from loading, but I miss my smilies
|
| # ? Nov 14, 2011 18:21 |
|
Lprsti99 posted:Queston, is it possible to make SA smilies ignore the "load images" setting? I like the ability to prevent gigantic pictures from loading, but I miss my smilies I've asked this before but FERG hasn't commented!
|
| # ? Nov 14, 2011 18:42 |
|
nimper posted:I've asked this before but I could probably do this while implementing 'hide image on previously read posts'. Image linking is one of the few things still being done in JS, so I'd like to see if it's faster to do it during the parsing stage. I'd also like to make clicking a thumbnailed image that links to the full image not have that link overridden like it is currently. e: Did some of this, adding some images to test with: Linked, large TIMG: ![]() Regular TIMG: ![]() Regular IMG: ![]() e2: I should test video tags: http://www.youtube.com/watch?v=J1ZR_M0Y17k http://vimeo.com/23956527 Salvador Dalvik fucked around with this message at Nov 15, 2011 around 04:19 |
| # ? Nov 14, 2011 18:58 |
|
Lprsti99 posted:Queston, is it possible to make SA smilies ignore the "load images" setting? I like the ability to prevent gigantic pictures from loading, but I miss my smilies Wish granted! Also, other stuff: -Added option to convert images to links in previously read posts. (Default: off) -Reworked image sizing/linking to automatically resize images to fit screen, but still offer the ability to click them to view them in a browser. However, if that image is already inside a link (Ex: thumbnailed images), it will keep the outer link instead. Honestly, I don't like the old method of allowing images to stretch beyond the screen. If the image was large enough that shrinking it made it look bad, it was probably too large to view on that screen. At least clicking it to view in a zoomable/panable browser is a good compromise.
|
| # ? Nov 15, 2011 05:06 |
|
Just getting to read the leftmost panes of that comic has left me scared and confused.
|
| # ? Nov 15, 2011 05:24 |
|
2 things I've noticed recently, pressing back to exit the app cycles me through a million pages before I leave the app, and if I don't back out of the app, it always starts at the first page of the last thread I was reading. Always.
|
| # ? Nov 15, 2011 07:13 |
|
Over the weekend, I had a couple of instances of returning to the app (usually after the phone auto-locked) to have it try to load page 0/x of whatever thread I'd been reading.
|
| # ? Nov 15, 2011 07:26 |
|
Cakefool posted:2 things I've noticed recently, pressing back to exit the app cycles me through a million pages before I leave the app, and if I don't back out of the app, it always starts at the first page of the last thread I was reading. Always.
|
| # ? Nov 15, 2011 12:23 |
|
Geekner posted:Wish granted! You rock.
|
| # ? Nov 15, 2011 13:21 |
|
Vykk.Draygo posted:Because you aren't hitting back when you're done redding a thread, you're pushing the forums list button / UCP button and creating a million pages you have to back out of. Hmm, sometimes yes, but not often enough to cause this? I'll try to be more consistent, see if that fixes it.
|
| # ? Nov 15, 2011 13:30 |
|
Step away for a few days because, you know, Skyrim, and I've got 3 new pull requests. I smell a release in the near future.
|
| # ? Nov 15, 2011 14:24 |
|
Ferg posted:Step away for a few days because, you know, Skyrim, and I've got 3 new pull requests. I smell a release in the near future.
|
| # ? Nov 15, 2011 14:57 |
|
LastInLine posted:Can you fix the oddball characters not working before you do? The only one I know for sure doesn't work is the > symbol, but I'm sure others don't as well. Alright, I'll look at it. Probably the overzealous stringescape library.
|
| # ? Nov 15, 2011 17:16 |
|
Geekner posted:Alright, I'll look at it. Probably the overzealous stringescape library. I are smart.
|
| # ? Nov 15, 2011 18:02 |
|
What's the easiest way to get this on the Kindle Fire?
|
| # ? Nov 15, 2011 19:57 |
|
jfreder posted:What's the easiest way to get this on the Kindle Fire? Get it on the Market on another Android device, and then extract the APK and copy it over? Assuming the Fire allows you to install apps from "unknown sources".
|
| # ? Nov 15, 2011 20:01 |
|
LastInLine posted:Can you fix the oddball characters not working before you do? The only one I know for sure doesn't work is the > symbol, but I'm sure others don't as well. Test quote. As for the fire, I don't see any problems with ferg throwing it up on the amazon market. I think we fixed any potential compatibility issues when we fixed Touchpad support. E: looks like that worked. > <¥¢€£~^° Salvador Dalvik fucked around with this message at Nov 15, 2011 around 20:17 |
| # ? Nov 15, 2011 20:09 |
|
Geekner posted:Test quote.
|
| # ? Nov 15, 2011 20:23 |
|
If possible, I'd like to see the option "Display threads with new posts first" from SLAR added into the app. Really, a lot of the SLAR options are awesome. Ferg, you make awesome things. Thanks for these! deong fucked around with this message at Nov 15, 2011 around 22:06 |
| # ? Nov 15, 2011 22:03 |
|
deong posted:If possible, I'd like to see the option "Display threads with new posts first" from SLAR added into the app.
|
| # ? Nov 15, 2011 23:18 |
|
Cakefool posted:Not a bug but slightly odd behavior. Previously when I homed out & came back much later- long enough for awful to be kicked out of memory- it'd go straight to ucp, now it always comes back to the start of whichever thread I was reading. Does anyone else get this? So, uh, this is fixed now. It was actually one of the simplest fixes I could have done for it. I wracked my brain with more complicated stuff when it was sitting right in front of me. Also, since it's related: How does everyone feel about clearing the back-stack whenever you go to the UserCP from the menu button? Right now, there are two main ways people browse threads: Hit thread -> read -> hit back. This clears that entry from the back stack and you can use back to exit the app completely. Hit thread -> menu -> usercp -> thread -> repeat. If you hit back a few times, it will go back to all of the previous threads you were reading. This might also lead to a large stack of activities in the background (there's no performance penalty, just more stuff to hit back through). However, it can be set to clear out that history when you hit UserCP from the menu button. Then you'll never get a large history, and we won't need to implement a 'Quit' button. Thoughts?
|
| # ? Nov 16, 2011 04:18 |
|
Geekner posted:So, uh, this is fixed now. It was actually one of the simplest fixes I could have done for it. I wracked my brain with more complicated stuff when it was sitting right in front of me. I'm very much in favor of this.
|
| # ? Nov 16, 2011 04:23 |
|
Geekner posted:So, uh, this is fixed now. It was actually one of the simplest fixes I could have done for it. I wracked my brain with more complicated stuff when it was sitting right in front of me.
|
| # ? Nov 16, 2011 04:47 |
|
I do the User CP -> thread -> back method, and honestly never thought to do it the other way at all... no wonder people are having issues. Seems pretty simple, and I'd go so far as to say that the basic Forums view, as well as the CP, should clear your log.
|
| # ? Nov 16, 2011 05:11 |
|
I used to hit CP from a thread from the menu and had that problem all the time. I just switched over to hitting back. If you're hitting CP from that menu you might want to switch anyway, since it's one less thing to press (just back instead of menu and then CP).
|
| # ? Nov 16, 2011 05:42 |
|
I'm guessing ozmodiar quoted that in the app? & becoming :amp; seems to be making a comeback.
|
| # ? Nov 16, 2011 07:47 |
|
Cakefool posted:I'm guessing ozmodiar quoted that in the app? It's already fixed. (not running dev version right now) Lots of minor fixes waiting. I'll commit the clear history thing in the morning and post a full changelog.E. Yea, works on dev version. Forgot that my tablet was a few commits behind. Salvador Dalvik fucked around with this message at Nov 16, 2011 around 08:26 |
| # ? Nov 16, 2011 08:08 |
|
Great idea for dumping the back stack. While I've never used the app in the broken memory hogging way, it seems like a very useful proactive measure. Does the Google Analytics data provide that kind of usage detail?
|
| # ? Nov 16, 2011 13:52 |
|
Nth Doctor posted:Great idea for dumping the back stack. While I've never used the app in the broken memory hogging way, it seems like a very useful proactive measure. Well, that method never hogged memory. After leaving an activity the OS usually kills it afterwards (causing the 0/1 page thing that's also fixed now). All that really hangs around is the leftover intent, which is pretty small. Anyways, the history-clearing stuff is up there. It only applies to usercp and forum index, so you can click a thread-link while browsing and still be able to go back. That's all the changes I plan on making for this release, so hopefully Ferg can release a test version. Here's the current changelist since current market release: -Spoiler color matches text color. (Sereri) -Disable spoilers setting. (Sereri) -Video tags now show a preview image. (Sereri) -That CPU bug is gone, I swear. -'Show Emote' setting, now separate from the 'Enable Images' setting. Emotes should cache well, so they shouldn't use much data transfer. -'Hide Previously Viewed Images' setting. Converts images to links on previously read posts. -Images scale to fit screen, but can be clicked to view in separate browser. Preserves existing link if one exists. -Loading status icon reflects image-loading as well. New icon for Image stage, can be clicked to cancel image load. -Some special characters don't won't escape this time. (Run, & amp;, RUN!) -Resuming after the program is killed won't load page 1 of whatever thread you are on. (It won't save scroll position, sorry.) -Hitting Menu->UserCP will clear back button history.
|
| # ? Nov 16, 2011 18:11 |
|
Currently, I click an image and it loads in my web browser. When I close the browser, I get sent back to the mythical page 0 of the thread. Has anyone else noticed that behavior?
|
| # ? Nov 16, 2011 19:07 |
|
Nth Doctor posted:Currently, I click an image and it loads in my web browser. When I close the browser, I get sent back to the mythical page 0 of the thread. Has anyone else noticed that behavior? Already fixed, second to last item on the changelist above.
|
| # ? Nov 16, 2011 19:13 |
|
^^^^^^^ Your phone runs out of or low on memory and makes some room on awful's expense. Though I never understood why the app kept the thread but not the page.
|
| # ? Nov 16, 2011 19:15 |
|
Is there a way I can get the apk file? I'd like to load this on my Kindle Fire but I have no way of getting the app from the Android Market.
|
| # ? Nov 16, 2011 22:03 |
|
Radnor posted:Is there a way I can get the apk file? I'd like to load this on my Kindle Fire but I have no way of getting the app from the Android Market. I'd also love this. My Kindle Fire just isn't complete without it!
|
| # ? Nov 16, 2011 23:45 |
|
Geekner posted:Well, that method never hogged memory. After leaving an activity the OS usually kills it afterwards (causing the 0/1 page thing that's also fixed now). All that really hangs around is the leftover intent, which is pretty small. Very busy week, I've got these pull requests sitting in my inbox waiting to be pulled. I'll get to them as soon as I'm able, which is hopefully very soon.
|
| # ? Nov 17, 2011 01:30 |
|
Geekner posted:Well, that method never hogged memory. After leaving an activity the OS usually kills it afterwards (causing the 0/1 page thing that's also fixed now). All that really hangs around is the leftover intent, which is pretty small.
|
| # ? Nov 17, 2011 04:56 |
|
|
| # ? May 23, 2013 14:24 |
|
Geekner posted:Already fixed, second to last item on the changelist above. Sometimes I hate being illiterate.
|
| # ? Nov 17, 2011 15:54 |








FERG











& becoming :amp; seems to be making a comeback.
(not running dev version right now) Lots of minor fixes waiting. I'll commit the clear history thing in the morning and post a full changelog.




