Messages by klickr

Hey Jorge,

I don't know of a readily available list but if you visit DeviceAtlas.com and search for devices that support at least MIDP2.0 and at least CLDC 1.0 it will return a list of handsets.

I have found that my Kuix apps are between 240KB on average. Therefore you need to ensure you develop for devices that allows a MAX-JAR-SIZE of >250KB.

Else Kuix works perfectly fine.

Klickr

Hey Talavang

Keep the faith buddy. Keep developing in Java, but don't neglect to keep researching new software languages. Objective C is not a bad one to know - for whatever Apple might get up to in the years to come. I would have been worried if I was a Microsoft Developer - specially guys with pre-C# skills. Eish.

Klickr.

Hey Pandora

I'm also fulltime into J2ME and enjoying myself. The advertising industry is only now awakening to the value of mobile apps. And the truth is iPhone and Android is far from taking over the world just yet. I am extending my skillset to include the new platforms though. But right now, 80% of my income is J2ME.

J2ME will only die if Sun gives up the fight. It is high time for Sun to take a long hard look at where they want to go with J2ME and shape it up. If Sun is silly enough to not respond to the current market conditions they would have lost everything they have worked for over the past 6 to 8 years.

Anyway, why don't we start a forum to help Kuix live on? Port it MIDP3.0. Sort out the issues. Make it lighter in weight. Let's do whatever we need to do!

Hi Shappy,

Yup, I experienced the exact same issue - but it was sort of resolved by pandora808's solution up-top. Having implemented that solution I never experienced the static-screen issue again. However, what I did discover was that once you push a new Task into the worker instance a "memory leak" occurs. The worker just keeps on creating objects even when there is no acitivity. This can be seen on a memory monitor. Just launch the app, push a new Task and then sit back and watch the memory fill up. Calling System.gc() clears out all the "spawned" objects - but new objects start forming at the very next worker cycle. An out of memory error results.

L.

Dear Kalmeo team

Is there a way to split a screen where only the second container is scrollable?

I would like to create a screen that contains a "static" heading-part and a scrollable menu part. The heading part needs not be focusable, only the scolling part should be focusable.

Any suggestions?

Hi!

With respect to ClassNotFoundException on BlackBerry handsets I experienced the same and resolved it with a BlackBerry specific build of the Kuix framework.

(I use the BlackBerry JDE side-by-side with Netbeans but I build my BlackBerry apps using the JDE. It just makes life easier when deploying. Anyway, to get to the point:....)

Tofu is right when saying:

Those exceptions come from the platform auto-detection.

 When you are building specifically for BlackBerry you don't need to auto-detect the platform (coz you know you are building for BlackBerry). Therefore it makes sense to remove the platform detection code from the KuixCanvas class.

Here's how I did it (Be advised - you are doing this at your own risk. Back up before you try this!)

OPEN:
org.kalmeo.kuix.core.KuixCanvas;

FIND METHOD:
getPlatform();

DO:
Remove all try{}catch() blocks that contains Class.forName("nothingToDoWithBlackBerry") - where nothingToDoWithBlackBerry=classNames that are used to detect Non-BB platforms.

This is what my new getPlatform method looks like:

        /**
         * Returns mobile phone platform
         *
         * @return name mobile phone platform
         */
        private String getPlatform() {               
                return KuixConstants.PLATFORM_BLACKBERRY;
        }

Worked for me and tested and several BB handsets.

Let me know if there was a better way of doing this.

Friendly greetings from Sunny South Africa!

PS. If you haven't yet bought a Kuix license please consider doing so ASAP. We need to support this project. It is possibly the best effort at a portable GUI for J2ME around. I have tried many and nothing compares. Buy a license!

Hi Pandora, Tofu and all future readers of this thread.

Kuix Version: 1.1.0

Just to confirm, the Worker Solution posted above resolved the "White Screen" and "Static Screen" issues we experienced.

 WorkerTask repaintTask = new WorkerTask() {
            public boolean run() {
                Kuix.getCanvas().repaint();
                return false;
            }
        };
        Worker.instance.pushTask(repaintTask);

For newbies here's how I did it (Moderators please correct where required):

OPEN: org.kalmeo.kuix.widget.Screen

ADD:
import org.kalmeo.util.worker.Worker;
import org.kalmeo.util.worker.WorkerTask;

FIND METHOD:
setCurrent()  in the Screen class

ADD CODE BELOW LINE "Kuix.getCanvas().getDesktop().setCurrentScreen(this);":

      //an effort to avoid white screens and hanging canvas
            WorkerTask repaintTask = new WorkerTask() {

                public boolean run() {
                    Kuix.getCanvas().repaint();
                    return false;
                }
            };
            Worker.instance.pushTask(repaintTask);

REBUILD you project. Thanks Pandora808 for this and many other solutions and tips. Much appreciated!

PS. If you haven't already bought the Kuix License, please consider doing it ASAP. We need to fund this project so that it doesn't stop developing.

Greetings from Sunny South Africa!