hSuite Getting
Started
|
||||||||||||||
Installation
Download the zip file from the main page. The zip file contains everything, i.e adt, jdk and an hsuite directory. Aside from un-zipping, there is no furthur installation. Everything is self contained and environment variables are made on the fly. Unzip to a directory of your choice.
exceptions; * Do not unzip to a directory with spaces in the name, e.g "my dir" * It is advisable not to unzip to a directory named "temp" Tip: hSuite is about 120mb with loads of small files inside. So either turn off your virus checker or add an exclusion zone to c:\mytest. Also, 7-zip is about 10 times faster than window's own unzipper. |
||||||||||||||
Compiling the Example
Project
Included in hSuite is a test-project that performs a
few tests. Below is a quick run-through on how to make a standalone apk of the test-project. This assumes you have Windows.
1. Download
hSuite windows version if you haven't yet
already.
2. Unpack it to somewhere e.g c:\mytest 3. Go into the hsuite dir and run hpatcher.exe 4. (Optional) Select some patches, and click Apply. (Optional) 5. Click Customise. Fill in the form;
App
Version:1.00, com.rfo.test App_Name:Test 6. Click App Icon
Point the input file to test-project/test-icon.png 7.
Click
Permissions.
Select the first two. Click Back.Click 144x144 xxhdpi Click Back 8. Click Loading.
Point the image file to test-project/splash.png 9. Click
StandAlone.
Then Click Standalone
APK. The standalone fields will
open up.Click Back
Point
(main).bas to test-project/source/test.bas Type "test" for app_path. Click Back. 10. click Commit 11. click Compile and wait till it finishes. 12. A test.apk file will be found in c:\mytest\hsuite\work That's a quick example. There is some stuff you can do in-between, so just explore it in your own time. It's completely safe, If you get into trouble, you can always delete the whole c:\mytest and start again. |
||||||||||||||
Create a customised version of
hBasic
When you first install hSuite there is a [master] directory. When you first run hPatcher it checks to see of the [basic] directory exists. If it does not exist, it copies [master] to [basic]. (this is the same as if you had pressed Reset). This copy of the master is hBasic in it's base form. At first installation Customise>StandAlone is by default OFF. This is called Standard mode. If you now press Compile, You will generate a version of hBasic without any patches. If you instead select all of the patches and click Apply and then Compile, you will have a version of hBasic that's almost the same as the official release version. I say 'almost' because the version number and permissions will be different. These can be changed inside the Customise panel. Customisation for a standard hBasic therefore depends on which patches you select, the version number you enter, the permissions you choose and whether not you want a splash and loading screen. It is best not to change anything else in the Customise panel. When you have finished with Customise, click Commit to apply changes and then Compile. |
||||||||||||||