MultiLanguages | Android 多语种适配框架，兼容高版本，适配第三方库语种 | Internationalization library

by getActivity Java Version: 8.0 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | MultiLanguages Summary

MultiLanguages is a Java library typically used in Utilities, Internationalization applications. MultiLanguages has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

Android 多语种适配框架，兼容高版本，适配第三方库语种

Support

Quality

Security

License

Reuse

Support

MultiLanguages has a low active ecosystem.

It has 704 star(s) with 99 fork(s). There are 12 watchers for this library.

It had no major release in the last 12 months.

There are 1 open issues and 30 have been closed. On average issues are closed in 15 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of MultiLanguages is 8.0

Quality

MultiLanguages has 0 bugs and 9 code smells.

Security

MultiLanguages has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

MultiLanguages code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

MultiLanguages is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

MultiLanguages releases are available to install and integrate.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

MultiLanguages saves you 162 person hours of effort in developing the same functionality from scratch.

It has 402 lines of code, 28 functions and 19 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed MultiLanguages and discovered the below as its top functions. This is intended to give you an instant insight into MultiLanguages implemented functionality, and help decide if they suit your requirements.

Create the web view
Load language resources
Gets the system language
Determines if the system language is defined
Called when configuration changed
Get on language listener
Gets the application
Update configuration changed
On create
Injects the activity languages
Initialize library
Set default locale
React changed
Clear language
Change the language of the application
Clear the current language
Called when Activity is created
Gets the current locale
Compare two locale
Called when activity is resumed
Set shared preferences name
Launch the activity
Resume the web view
Called when the view is paused
Destroy the web view
Attach the base context

Get all kandi verified functions for this library.

MultiLanguages Key Features

No Key Features are available at this moment for MultiLanguages.

MultiLanguages Examples and Code Snippets

No Code Snippets are available at this moment for MultiLanguages.

Community Discussions

Trending Discussions on MultiLanguages

Having one template app and making multiple different apps from it

QUESTION

Having one template app and making multiple different apps from it

Asked 2020-Apr-07 at 14:55

I am trying to figure out what would be a good way of setting up application architecture and how to setup Xcode project itself, in the case where I have one base application, and I need to make multiple applications of it where the all apps will have those same base functionalities but will differ in a way that:

Assets may be different
Some features can be added ( new screens that uses new endpoints that are not defined in base app)
Localization can be differ (eg. one app can only be translated to english, and other can support multilanguages)

and probably some more, but you get an idea of what kind of an app (kinda template app) I am referring to.

What would be a preferred way to implement something like this? I guess targets and making a framework for a shared code is one way to go? Or there is something else that would be suitable too?

...

ANSWER

Answered 2020-Apr-07 at 14:55

Target is a good start. Thanks to target memberships, you can "share" storyboards, source files and whatever you want between several targets. Then within each specific target, you add your assets and specific functionalities.

Frameworks can be also a good way to share functionalities between apps. But you can start and try simply with targets, and then later factorize code within frameworks.

The way I would do it could be this way :

Create your project with a single target, let's call it "Blank App"
Develop functionalities and prepare generic assets for this app
When you want to add a new App, duplicate the "Blank App" target, remove membership of default assets, add new ones, add also specific source and resource files, and that's it.

After a few targets, you can spot what can be factorized within frameworks. Add a new framework target, migrate your sources in it, make all apps use this framework, and you'll have a nice system.

Source https://stackoverflow.com/questions/61082160

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install MultiLanguages

You can download it from GitHub.
You can use MultiLanguages like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the MultiLanguages component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: