The automated integration plugin for Android Studio and IntelliJ IDEA for Nativer SDK (multilingual runtime extension) is available on Github: https://github.com/Transround/NativerSDK/tree/master/tools/nativer-admin-plugin-android-studio
The SDK itself is a new app localization technology for Java Android apps that implements dynamic string resource management. It separates the translation from the development process and supports on-the-fly resource distribution, so no app redeployment is needed when adding more languages. The SDK is also available on Github: https://github.com/Transround/NativerSDK
It’s just 15 minutes of your time to let users learn and practice languages while translating and using your app.
We prepared a tool window for easier usage and to track how translation goes on.
gyuri bp said:
The automated integration plugin for Android Studio and IntelliJ IDEA for Nativer SDK (multilingual runtime extension) is available on Github: https://github.com/Transround/NativerSDK/tree/master/tools/nativer-admin-plugin-android-studio
The SDK itself is a new app localization technology for Java Android apps that implements dynamic string resource management. It separates the translation from the development process and supports on-the-fly resource distribution, so no app redeployment is needed when adding more languages. The SDK is also available on Github: https://github.com/Transround/NativerSDK
It’s just 15 minutes of your time to let users learn and practice languages while translating and using your app.
Click to expand...
Click to collapse
Related
Anyone had ever crosscompiled some application for android? What about compiler, method (static or shared linking, if you can do it...), performance?
There are a few compilers out there and multiple approaches.
If you are ok with static builds, you can use use *just any* compiler for the architecture, otherwise you might want to stick with the stuff that comes with the source. There is also the NDK approach for building native libraries to link to from your java application.
Yesterday I released the first public version of PhoneCore Framework which helps to build applications on Windows Phone 7. There is the short list of features:
Navigation engine which simplifies navigation between pages
Dependency injection container which helps you to create lously coupled application
Configuration subsystem which allows you to manage workflow without rebuilding of an application
Tracing engine which allows to do postmortem analysis or analyze workflow/performance
Bootstrapping engine with plugin architecture
Primitive types: Lazy, Tuple
You can find the project, installation package and details at codeplex.
posting link for op http://phonecore.codeplex.com/
so im coming from c++ and trying to learn to create apps. im interested in using android studio to create apps so now i need to learn java.
quick question about java, im assuming java is for application development , and javascript is for browser related apps? am i correct? close?
also were is the thread showing how to install android studio and all the programs required? i stumbled upon it earlier, but i cant remember where it was at.
You are correct, java is for application development , in your case for Android development, and javascript is for web development.
More specifically,
JavaScript:
Interpreted
Runs in the browser, works on mobile devices
Runs on the client side (NOT the server)
Sandboxed so you won't be able to do low level stuff
Cross platform
JAVA
Compiled
Runs on the client or on the server
To run in the browser it needs a plugin so won't work on mobile devices
You can do low level stuff
Cross platform
I won't get into personal preferences, but there are many other differences, most of which will come evident when you start making stuff. If you want to make cross platform mobile apps you might want to look into Apache Crodova that uses HTML and JavaScript but can interface with device hardware too.
I have no idea if the project is feasible, and ideas/suggestions are welcome!
Project Idea -
What I want to do is translate all in-app text from one predefined language to another at runtime.
Say for example an app is in German (Not necessarily just the strings from *.xml, even text generated at runtime).
A user predefines the package name, and the required language conversion (say German to English).
Then whenever the user uses the required app, all the string, ANYWHERE in the app, are replaced by their translated equivalents.
Something similar to the way google translate works in chrome (minus the auto-detect page language part)
Project Implementation Proposal -
[*]Get all text drawn on the screen by hooking
TextView.class, "setText"
TextView.class, "setHint"
"android.view.GLES20Canvas", "drawText", etc.
[*] Use an online translation service (preferably Microsoft Translator as its free) to translate all the strings.
Note - Cache these translations offline since they will likely be needed often.
[*] Use beforeHookedMethod to replace any such String methodHookParam
Note - I understand that using any such online translation service will result in significant delay.
but if the delay is of an acceptable level, I would consider this project a life-saver. Perhaps caching the translations should suffice?
Any ideas, suggestions, criticism welcome!
I am new in developing for Xposed, but not new to development in general.
I have finished the module, and uploaded it here - http://forum.xda-developers.com/xposed/modules/xposed-alltrans-completely-translate-t3539878/page1
Translate any app, from any language to another.
Hey all,
I'm about to start developing an open source project for managing android devices from a Linux machine.
Technology stack is going to be;
Symfony (5.1 / PHP 7.4)
VueJs 2.* (ECMAScript 6 / TypeScript/ Buefy)
I'm still setting up the architecture for the backend and yet to begin on the frontend. For the frontend I've got a prebuily VueJs codebase I can use for the frontend architecture
Preliminary road map
Devices details
File manage
Screen interaction (Screenshot, record, touch control)
APK manager
Root / Fastboot tools
Where possible (at least in the beginning) I was to avoid functionality that is specific to devices and custom roms.
If you interested in getting involved drop me a reply on here. Eventually looking to distribute this over APT so would be really good for someone looking to add to or start there portfolio.