Should whole objects be passed around or only the thing we need from it?

TheKeeperOfPie · 2017-02-17T20:53:35+00:00

If you have an application singleton cache the data, then it would be basically instant when you load the next screen. Your loading state/View should have logic for a minimum delay before transitioning to/from a loading state so you don't get a flash.

Although it depends on what the screens are. If they're related enough, I'd probably just make them 2 Fragments which share the same Activity-scoped data presenter. That way they both read the same object and you don't have to pass a pointer using the Intent or arguments.

TheKeeperOfPie · 2017-02-17T20:32:53+00:00

You can shorten or eliminate the loading state by having caching, but generally, yes, every screen that loads data should have a loading state.

Intent/Bundles aren't meant to hold large data sets, only data pointers, and it's enforced with an error on newer SDK versions.

TheKeeperOfPie · 2017-02-17T17:26:05+00:00

Yeah. It should be com.microsoft.office.lync15 anyways.

TheKeeperOfPie · 2017-02-17T16:19:40+00:00

Funny. The AutoMod rule caught your code string with the Play Store link. Do you mind redacting that so I can approve your comment?

Also, that string is wrong anyways. The package name is not the entire link, just the com.... part.

TheKeeperOfPie · 2017-02-13T22:56:58+00:00

Hey there,

Your question breaks rule 3.

No linking to your own apps without source code

Please remove that link and let me know so I can approve your comment. Or add a GitHub link to your source code.

Thanks.

TheKeeperOfPie · 2017-02-13T15:24:05+00:00

Company: SeatGeek (App)

Job: Android Engineer

Location: New York, NY (we pay for relocation)

Allows Remote: No

Visa: No

URL: Apply here

SeatGeek is a live event ticketing startup in NYC that lets you find, buy, send, and sell tickets. We use contemporary tools like RxJava and Dagger 2 and have recently added features like Android Pay and Discovery (a revamp of our main screen).

For more information about us, check out our jobs page, and ChairNerd, our product dev blog.

If you have any questions about SeatGeek, the job, or NYC, feel free to send me a message (I'm part of the team).

TheKeeperOfPie · 2017-02-09T16:45:38+00:00

I mean, to be fair, SearchView does that have documented:

https://developer.android.com/reference/android/widget/SearchView.html#attr_android:imeOptions

TheKeeperOfPie · 2017-02-09T16:18:30+00:00

It's called the IME action and can be set on the EditText, I think.

TheKeeperOfPie · 2017-02-08T20:51:57+00:00

As a random guy on the internet, that sounds good to me. It's like if the FAB launched a brand new search screen, but instead you have search in the toolbar. Feels like it would work fine.

TheKeeperOfPie · 2017-02-07T20:43:10+00:00

Just from some quick Googling:

https://www.microsoft.com/typography/otspec/otff.htm

You might want to look up an open source font creator and see if you can look at the file generation code.

TheKeeperOfPie · 2017-02-07T20:27:50+00:00

I'm not sure you need an external tool. Android has enough built in that you could write the users touch events to a Path object or something, and then you could manually write the TTF file from those paths.

TheKeeperOfPie · 2017-02-07T17:26:04+00:00

To be fair, I found Java and Android much easier than the 10 minutes of web development I've done.

TheKeeperOfPie · 2017-02-07T17:23:36+00:00

The layout renderer uses the .class files rather than the .java, I assume. You only edit the .java, and it needs to go through a full rebuild to make the .class file, in case any other processors/plugins need to be run.

You could probably make some plugin that built only a single .java and copied the .class file into the right place to get around that, but it would break if you did anything besides vanilla java.

TheKeeperOfPie · 2017-02-07T17:22:15+00:00

Replace removes the current Fragment A. You're looking for .add()

TheKeeperOfPie · 2017-02-07T16:51:40+00:00

Impressive, you broke 2 rules at once.

Gotta link your source code or remove your Play Store link.

And take out the hiring line.

Then I can re-approve.

TheKeeperOfPie · 2017-02-06T21:05:59+00:00

MVC (model-view-controller) was the predecessor, which was really more of a cycle than having anything in between.

MVP came out of that, presenter replacing controller, but rather than swapping around the letters, just changing the last one made it easier to understand, I guess.

Got that from a quick glance at Wikipedia.

https://en.wikipedia.org/wiki/Model-view-controller https://en.wikipedia.org/wiki/Model-view-presenter

TheKeeperOfPie · 2017-02-06T18:24:15+00:00

There's https://developer.android.com/preview/support-712.html, but I think generally full changelogs aren't released until the build is made stable/released.

Otherwise we could get feature declarations that could be removed before release, like the screen tint night mode with 7.0 or whatever version that was.

TheKeeperOfPie · 2017-02-06T15:53:18+00:00

The header is just a different item type in the RecyclerView.

Make a data model which knows where each header is and what items go under it, and then use a RecyclerView.Adapter to adapt that model into the Views for the header and what goes underneath.

TheKeeperOfPie · 2017-02-06T15:30:21+00:00

Just make the entire thing a single RecyclerView with different items.

TheKeeperOfPie · 2017-02-03T20:47:55+00:00

That's like wake-up-from-coma, step-out-of-time-machine level of upgrade there.

But I don't think you'll get Gradle to use 32 GB of RAM. It just doesn't need that much. Adjusting your heap size to a large enough size, like 4 GB or something, is probably enough.

Recently saw someone share this article in case you want general gradle tweaks: https://medium.com/@kevalpatel2106/how-to-decrease-your-gradle-build-time-by-65-310b572b0c43#.4mwnjetti

Haven't read it all the way through though.

TheKeeperOfPie · 2017-02-03T19:16:32+00:00

I've tried 5 or 6 times now to use ConstraintLayout, but have ended up reverting each time due to needing a feature that CL wasn't really designed for.

I seem to do a lot of operations expecting parts of my View to be grouped into parent ViewGroups (a hierarchy), and since CL is flat, there's really no equivalent there.

It's good if you have a simple static layout that doesn't need to be manipulated heavily.

TheKeeperOfPie

MODERATOR OF

TROPHY CASE

daily reddit gold goal

Four-Year Club	Team Orangered
Verified Email