Skip navigation

And now for the first marsupial digimal…

Digimals::KoalatyAssuranceTesting := the (not-so) subtle science and exact art of designing unit tests which probe every aspect of your system, as tenaciously and tirelessly as a koala quests after eucalyptus leaves to munch 🙂  Ideally, a parent unit test will host child tests locally, will re-launch them upon failure, and will be able to automatically tweak system parameters (within use-case specific boundaries)  to support their likelihood of returning a success condition on their next try.

coalaFacekoala-bear-is-astonishedKoala3koala-ears-grass-animal-Favim.com-485062

Beautiful Stranger

Her smile brighter than gold

Distant treasure

veronicabelmont

 

EA’s Sim City

Greed is not always good

DRM is TRWTF

simcity2013-640x360

Seg Fault

Causal factors unclear

Dump step

hex_memory_dumpResidential_subdivision_under_development_garbage_dump_jan08_1

battletac_hud_gunmounted_02
I’ve been experimenting with the proper way to put a 2D UI over a 3D scene for a while and I’ve finally gotten it working (using JPCT-AE as the 3D rendering engine)– behold!

protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
am = this.getAssets();

ll = new LinearLayout(this);
hsv = new HorizontalScrollView(this);
img = (ImageButton) findViewById(R.id.tux_view);
img2 = new ImageButton(this);
img2.setImageResource(R.drawable.tux);
Logger.log(“onCreate”);

if (master != null) {
copy(master);
}

ui = new View(getApplication());
button = new Button(getApplication());
button.setText(“Hello!”);
//button.draw(canvas)
mGLView = new GLSurfaceView(getApplication());

mGLView.setEGLConfigChooser(new GLSurfaceView.EGLConfigChooser() {
public EGLConfig chooseConfig(EGL10 egl, EGLDisplay display) {
// Ensure that we get a 16bit framebuffer. Otherwise, we’ll fall
// back to Pixelflinger on some device (read: Samsung I7500)
int[] attributes = new int[] { EGL10.EGL_DEPTH_SIZE, 16, EGL10.EGL_NONE };
EGLConfig[] configs = new EGLConfig[1];
int[] result = new int[1];
egl.eglChooseConfig(display, attributes, configs, 1, result);
return configs[0];
}
});

renderer = new MyRenderer();
mGLView.setRenderer(renderer);
ll.addView(button);
ll.addView(img2);
hsv.addView(ll);
setContentView(mGLView);
addContentView(hsv, new LayoutParams(LayoutParams.WRAP_CONTENT, LayoutParams.WRAP_CONTENT));

}

This overlays 2D button and 2D imagebutton widgets over a 3D GLSurfaceView… awesome!

android_awesome

Okay, finally had some time to revisit this issue and I believe I’ve found the answer: First, before the xml layout or its components can be addressed they need to be inflated. I knew this, but I wasn’t sure when exactly they were inflated. It turns out that setContextView (and probably addContextView) trigger xml inflations. In order to have completely modular activity/view classes, I needed to do something like the following:

Activity Class–

package com.ai.ultimap;

import com.ai.ultimap.views.HomeView;
import android.app.Activity;
import android.os.Bundle;
import android.view.View;
import android.view.ViewGroup.LayoutParams;

public class UltiMapActivity extends Activity {
private View hv;

/** Called when the activity is first created. */
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
hv = new HomeView(this);
}
}

Custom View Class-

package com.ai.ultimap.views;

import com.ai.ultimap.R;
import android.app.Activity;
import android.os.Bundle;
import android.view.*;
import android.widget.*;
import android.view.View.OnClickListener;

public class HomeView extends View implements OnClickListener{

private RadioButton twodRB;
private RadioButton threedRB;
private TextView locTV;
private EditText editlocET;

public HomeView(Activity hAct) {
super(hAct);
//THE FOLLOWING LINE INFLATES– IT (or another function which calls xml inflation)
//MUST COME BEFORE ANY JAVA ADDRESSING OF WIDGETS IN
//THE XML LAYOUT
//Also note that even though you could invoke findViewById from a class extending
//View, in this case you must use hAct.findViewById. I believe this is due to the
//fact that the activity referenced by hAct is the object responsible for inflating
//the xml and thus the widgets need to be instantiated from it.
hAct.setContentView(R.layout.ultimap);
twodRB = (RadioButton) hAct.findViewById(R.id.twodRBV);
threedRB = (RadioButton) hAct.findViewById(R.id.threedRBV);
locTV = (TextView) hAct.findViewById(R.id.locationTV);
editlocET = (EditText) hAct.findViewById(R.id.locationETV);
//After instantiation however they can be freely accessed from java in
//non-activity classes, which is the point; see the next line…
twodRB.setOnClickListener(this);

}

@Override
public void onClick(View v) {
// TODO Auto-generated method stub
locTV.setText(“yo”);
}

}

This code works properly to load up the pre-defined xml view ultimap.xml and then address the widgets dynamically from Java (completely outside the activity class), changing the text of the location text view from ‘Location’ to ‘yo’ when the twodRB radiobutton is clicked!  To get a direct handle to the layout inflater service, invoke the following:

LayoutInflater instantiates a layout XML file into its corresponding View objects. It is never used directly. Instead, use an Activity object’s getLayoutInflater() or getSystemService(String) method to retrieve a standard LayoutInflater instance that is already hooked up to the current context and correctly configured for the device you are running on. For example:

LayoutInflater inflater = (LayoutInflater)context.getSystemService
      (Context.LAYOUT_INFLATER_SERVICE);

To create a new LayoutInflater with an additional LayoutInflater.Factory for your own views, you can use cloneInContext(Context) to clone an existing ViewFactory, and then call setFactory(LayoutInflater.Factory) on it to include your Factory.

(ref: http://developer.android.com/reference/android/view/LayoutInflater.html)

Hope this helps some googlers :)

linux_android_iphone1

Ever been vexed by defining layout parameters in android views via the “new LayoutParams(LayoutParams.whatever,LayoutParams.whatever)” syntax you see all over the place? Well I certainly am, and it’s also bad practice for runtime performance since you use the ‘new’ operator repeatedly for essentially the same task.

Below follows a convenience class for defining simple layout parameters:


import android.view.ViewGroup.LayoutParams;

public class DefineLayoutParams {
//the controls
private static final int MATCHMATCH = 1;
private static final int WRAPMATCH = 2;
private static final int MATCHWRAP = 3;
private static final int WRAPWRAP = 4;

//the ONE layoutparams object
private static LayoutParams floatParams = new LayoutParams(0,0);

public DefineLayoutParams(){

}

public static LayoutParams getParams(int type){
if (type == MATCHMATCH){
floatParams.width = LayoutParams.MATCH_PARENT;
floatParams.height = LayoutParams.MATCH_PARENT;
}
else if(type == WRAPWRAP){
floatParams.width = LayoutParams.WRAP_CONTENT;
floatParams.height = LayoutParams.WRAP_CONTENT;
}
else if (type == WRAPMATCH){
floatParams.width = LayoutParams.WRAP_CONTENT;
floatParams.height = LayoutParams.MATCH_PARENT;
}
else if (type == MATCHWRAP){
floatParams.width = LayoutParams.MATCH_PARENT;
floatParams.height = LayoutParams.WRAP_CONTENT;
}
return floatParams;
}

public static LayoutParams getCustomParams(int w, int h){
floatParams.width = w;
floatParams.height = h;
return floatParams;
}

public static int getMM(){
return MATCHMATCH;
}
public static int getWW(){
return WRAPWRAP;
}
public static int getWM(){
return WRAPMATCH;
}
public static int getMW(){
return MATCHWRAP;
}

}

Once this class is added to your project’s src directory, use it like so–
1. [predefined] hActivity.addContentView(hView,DefineLayoutParams.getParams(DefineLayoutParams.getWW()));
2.[custom] hActivity.addContentView(hView,DefineLayoutParams.getCustomParams(150,250));

Beguiling beauty

Sweet, soft, and sly

Be wary

OLYMPUS DIGITAL CAMERA

 

 

I’ve been working with parallel algorithms a lot lately, so here’s another digimal related to semaphores:

Digimals::SerpentineSemaphore := A variant semaphore structure configured to unobtrusively watch or slither between asynchronous threads, ominously gathering statistics until the perfectly opportunistic conditions (for collision, deadlock, starvation etc.) are met, at which point it mercilessly strikes target threads  with precise and undeniable directives!

Green-Beautiful-Emerald-Tree-Boa-snake (7) Emerald_Tree_Boa_by_Track_Maidens

Clever creation

Clockwork springs to life

Love realized

timecalcmashin_1600x1200