使用Sencha Touch中的图像处理不同的分辨率触摸设备(Working with images in Sencha Touch for different Resolution Touch Device)

 在Log4j 2初始化期间，配置中的所有插件都将被处理并存储在Node对象中。 实现Node.toString（）方法，如果原始Plugin的printObject属性为true，则Node.toString（）将委托给Plugin的toString（）方法。 否则，它返回一个包含插件类和插件名称的String。 
 
 所以一般来说，提供一个好的toString（）方法并将printObject声明为true是明智的。 另一方面，如果你错过了它也不是灾难：这主要是为了调试。 因此，如果printObject为true但您没有覆盖toString（），那么所有发生的事情都是在调试插件时您将看不到有用的值。 
 
 Log4j 2在DEBUG / TRACE级别向StatusLogger记录初始化过程的详细信息。 如果您的配置以<Configuration status="trace">开头，则可以看到此信息。 
 
 自定义插件可以使用printObject属性来影响在配置期间记录到StatusLogger日志记录的内容。 可以肯定的是，在初始化之后，在调试生成的Node值时显示插件的toString（）值很有用。 

During Log4j 2 initialization, all plugins in the configuration are processed and stored in Node objects. The Node.toString() method is implemented such that if the original Plugin's printObject attribute was true, Node.toString() will delegate to the Plugin's toString() method. Otherwise, it returns a String containing the plugin class and the plugin name.
 
So in general it is wise to provide a good toString() method and declare printObject to be true. On the other hand, it is not a disaster if you miss either: this is mostly for debugging. So, if printObject is true but you don't override toString(), all that happens is that when debugging your plugin you won't see useful values. 
 
Log4j 2 logs details of the initialization process to the StatusLogger at DEBUG/TRACE level. You can see this information if your configuration starts with <Configuration status="trace">.
 
It is possible that custom plugins can use the printObject attribute to influence what is logged to the StatusLogger logging during configuration. What is certain is that after initialization, it is useful to have your Plugin's toString() value shown when debugging the resulting Node values.