Skip to content

Commit b72527d

Browse files
curoviyxrurmn20
curoviyxru
and
rmn20
committed
Public source version
Co-authored-by: rmn20 <[email protected]>
0 parents  commit b72527d

File tree

3,472 files changed

+23914
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

3,472 files changed

+23914
-0
lines changed

‎.gitignore

+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
build
2+
dist
3+
/build/
4+
src/res/Thumbs.db
5+
nbproject/private
6+
emoji/Thumbs.db
7+
Thumbs.db
8+
/iconpacker/nbproject/private/
9+
iconpacker/nbproject/genfiles.properties
10+
/iconpacker/build/
11+
iconpacker/*.png
12+
iconpacker/*.rle

‎.gitmodules

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
[submodule "j2vk"]
2+
path = j2vk
3+
url = https://github.com/VK4ME/j2vk

‎COPYING

+674
Large diffs are not rendered by default.

‎README.md

+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
# VK4ME Next
2+
![Logo](src/res/new/phmini.png)
3+
4+
Unofficial J2ME application for the most popular Russian social site, VK.
5+
6+
# Credits
7+
- [curoviyxru](https://github.com/curoviyxru)
8+
- [rmn20](https://github.com/rmn20)
9+
10+
# Depends on
11+
- [TimeUtil](https://github.com/solkin/tomemu/blob/master/src/com/tomclaw/utils/TimeUtil.java) by TomClaw
12+
- [J2VK](https://github.com/vk4me/j2vk)
13+
- [json-org](https://github.com/vk4me/json-org)
14+
- [MidletIntegration](https://github.com/shinovon/MIDletIntegration)

‎build.xml

+83
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
<?xml version="1.0" encoding="UTF-8"?>
2+
<!-- You may freely edit this file. See commented blocks below for -->
3+
<!-- some examples of how to customize the build. -->
4+
<!-- (If you delete it and reopen the project it will be recreated.) -->
5+
<project name="vk4me" default="jar" basedir=".">
6+
<description>Builds, tests, and runs the project .</description>
7+
<import file="nbproject/build-impl.xml"/>
8+
<!--
9+
10+
There exist several targets which are by default empty and which can be
11+
used for execution of your tasks. These targets are usually executed
12+
before and after some main targets. They are:
13+
14+
pre-init: called before initialization of project properties
15+
post-init: called after initialization of project properties
16+
pre-preprocess: called before text preprocessing of sources
17+
post-preprocess: called after text preprocessing of sources
18+
pre-compile: called before source compilation
19+
post-compile: called after source compilation
20+
pre-obfuscate: called before obfuscation
21+
post-obfuscate: called after obfuscation
22+
pre-preverify: called before preverification
23+
post-preverify: called after preverification
24+
pre-jar: called before jar building
25+
post-jar: called after jar building
26+
pre-build: called before final distribution building
27+
post-build: called after final distribution building
28+
pre-clean: called before cleaning build products
29+
post-clean: called after cleaning build products
30+
31+
Example of pluging a my-special-task after the compilation could look like
32+
33+
<target name="post-compile">
34+
<my-special-task>
35+
<fileset dir="${build.classes.dir}"/>
36+
</my-special-task>
37+
</target>
38+
39+
For list of available properties check the imported
40+
nbproject/build-impl.xml file.
41+
42+
Other way how to customize the build is by overriding existing main targets.
43+
The target of interest are:
44+
45+
preprocess: preprocessing
46+
extract-libs: extraction of libraries and resources
47+
compile: compilation
48+
create-jad: construction of jad and jar manifest source
49+
obfuscate: obfuscation
50+
preverify: preverification
51+
jar: jar archive building
52+
run: execution
53+
debug: execution in debug mode
54+
build: building of the final distribution
55+
javadoc: javadoc generation
56+
57+
Example of overriding the target for project execution could look like
58+
59+
<target name="run" depends="init,jar">
60+
<my-special-exec jadfile="${dist.dir}/${dist.jad}"/>
61+
</target>
62+
63+
Be careful about correct dependencies when overriding original target.
64+
Again, for list of available properties which you can use check the target
65+
you are overriding in nbproject/build-impl.xml file.
66+
67+
A special target for-all-configs can be used to run some specific targets for
68+
all project configurations in a sequence. File nbproject/build-impl.xml
69+
already contains some "for-all" targets:
70+
71+
jar-all
72+
javadoc-all
73+
clean-all
74+
75+
Example of definition of target iterating over all project configurations:
76+
77+
<target name="jar-all">
78+
<property name="target.to.call" value="jar"/>
79+
<antcall target="for-all-configs"/>
80+
</target>
81+
82+
-->
83+
</project>

‎iconpacker/build.xml

+74
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
<?xml version="1.0" encoding="UTF-8"?>
2+
<!-- You may freely edit this file. See commented blocks below for -->
3+
<!-- some examples of how to customize the build. -->
4+
<!-- (If you delete it and reopen the project it will be recreated.) -->
5+
<!-- By default, only the Clean and Build commands use this build script. -->
6+
<!-- Commands such as Run, Debug, and Test only use this build script if -->
7+
<!-- the Compile on Save feature is turned off for the project. -->
8+
<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
9+
<!-- in the project's Project Properties dialog box.-->
10+
<project name="iconpacker" default="default" basedir=".">
11+
<description>Builds, tests, and runs the project iconpacker.</description>
12+
<import file="nbproject/build-impl.xml"/>
13+
<!--
14+
15+
There exist several targets which are by default empty and which can be
16+
used for execution of your tasks. These targets are usually executed
17+
before and after some main targets. They are:
18+
19+
-pre-init: called before initialization of project properties
20+
-post-init: called after initialization of project properties
21+
-pre-compile: called before javac compilation
22+
-post-compile: called after javac compilation
23+
-pre-compile-single: called before javac compilation of single file
24+
-post-compile-single: called after javac compilation of single file
25+
-pre-compile-test: called before javac compilation of JUnit tests
26+
-post-compile-test: called after javac compilation of JUnit tests
27+
-pre-compile-test-single: called before javac compilation of single JUnit test
28+
-post-compile-test-single: called after javac compilation of single JUunit test
29+
-pre-jar: called before JAR building
30+
-post-jar: called after JAR building
31+
-post-clean: called after cleaning build products
32+
33+
(Targets beginning with '-' are not intended to be called on their own.)
34+
35+
Example of inserting an obfuscator after compilation could look like this:
36+
37+
<target name="-post-compile">
38+
<obfuscate>
39+
<fileset dir="${build.classes.dir}"/>
40+
</obfuscate>
41+
</target>
42+
43+
For list of available properties check the imported
44+
nbproject/build-impl.xml file.
45+
46+
47+
Another way to customize the build is by overriding existing main targets.
48+
The targets of interest are:
49+
50+
-init-macrodef-javac: defines macro for javac compilation
51+
-init-macrodef-junit: defines macro for junit execution
52+
-init-macrodef-debug: defines macro for class debugging
53+
-init-macrodef-java: defines macro for class execution
54+
-do-jar-with-manifest: JAR building (if you are using a manifest)
55+
-do-jar-without-manifest: JAR building (if you are not using a manifest)
56+
run: execution of project
57+
-javadoc-build: Javadoc generation
58+
test-report: JUnit report generation
59+
60+
An example of overriding the target for project execution could look like this:
61+
62+
<target name="run" depends="iconpacker-impl.jar">
63+
<exec dir="bin" executable="launcher.exe">
64+
<arg file="${dist.jar}"/>
65+
</exec>
66+
</target>
67+
68+
Notice that the overridden target depends on the jar target and not only on
69+
the compile target as the regular run target does. Again, for a list of available
70+
properties which you can use, check the target you are overriding in the
71+
nbproject/build-impl.xml file.
72+
73+
-->
74+
</project>

‎iconpacker/lazy.bat

+2
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
cd %~dp0
2+
java -jar dist/iconpacker.jar %*

‎iconpacker/manifest.mf

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
Manifest-Version: 1.0
2+
X-COMMENT: Main-Class will be added automatically by build
3+

0 commit comments

Comments
 (0)