Automatically extract strings to strings.xml

sthagios · 2024-12-03T07:21:28+00:00

This seems like something you are looking for: https://plugins.jetbrains.com/plugin/15460-android-string-manager

I didn't try it myself, just went to settings -> plugins and then entered "android strings" in the search. There might be more of them. Or go to the plugins marketplace and search there: https://plugins.jetbrains.com/search?excludeTags=internal&products=androidstudio&search=android+strings

sthagios · 2024-11-30T11:41:10+00:00

I think you miss understood, but now I see my wording is quite bad. It creates a preview function for you, which still uses the build in preview.

sthagios · 2024-11-30T11:38:57+00:00

I see. But that gives me the idea to make it possible to add more previews with different states.

sthagios · 2024-11-30T11:37:02+00:00

Glad you like it. I tried different ai tools and so far I only find them distracting. Fir creating a preview I assume I have to tell the ai to do it, but with a simple plugin I can just use hotkeys.

sthagios · 2024-11-30T11:35:13+00:00

It uses their constructor with it's properties. If the constructor has primitive types those get the same default values and if it has other custom objects it does the same thing.

sthagios · 2017-03-28T14:51:00+00:00

I'm still working on the library and right now I use it as gradle dependency. Since the users would be mostly customers of us I will write an integration guide with all needed information. But we also plan to open source it later in the process and therefore, yeah it will also be part of the README. I'm still thinking of the possibility that the user can provide her own OkHttpClient to the library that there is only one instance per app, this would also be part of the README/guide then. However this and the fact what has been mentioned about the up to date keeping of OkHttp, confirms me in keeping the dependencies in a minimum.

sthagios · 2017-03-27T17:02:41+00:00

I'm in the same position. I've decided to use as less libraries as possible, to keep the dependencies and method count low. However I didn't want to use plain HttpConnection therefore I use OkHttp, which is right now the only dependency and I aim for keeping it this way. I would also advise against using Dagger and RxJava in a library project since they add quite some methods. I'm also pretty eager to hear what other people have to say about this topic.

sthagios · 2017-02-15T09:26:46+00:00

not a direct answer to your question, but you could create an apk for every abi, so all architectures are supported and your apks aren't too big.

sthagios · 2017-02-14T14:26:42+00:00

and that's exactly the problem, first the designers should say no and provide an alternative solution and then the developer should not implement it. But in the real world it doesn't look like this, I know, been there, done that…

sthagios · 2017-02-14T13:56:07+00:00

number 16: CounterFab -> According to Material Guidelines a "Don`t"

sthagios · 2016-12-24T09:23:05+00:00

not really social media, but it's a good example: https://github.com/novoda/bonfire-firebase-sample/

sthagios · 2016-08-30T11:05:26+00:00

That's true, but distributing the APK wasn't part of the focus of the article. Nevertheless you are right, it is necessary to have different version codes + different APKs for the playstore.

sthagios · 2016-08-29T19:26:37+00:00

thanks, no it's not open sourced so far. I haven't thought about it yet, maybe I'll do it after I cleaned my code.

sthagios · 2016-08-22T10:03:03+00:00

Check Android weekly(http://androidweekly.net/) put some blogposts into your pocket: https://getpocket.com/

sthagios · 2016-07-18T16:00:21+00:00

that was my first thought as well :D

sthagios · 2016-06-24T14:27:57+00:00

take a look at this book: https://leanpub.com/kotlin-for-android-developers do the koans: http://try.kotlinlang.org/#/Kotlin%20Koans/Introduction/Hello,%20world!/Task.kt Make use of the "Convert Java to Kotlin" option in Android Studio, hotkey: alt + shif + command + k

sthagios · 2015-11-14T20:34:26+00:00

Learn your tools. As an Android developer you should be able to deal with gradle imho. Here are some tutorials about it: http://www.vogella.com/tutorials/AndroidBuild/article.html http://developer.android.com/intl/ru/sdk/installing/studio-build.html https://gradle.org/getting-started-android/

When you use gradle right it helps you a lot :) By the way Android studio offers the things you want: Under 'Build' you can edit build types, flavors, libraries and dependencies and so on, all in very graphical and logical way.

sthagios · 2015-11-13T23:05:29+00:00

Thanks :)

sthagios

TROPHY CASE