[Xposed Framework Modules] WisdomSky:
Source Code

Link.

Paypal Donations

If you have a very nice heart and want to make my wish come true, please don't hesistate to send your donations to my paypal account: julianpaolodayag143@gmail.com

Scripting

(For themers and programmers)

Apart from the Laboratory where users are provided with user-friendly interface, there is an another way to make modifications and that is by using the scripting feature of Resflux.

Soon, I will be focusing on adding more features to it. One is providing support for layouts. Not the whole layout, but to the components inside defined with an id.

When you export packages mod in Resflux, you will be given a zip file. And when you look inside it, you will actually find atleast a Resflux.ini file. And when you look inside the Resflux.ini file, you will see how Resflux turn everything into series of keys, sections, comments and how they are arranged.

The structure of the Resflux.ini complies with of an INI file as defined here:

http://en.m.wikipedia.org/wiki/INI_file

From the INI File wiki page, you can learn about which one is a key, section or comment.

From it, you may start studying how to write your own.

If you are a programmer, you may find it very easy to understand on how it works. And you can see that you are like dealing with objects. For now, we only have drawable, string, color, boolean, integer, layout, resflux and ini.

Rules

Resflux have rules in when it comes to syntax, grouping and arrangement.

RULE 1: The Resflux.ini can contain only keys, sections, comments and blank lines(with space or not) and should follow their corresponding syntax and must occupy a line therefore two keys in a single line is not honored.

For comments:

# [any text here]
; [any text here]

For sections:

[package.name.here]

For keys:

object.property_name = value
object.property_name : value

For blank lines:

A an empty line or composed of whitespaces.

If an invalid syntax is found, resflux will return error status 0

RULE 2: All resflux.* must be grouped together and must be placed before sections and any other keys except comments.

When this rule is violated, Resflux will return Error Status 1 during an attempt of importing it.

Rule 3: ]: All ini.* must be grouped together and must be placed after resflux.* and before sections and any other keys except comments.

When violated, it returns error status 2.

Rule 4: Before starting defining a key, you must have atleast defined a section. A section is composed of a opening square bracket "[", followed by the package name of the target app, and then a closing square bracket "]".

For example:

[com.my.app]

Rule 5: Each key must follow their respective value's format.

For drawable:

it could be a PNG image relative path like:

drawable.ic_launcher = icon.png
# or it could be also a color hex code:
drawable.ic_launcher = #ffff0000

For color:

color can have a single possible format for its value.

color.bg_color = #ff0000

For boolean:

boolean can only have two choices, the value could be either true or false.

boolean.enable_nothing = true
boolean.enable_nothing = false

For string:

string can have any value.

string.app_name = anything you want!!!
# enclosing value with quotes is also fine and work with all types of keys
string.app_name = "!want you anything"