version 1.0

RollingBead is an android library that can make bead (lens) moving effect in Views like ImageViews(as of now). This is available in two flavours, i.e, MovingBead and StaticBead. Both can be used as and when required to produce circular bead(lens) effect.

• Moving Bead : The library provides enough methods to control movement of moving bead.
• single(Static) Bead : Method to form and dissolve single bead has been provided.
• Reduction in calculation : Effort has been made to reduce large amount of calculations involved.
• Unharmed image : Care has been taken not to harm the original image provided.
• Consistency : It provides required attributes and parameters to make it consistent accross screen densities.
• Async Calculations : The library does all operations(Moving Bead) asynchronously to avoid blocking the UI thread.

Add the following dependency to your app's build.gradle file:

allprojects {
	repositories {
		maven { url 'https://www.jitpack.io' }
	}
}

dependencies {
	        implementation 'com.github.ritik1991998:RollingBeadView:v1.0'
	}

Currently the library supports two types of usage:

• Get the ImageView object and pass in to RollingBead as parameter

        ImageView imageView = (ImageView) findViewById(R.id.imageView);
        RollingBead rb = new RollingBead(imageView);
        // or directly pass the bitmap

• use the generateFixedBead method to generate a static bead

• use the dissolveFixedBead method to dissolve a static bead

Example 1

imageView.setImageBitmap(rb.generateFixedBead(0.025f, 0.025f, 0.45f, 2.0, true, true));

imageView.setImageBitmap(rb.dissolveFixedBead(0.025f, 0.025f, 0.45f, true, true));

Example 2

imageView.setImageBitmap(rb.generateFixedBead(0.93f, 0.46f, 0.2f, 2.0, true, true));

imageView.setImageBitmap(rb.dissolveFixedBead(0.93f, 0.46f, 0.2f, true, true));

Example 1

 <com.example.android.rollingbeadlibrary.RollingBeadImageView
        android:id="@+id/mimage"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:layout_centerVertical="true"
        android:src="@drawable/life"
        app:center_X="37%"
        app:center_Y="5%"
        app:direction="positive"
        app:movement="3.7%"
        app:number_Of_Times="1"
        app:radius="14.8%"
        app:orientation="vertical"
        app:repetition_Times="220" />

Example 2

    <com.example.android.rollingbeadlibrary.RollingBeadImageView
        android:id="@+id/mimage"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:layout_centerVertical="true"
        android:src="@drawable/hope_1"
        app:center_X="245dp"
        app:center_Y="203dp"
        app:direction="positive"
        app:movement="23dp"
        app:number_Of_Times="1"
        app:radius="35dp"
        app:orientation="horizontal"
        app:repetition_Times="92" />

• Parameters for moving bead: RollingBead

*Or use generateFixedBead with 0.0 as lens_factor
**returns Bitmap object

• Attributes for moving bead: RollingBeadImageView

*attribute: dimension or fraction [0%,100%)(w.r.t height)
*#attribute: dimension or fraction [0%,100%)(w.r.t width)
**attribute: integer
***attribute: enum
# parameters: int(Pixels) or float [0,1)(w.r.t height)
## parameters: int(Pixels) or float [0,1)(w.r.t width)

The methods used in the library intensively uses system's resources. Thus encountering some of the vital limitations!!. Do go through these before using the library:

• Static bead function is currently handled on the UI thread. It will be improved in the future. Currently you can make separate thread yourself or make a PR for the same.

• making lens_factor negative squeezes the image, (instead of bulging it), but this might produce error!!.

• The entire movingBeadImageView is highly vulnerable to frequent GC event, thus affectingly reducing performance and disturbing the UI thread notoriously. To counter this, reduce the radius, movement and increase repetition_Times. At the same time smaller image and horizontal orientation will be quiet helpful.

• When moving forward, moving bead creates a major segment instead of complete circle to reduce calculation.

• Though moving bead does't disturbs a single pixel after passing, please use stopRender when switching the current activity.

• Following the point above, don't put set request consecutively within repetition_Times interval. This might severely damage the input image.

All contributions are welcome and appreciated. Please make a Pull Request or open an issue, if necessary. This may also include any form of feature enhancement. Every constructive criticism is welcome.

• Static bead handling in non UI thread
• Extending to other views particularly TextView

The initial algorithm for generating bead effect was taken from this repo