In this here second part of the "Timestamped" series, we introduce its namesake Timestamped interface, and use a Deque from Java6 to collect such things, and impose a time-based capacity for that.
We herewith begin a saga about monitoring with this series entitled "Timestamped: a trilogy in a few parts," this being the first part, where we introduce a map to count key things, and ensure we can order it by its integer values.
I enjoyed reading the Android=Java blog just now, and agree with Osvaldo's sentiments.
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.
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.
Having blogged this hack some years ago (Event Pump DTs), today i actually used it.
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.
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.
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.