evanx's blog

The Prodigal Android

I enjoyed reading the Android=Java blog just now, and agree with Osvaldo's sentiments.

Betwixt the Brackets

So we need to convert objects into XML and back again, eg. to store some data in the database in XML format, because otherwise maybe we just gonna have too many tables and joins and what-not.

Trivial Templating

Notwithstanding the fact that anyone in their right mind (which rules me out) would use Apache Velocity or FreeMarker for templating, we present a trivial templating helper class, where for instance we have an HTML template as follows to send a confirmation email to a customer.

Swing Event Pump Redux

Having blogged this hack some years ago (Event Pump DTs), today i actually used it.

Automatic Binding

In the Gooey MvnC prequel, we advocate an MVC-type architecture for programming a Swing UI panel, using convention-over-configuration to automate event handling, thread switching and beans binding.

On Computers, God, the Universe and UI

We gonna consider the definition and evolution of computer UI. But first, what is a computer? It's a number crunching machine that interfaces to a human being, innit. Actually, "data crud'ing" is probably a better depiction than "number crunching" in the world of business information systems.

An idea for a builder thingymajig

Let's say we have a following class with Swing components.

public class PersonEditor {
    JPanel mainPanel;
    JTextField firstname;
    JTextField surname;
    JFormattedTextField dateOfBirth;
    ...
    public     
  
  

Gooey Event Proxy

In the Gooey MvnC prequel, we consider an MVC-type separation for programming a Swing UI panel, and convention-over-configuration to automate events, threading and beans binding.

A short history of Web UI programming

Web 1.0, XUL, Ajax, Laszlo, Flex and Silverlight have a common approach - declare the UI view using markup (HTML or XML), and use JavaScript to handle the UI events and manipulate the UI. JavaFX/Swing is a notable exception - which is exciting and/or risky?!

MVnC architecture for Swing GUIs

Rather than put our "application logic" in a "messy" view class, we create a separate "controller" class, with event handlers.

We wish this controller class to be as neat and tidy as possible eg. with minimal boilerplate or much else besides our application logic.