Skip to main content

How to make glow effect around a bitmap?



The following code is what I got so far. However, there are 2 issues:









  1. I want both inner and outer glow effects, which looking similar to the Photoshop's blending options. But I only managed to make the outer glow, if I set BlurMaskFilter.Blur.INNER or other value, the whole image is blocked, instead of just edges.









  2. Despite I set "FF" as alpha value, the glow color is still very dark.







    Bitmap alpha = origin.extractAlpha();

    BlurMaskFilter blurMaskFilter = new BlurMaskFilter(5, BlurMaskFilter.Blur.OUTER);





    Paint paint = new Paint();

    paint.setMaskFilter(blurMaskFilter);

    paint.setColor(0xffffffff);





    Canvas canvas = new Canvas(origin);

    canvas.drawBitmap(alpha, 0, 0, paint);





    return origin;











alt text



Source: Tips4all

Comments

  1. I think there is no method in android to create glow effects. you have to make them yourself from scratch or find some java library that supports this.

    the simplest thing that i prefer to use is making layers of images. basically you define a relative layout and put 2 imageViews one on top of another. just create the photoshop effect in its own layer and rasterize that layer, save it to png place it on top of your image. But careful if you are using this method with large images you can easily get that VM exceeded exception. Resampling the bitmaps according to the view size is a pretty good solution for this issue.

    the other method that comes to my mind is drawing gradients over your image (ex: radial gradient that is transparent in the middle and white among the edges- to get a white glow) but this way takes a lot of time to tune up to exactly what you need so in my opinion isn't worth the effort).

    Also here is a link for a site that makes java image filters. maybe you can find something that does the job for you.

    http://www.jhlabs.com/ip/filters/index.html

    ReplyDelete
  2. How about this:

    <LinearLayout
    xmlns:android="http://schemas.android.com/apk/res/android"
    android:orientation="vertical"
    android:background="@color/Black"
    android:layout_width="fill_parent"
    android:layout_height="fill_parent">
    <TextView android:textColor="@color/White"
    android:layout_width="wrap_content"
    android:text="Glowing Text"
    android:layout_height="wrap_content"
    android:padding="2dp"
    android:shadowColor="@color/White"
    android:shadowDx="0"
    android:shadowDy="0"
    android:shadowRadius="3" />
    </LinearLayout>


    found here: http://blog.stylingandroid.com/archives/378:

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex