mirror of
https://github.com/pachli/pachli-android.git
synced 2025-02-02 18:37:00 +01:00
f0fc0fd530
Continue modularisation by moving core activity classes that almost all activities depende on to a `core.activity` module. This includes core "helper" classes as well. Implement core.activity: - Contains BaseActivity, BottomSheetActivity - Contains LinkHelper and other utility classes used by activities Implement core.common.extensions: - Move ViewBindingExtensions and ViewExtensions here Implement core.common.util: - Move BlurHashDecoder and VersionName here Implement core.designsystem: - Holds common resources (animations, colours, drawables, etc) used through the app - Import "core.designsystem.R as DR" through the app to distinguish from the module's own resources Implement feature.login: - Move the LoginActivity and related code/resources to its own module Implement tools/mvstring - Moves string resources (and all translations) from one module to another
24 lines
526 B
Markdown
24 lines
526 B
Markdown
# mvstring
|
|
|
|
## Synopsis
|
|
|
|
`mvstring` moves a string resource from one module to another.
|
|
|
|
## Usage
|
|
|
|
From the parent directory, run:
|
|
|
|
```shell
|
|
./runtools mvstring dst-module id
|
|
|
|
./runtools mvstring src-module dst-module id
|
|
```
|
|
|
|
where:
|
|
|
|
- `src-module` - identifier for the source module that contains the string. If omitted then `app` is assumed.
|
|
- `dst-module` - identifier for the destination module
|
|
- `id` - resource ID of the string to move
|
|
|
|
Verify the modifications made to the Pachli resource files, and commit the result.
|