Skip to main content

Java: Create message with MessageFormat class


Creating a message string is very easy, but creating it with more effective way that's matter. Most of time when we write the code for message string, we use "+" operator on string. But it become complex when we have to deal with lots of pieces of string.

It can be worse when we have to deal with number, date and currency type data with locale setting.

Below are few test data which use common way of creating the message string.

DateFormat df = DateFormat.getDateInstance(DateFormat.DEFAULT);
DateFormat tf = DateFormat.getTimeInstance(DateFormat.DEFAULT);
Date today = new Date();
String text = "Work";
int num = 7;
 
String meesage1 = "Time= " + tf.format(today) +
   ", Date= " + df.format(today) +
   ", Text= " + text +
   ", Number= " + num + ".";
System.out.println(meesage1);
   
String message2 = new StringBuffer("Time= ").append(tf.format(today))
  .append(", Date= ").append(df.format(today))
  .append(", Text= ").append(text)
  .append(", Number= ").append(num)
  .append(".").toString();
System.out.println(message2);
   

Output:->
Time= 11:41:17 AM, Date= Dec 3, 2011, Text= Work, Number= 7.
Time= 11:41:17 AM, Date= Dec 3, 2011, Text= Work, Number= 7.


And here is the more easy way of creating the string message. (after using the MessageFormat class)

Date today = new Date();
String text = "Work";
int num = 7;

String message3 = MessageFormat.format(
     "Time= {1,time}, Date= {1,date}, Text= {2}, Number= {0,number,integer}.",
     num, today, text);
System.out.println(message3);

Output:->
Time= 11:41:17 AM, Date= Dec 3, 2011, Text= Work, Number= 7.


Some more details form java doc

Format Element
{ ArgumentIndex , [FormatType] , [FormatStyle] }

FormatType:
number | date | time | choice


FormatStyle:
short
medium
long
full
integer
currency
percent
SubformatPattern


Format TypeFormat StyleSubformat Created
(none)(none)null
number(none)NumberFormat.getInstance(getLocale())
integerNumberFormat.getIntegerInstance(getLocale())
currencyNumberFormat.getCurrencyInstance(getLocale())
percentNumberFormat.getPercentInstance(getLocale())
SubformatPatternnew DecimalFormat(subformatPattern, DecimalFormatSymbols.getInstance(getLocale()))
date(none)DateFormat.getDateInstance(DateFormat.DEFAULT, getLocale())
shortDateFormat.getDateInstance(DateFormat.SHORT, getLocale())
mediumDateFormat.getDateInstance(DateFormat.DEFAULT, getLocale())
longDateFormat.getDateInstance(DateFormat.LONG, getLocale())
fullDateFormat.getDateInstance(DateFormat.FULL, getLocale())
SubformatPatternnew SimpleDateFormat(subformatPattern, getLocale())
time(none)DateFormat.getTimeInstance(DateFormat.DEFAULT, getLocale())
shortDateFormat.getTimeInstance(DateFormat.SHORT, getLocale())
mediumDateFormat.getTimeInstance(DateFormat.DEFAULT, getLocale())
longDateFormat.getTimeInstance(DateFormat.LONG, getLocale())
fullDateFormat.getTimeInstance(DateFormat.FULL, getLocale())
SubformatPatternnew SimpleDateFormat(subformatPattern, getLocale())
choiceSubformatPatternnew ChoiceFormat(subformatPattern)

Comments

Popular posts from this blog

ERROR: Ignored call to 'alert()'. The document is sandboxed, and the 'allow-modals' keyword is not set.

Recently I found this issue while writing code snippet in "JSFiddle". And after searching, found this was happening because of new feature added in "Chrome 46+". But at the same time Chrome doesn't have support for "allow-modals" property in "sandbox" attribute.

Chromium issue for above behavior:
https://codereview.chromium.org/1126253007

To make it work you have to add "allow-scripts allow-modals" in "sandbox" attribute, and use "window.alert" instead of "alert".



<!-- Sandbox frame will execute javascript and show modal dialogs --> <iframe sandbox="allow-scripts allow-modals" src="iframe.html"> </iframe>


Feature added: Block modal dialog inside a sandboxed iframe.
Link: https://www.chromestatus.com/feature/4747009953103872

Feature working Demo page:
https://googlechrome.github.io/samples/block-modal-dialogs-sandboxed-iframe/index.html



JavaScript [ExtJs3]: EditorGridPanel Read-Only (dynamically)

Many time we face the scenerio where we have to make the editor grid read-only dynamically.


Ext.override(Ext.ux.grid.CheckColumn, { editable: true, onMouseDown: function (e, t) { if (Ext.fly(t).hasClass(this.createId())) { e.stopEvent(); var me = this, grid = me.grid, view = grid.getView(), index = view.findRowIndex(t), colindex = view.findCellIndex(t), record = grid.store.getAt(index); if (!grid.isReadOnly && grid.colModel.isCellEditable(colindex, index)) { record.set(me.dataIndex, !record.data[me.dataIndex]); } } } }); var grid = new Ext.grid.EditorGridPanel({ ... isReadOnly: true, //set to flag to make check column readonly ... }); //to make other column readonly grid.on('beforeedit', function () { return false; });

CSS Specificity

Many time different CSS rules overlap on one or more element. And some people always get confuse about, which rule will take higher priority then other and why? CSS Specificity is the answer of all these kind of questions.
As the name suggest, the CSS rule which is more specific to the element will take higher priority then other. Means something like “#some_id{}” will always take higher priority then “*{}” universal selector.  And if duplicate rules are define then the last rule will be applied to the element.

The following list of selectors is by increasing specificity:
Type selector (e.g., div) and pseudo-elements in selector (e.g., :after) Class selectors (e.g., .some_class), attributes selectors (e.g., [type=”radio”]) and pseudo-class selector (e.g., :hover) Id selectors (e.g., #some_id)


ID takes higher priority then Class, Type and Universal selector (Note: Universal selector has no effect on specificity, see below special conditions). 



If duplicate rules are given, then last…