Skip to main content
summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat (limited to 'Article-Progress-Monitors/about.xml')
-rw-r--r--Article-Progress-Monitors/about.xml24
1 files changed, 24 insertions, 0 deletions
diff --git a/Article-Progress-Monitors/about.xml b/Article-Progress-Monitors/about.xml
new file mode 100644
index 0000000..91e7369
--- /dev/null
+++ b/Article-Progress-Monitors/about.xml
@@ -0,0 +1,24 @@
+<article link="article.html" show="false">
+ <title>How to Correctly and Uniformly Use Progress Monitors</title>
+ <date>January 3, 2006</date>
+ <category>platform</category>
+ <category>general</category>
+ <author>
+ <name>
+ <![CDATA[Kenneth &Ouml;lwing]]>
+ </name>
+ <company>BEA JRPG</company>
+ </author>
+ <description>
+ Handling a progress monitor instance is deceptively simple. It
+ seems to be straightforward but it is easy to make a mistake
+ when using them. And, depending on numerous factors such as the
+ underlying implementation, how it is displayed, the result can
+ range from completely ok, mildly confusing or outright
+ silliness. In this article we lay down a few ground rules that
+ will help anyone use progress monitors in a way that will work
+ with the explicit and implicit contract of IProgressMonitor.
+ Also, understanding the usage side makes it easier to understand
+ how to implement a monitor.
+ </description>
+</article> \ No newline at end of file

Back to the top