It was organized by a group aptly called Cebuntu (Cebu + Ubuntu) which draws most
of its members from the linux enthusiasts of istorya.net.

I wasn’t expecting the party to be that grand(honestly). There was food (real food
like lechon and rice!) and the place was posh (The Jive Restobar in Lahug) and
overlooking Cebu city.

This release party was happening in sync with most release parties in the country,
particularly the one in Orange and Bronze in Makati. Streaming videos were exchanged.
Nap made an impromptu speech. He didn’t know he was speaking until after he was
called (he had a memorable look on his face, as Jev pointed out).

We distributed CDs, stickers (thanks to another member who printed them),
exchanged ideas on how to spread the gospel of linux and Ubuntu all over the Visayas
region (we are not limiting ourselves to Cebu!) and discussed Ubuntu’s bug no. 1
(filed by Mark Shuttleworth himself). We also discussed on how best to
convert users to ubuntu (wow them with compiz effects) and how to dominate the
world (start in the schools). We also had a brief discussion with regards to the
usage and guidelines of the Ubuntu trademark and logos.

But best of all, we elected our first contact person to represent the chapter.
We wanted to be recognized as the official Cebu chapter of the Ubuntu local
community here in the Philippines (so we can tell sponsors, business people,
schools,etc. that we do represent a real organization and that they can take
us seriously) and as Nap pointed out, the first step is to have a contact person
to represent us so he can link that person up with the current LoCo head.

Congrats to Scriptwarlock, by the way, for being that contact person!

After a ravaged lechon and a brief photo-op, we left the party with hopes
and dreams that someday we will see Ubuntu being commonly used in Cebu
in lieu of pirated windows (or even non-pirated ones). And maybe, just maybe,
we can then say proudly that we squashed Ubuntu’s Bug No. 1 here in Cebu!

So, if you are in Cebu and you are an Ubuntu user, please participate and become
a member of Cebuntu. Our forum is Cebuntu and most of our members hang out in
IRC, in the #cebuntu channel in Freenode.

Pictures will appear on this blog post after I’ve gotten them from Jan and Nap.

—————————————————————————————-
PS: Thanks to the sponsors, the lechon was yummy and the place, nice!
—————————————————————————————-

The first thing I check out if I’m planning to use a particular editor for the long haul is if its color theme can be modified to my taste. Additional bonus is if it has a way to import/export those themes, so I can just find a color theme in the internet and import it to my editor.

These days, my IDE of choice is Eclipse. Apart from being fast and powerful, it has all those features I mentioned above. This blog entry is about a theme I’ve created that I’ve been using for almost 3 years now.

I named it the “Green Pintado”(green-painted ones) theme. It is a modification of a theme I’ve used before in Xcode which I have also created myself.

As the name implies, it is a green theme. Much of the colors are based on green and the colors that stand out against it or blend harmoniously with it.

Below you will find a screenshot of the theme being used.

And here is the link to the Eclipse Preference File -> http://editor-color-themes.googlecode.com/files/green-pintado.epf

To install it, on Eclipse, go to File > Import > General > Preferences , browse for the file, click Finish. Voila!

By the way, I’ve created a google project to act as a repository for all the syntax highlighting color themes I have created and those that will be contributed in the future. If you want your theme to be included in there, please visit http://code.google.com/p/editor-color-themes/

There are times when you want to unit test a part of your code. Maybe for proof-of-concept that it works, or you just wanna be sure that it works before you hit that execute button.

The thing is, that part of the code requires that a runtime mechanism be running.

Am I talking gibberish ? Let me give you an example: Suppose you are writing an eclipse plugin, and you are writing an action that would delete an item from a tree. That’s a fairly generic operation, so you start writing an action class that accepts an object and another object that you can use to find the parent of that object. Then you write the actual action method which finds the parent of this object and deletes it.

public class DeleteItemAction extends something<br />
{<br />
&nbsp;&nbsp; &nbsp;private ITreeContentProvider provider;<br />
&nbsp;&nbsp; &nbsp;public DeleteItemAction( ITreeContentProvider provider )<br />
&nbsp;&nbsp; &nbsp;{<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;this.provider = provider;<br />
&nbsp;&nbsp; &nbsp;}

&nbsp;&nbsp; &nbsp;public void doAction( Object object )<br />
&nbsp;&nbsp; &nbsp;{<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;Object parentObject = contentProvider.getParent( object );<br />
&nbsp;&nbsp; &nbsp; &nbsp; ( (Something) parentObject ).removeChild( object );<br />
&nbsp;&nbsp; &nbsp;}<br />
}

Perfect. Now, I can write a test for this code.

@Test<br />
public void testDeleteItemAction()<br />
{<br />
&nbsp;&nbsp; &nbsp;List&lt;object&gt; objectList = getObjects();<br />
&nbsp;&nbsp; &nbsp;ITreeContentProvider provider = getContentProvider( objectList );<br />
&nbsp;&nbsp; &nbsp;Object firstObject = objectList.get( 0 ); &nbsp;&nbsp;

    assertTrue(objectList.contains( firstObject ) );    

&nbsp;&nbsp; &nbsp;DeleteItemAction action = new DeleteItemAction( provider );<br />
&nbsp;&nbsp; &nbsp;action.doAction( firstObject );

&nbsp;&nbsp; &nbsp;assertFalse( objectList.contains( firstObject ) );<br />
}

Then you suddenly remember that you have to prompt your user if he really wants to delete it or cancel. So you then scrambled to your other codes and look for that message-box-launching code,.. you found it,.. you copy-paste it.

public class DeleteItemAction extends something<br />
{<br />
&nbsp;&nbsp; &nbsp;private ITreeContentProvider provider;<br />
&nbsp;&nbsp; &nbsp;public DeleteItemAction( ITreeContentProvider provider )<br />
&nbsp;&nbsp; &nbsp;{<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;this.provider = provider;<br />
&nbsp;&nbsp; &nbsp;}

&nbsp;&nbsp;&nbsp;&nbsp; public void doAction( Object object )<br />
&nbsp;&nbsp; &nbsp; {<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; MessageBox messageBox =<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; new MessageBox( PlatformUI.getWorkbench().getActiveWorkbenchWindow().getShell(), SWT.ICON_QUESTION |<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; SWT.YES | SWT.NO );<br />

&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; messageBox.setMessage( &quot;Do you want to delete this object&quot; );<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; messageBox.setText( &quot;Delete object?&quot; );&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; int response = messageBox.open();<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; if ( response == SWT.YES )<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; {<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Object parentObject = contentProvider.getParent( object );<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ( (Something) parentObject ).removeChild( object );<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; }<br />
&nbsp;&nbsp; &nbsp; }<br />
}

And you smirk and say, damn, I’m good. Then you run your test.

Surprise. It doesn’t run. The code you copy and pasted pops up a message box,.. and you need to run your test as an eclipse plugin test in order for the entire eclipse runtime mechanism to be running when you perform the test,.. for the message box to pop-up! The hassles you get for a want of a test to exercise a simple code.

So what do you do ? Do you give up and just click “Run eclipse plugin test” and wait for ages for it to load? Or do you restructure your code so you can still just “Run junit test” and still be able to test your code ?

I prefer the latter. Turns out, it was easy.

Abstract. Abstract the part that requires the runtime mechanism. In this case, the code that calls the message box. Move it out of the generic code, make it protected, so it could be overridden. And when you write your junit test, create a mock class that extends it and override the “heavy code” with something that just returns true.

To illustrate:

public class DeleteItemAction extends something<br />
{<br />
&nbsp;&nbsp; &nbsp;private ITreeContentProvider provider;<br />
&nbsp;&nbsp; &nbsp;public DeleteItemAction( ITreeContentProvider provider )<br />
&nbsp;&nbsp; &nbsp;{<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;this.provider = provider;<br />
&nbsp;&nbsp; &nbsp;}

&nbsp;&nbsp; &nbsp;public void doAction( Object object )<br />
&nbsp;&nbsp; &nbsp;{<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;if ( showWarningAndPrompt() )<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;{<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Object parentObject = contentProvider.getParent( object );<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;( (Something) parentObject ).removeChild( object );<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;}
&nbsp;&nbsp; &nbsp;}

&nbsp;&nbsp; &nbsp;protected boolean showWarningAndPrompt()<br />
&nbsp;&nbsp; &nbsp;{<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;MessageBox messageBox =<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;new MessageBox( PlatformUI.getWorkbench().getActiveWorkbenchWindow().getShell(), SWT.ICON_QUESTION |<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;SWT.YES | SWT.NO );messageBox.setMessage( &quot;Do you want to delete this object&quot; );<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;messageBox.setText( &quot;Delete object?&quot; );&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;int response = messageBox.open();<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;if ( response == SWT.YES )<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;return true;<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;else<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;return false;<br />
&nbsp;&nbsp; &nbsp;}

}

and in your test

@Test<br />
public void testDeleteItemAction()<br />
{<br />
&nbsp;&nbsp; &nbsp;List&lt;object&gt; objectList = getObjects();<br />
&nbsp;&nbsp; &nbsp;ITreeContentProvider provider = getContentProvider( objectList );<br />
&nbsp;&nbsp; &nbsp;Object firstObject = objectList.get( 0 );

    assertTrue(objectList.contains( firstObject ) );    

&nbsp;&nbsp; &nbsp;DeleteItemAction action = new DeleteItemActionMock( provider );<br />
&nbsp;&nbsp; &nbsp;action.doAction( firstObject );

    assertFalse( objectList.contains( firstObject ) );

}

private class DeleteItemActionMock extends DeleteItemAction<br />
{<br />
&nbsp;&nbsp; &nbsp;public DeleteItemActionMock( ITreeContentProvider contentProvider )<br />
&nbsp;&nbsp; &nbsp;{<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;super( contentProvider );<br />
&nbsp;&nbsp; &nbsp;}&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp; protected boolean showWarningAndPrompt()<br />
&nbsp;&nbsp; &nbsp;{<br />
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;return true;<br />
&nbsp;&nbsp; &nbsp;}<br />
}

The latter doesn’t need the entire eclipse runtime to run,.. it’s just another junit test.

Additional benefit ? Your code has now a better structure.

I believe this technique has a name already. I just don’t know.

I hate it when wordpress mangles my code.

1. The need to constantly check Slashdot and Digg when a command you issued on the commandline hasn’t finished yet.

• Have you ever done a “svn co” or compiled a huge maven project, and while waiting for it to finish, you constantly switch to your second ubuntu workspace so you could check Slashdot and Digg already opened on a browser there ?
• Bonus : You actually added a keyboard shortcut so you could easily switch workspaces? (Not that there isn’t a builtin shortcut, but Alt-1 and Alt-2 is way easier).

2. The need to slap that tech salesperson who told that other customer how Windows is much better than mac or linux.

3. The need to get on an “overheard” debate about any tech stuff ( C++ vs Java, Rails vs PHP, KDE vs Gnome, Eclipse vs Idea vs Netbeans, Ant vs Maven, Starwars vs Star Trek, etc.). You get my drift.

4. The need to have a practical working knowledge and understanding of techs whose names are 3 to 6 letter acronyms ( AJAX, XML-RPC, ROR , SOAP, J2EE, EJB ,.. FHM, MTC, GMA, ABS-CBN, :)) ).

5. The need to read

• All interviews of Linus Torvalds, Richard Stallman, Steve Wozniak ,… etc.
• All news about black holes, expanding galaxies, extra-solar planets,… etc.
• All XKCD and Dilbert comic strips.
• All your friend’s Twit.
• All articles bashing Vista.
• The latest news on Hans Reiser’s trial.
• The latest commit message on the open source project you’ve contributed on.
• The blogs of the committers of those high profile open source projects.
• The latest analysis on the nature of the force and their usage by several notable sith’s and jedi (Nap included).
• ….

6. The need to have a god-like familiarity of several technologies while being a “jack of all trades, master of none” on the rest.

7. The need to blog about your being a geek.

8. The need to constantly switch from working (coding) to doing “all of the above”, while simultaneously writing your next blog, Gimp-ing the logo of “the next great software that you’re gonna write” and educating your cubiclemate on what being RESTful means.

I rest here. Its 1:52 AM, I should be sleeping instead of blogging. If you think that sleeping time should be converted to “coding/blogging/making a website” time ,.. the force is strong in you!

1. You create a panel (HorizontalPanel or VerticalPanel) to act as the box. We will call this the “box panel”.
2. This panel must only have a single element. So, if you have a form with multiple elements, wrap it first in another panel (HorizontalPanel or VerticalPanel), then add it to your “box panel”.
3. Don’t set any properties for this “box panel”, like border width or spacing.
4. Set the style of this “box panel” to “panelBox” and add this CSS element to your CSS file:

.panelBox {
padding: 3mm 3mm 3mm 3mm;
border: 1px;
border-color: #e0e0e0;
border-style: solid
}

To give you a quick example, say we are writing a data-entry form that contains various informations:

package com.erle.client.components;
import com.google.gwt.user.client.ui.Composite;
import com.google.gwt.user.client.ui.HTML;
import com.google.gwt.user.client.ui.HorizontalPanel;
import com.google.gwt.user.client.ui.RadioButton;
import com.google.gwt.user.client.ui.TextArea;
import com.google.gwt.user.client.ui.TextBox;
import com.google.gwt.user.client.ui.VerticalPanel;
public class PersonalInfoComposite extends Composite
{
private TextBox fname;
private TextBox mname;
private TextBox lname;
private RadioButton male;
private RadioButton female;
private TextArea currentAddress;
public PersonalInfoComposite()
{
HorizontalPanel boxPanel = new HorizontalPanel(); // This is the panel that will be the box
VerticalPanel userInterfacePanel = new VerticalPanel(); /* This will be the panel that will hold the user interface elements */
userInterfacePanel.setSpacing( 7 );
userInterfacePanel.add( new HTML("First Name") );
fname = new TextBox();
userInterfacePanel.add( fname );
userInterfacePanel.add( new HTML("Middle Name") );
mname = new TextBox();
userInterfacePanel.add( mname );
userInterfacePanel.add( new HTML("Surname Name") );
lname = new TextBox();
userInterfacePanel.add( lname );
userInterfacePanel.add( new HTML("Gender") );
male = new RadioButton("gender" , "Male");
female = new RadioButton( "gender" , "Female");
userInterfacePanel.add( male );
userInterfacePanel.add( female );
userInterfacePanel.add( new HTML("Current Address") );
currentAddress = new TextArea();
userInterfacePanel.add( currentAddress );
boxPanel.setStyleName( "panelBox" ); // Set the style to panelBox
boxPanel.add( userInterfacePanel ); // Make the box panel as the main widget of this composite.
initWidget( boxPanel );
}
}

Then, in your CSS file, just add the CSS snippet above, then add this composite to your application.

Some screenshot:

Forgive wordpress’s inability to clearly display source code.

Happy GWT hacking.

First off, a few days ago, I started experimenting with GWT, trying to fathom its mysteries, trying to make sense of this new (for me) technology that google has come up with.

The goal was simple:

• To learn how to develop a web user interface with this technology.
• To learn how to wire this web user interface to a backend engine.
• To learn how to style and add flavor to the application created with it.
• To know (like a sort of recipe) how to do the usual things I want to do when developing web applications.

So, off I go.

First thing I noticed was the minimal HTML and Javascript that I had to write. Wow, I’m writing the web user interface in Java. Ain’t that cool? You see, previously, when you sit down to write a web application, first thing you do is to open MS Frontpage or Dreamweaver ( or emacs/vi if your a hardcore ) and pump up a beautiful webpage using the wysiwyg tool they’ve got. It gets boring quickly when you realize that more than fifty percent of your time is spent trying to hunt down browser incompatibilities. Then you try adding server side scripts to your webpage to make it dynamic (true in PHP and JSP, don’t know with others), and spend some time wiring the user interface so that it connects with your backend. Painful.

So, what do you do in GWT (I hear you ask) ? First, you google the term “GWT”. Then you read the documentation that they have on their website. Then, after that initial hurdle of creating your first project, you start coding! in Java! Using Swing-style of developing user interfaces! The thing is, GWT has its own libraries of user interface elements called widgets, and you assemble your web application using these components. It is by no means complete, so, they give you the option of being able to create more components. Ask google how. The idea is, you might not be able to create an aesthetically pleasing web interface quickly, but you can easily add functionality as fast as you can think and type. You can easily prototype an idea, but not a design ( well, yes, you can, if you go with google’s default look and feel ). Good for programmers, bad for designers. Well, of course, you can always go by the “create the webpage and add the controls via ID” route but where’s the fun in that? By the way, you add flavor to your GWT application via CSS, so keep a Core CSS Reference handy.

So far, I’m immensely enjoying it.  But then again, I’m developing a webapp, not a website, and my taste for color is so bland you’d puke.

You Are a Seeker Soul

You are on a quest for knowledge and life challenges. You love to be curious and ask a ton of questions. Since you know so much, you make for an interesting conversationalist. Mentally alert, you can outwit almost anyone (and have fun doing it!).Very introspective, you can be silently critical of others. And your quiet nature makes it difficult for people to get to know you. You see yourself as a philosopher, and you take everything philosophically. Your main talent is expressing and communicating ideas.Souls you are most compatible with: Hunter Soul and Visionary Soul

What Kind of Soul Are You?

The song’s title is Hymne by Era.

Here’s a youtube link to the song and the “possible” lyrics …

http://www.youtube.com/watch?v=Uv4e8ox-kpg