1. User interface seems to be a big concern of most programmers. Some just need normal LookandFeel while others expect special appearance. Only a few methods are provided in the component classes. Some requirement could also be implemented through paint and drawing. For example, paint strings vertically, or, draw a textIcon under an imageIcon. However, [...]
Archive for the ‘Ideas, Topics, and Other Issues’ Category
Thinkings of Swing tutorial
Posted in Ideas, Topics, and Other Issues on January 18, 2010 | Leave a Comment »
Labeling Cases Using Six Barriers
Posted in DHou's Advices, Project todo's on January 16, 2010 | Leave a Comment »
List of FAQs
Posted in DHou's Advices, Project todo's on January 16, 2010 | Leave a Comment »
Compile a list of Frequently Asked Questions from the cases analyzed. This list should contain both how-to and how-not-to and answers to common/important why questions. Our goal is to demonstrate that such a list should become stable as more posts are analyzed.
Random Sampling
Posted in DHou's Advices, Ideas, Topics, and Other Issues, Project todo's on January 7, 2010 | Leave a Comment »
I am thinking of how to “randomly” select Button related questions. It seems that the following approach would work 1. search button related questions – search with keywords “button 57 Swing” and “button 257 Swing” 2. Manually, copy and paste the url’s into a file, one url per line. Say we collect 1000 such url’s. [...]
default solution breakdown
Posted in Ideas, Topics, and Other Issues on January 3, 2010 | 3 Comments »
Swing provides a various kinds of graphic user interface. While the function library is huge, Swing design provides several packages that can obviously simplify learning process. However, packages cannot guarantee all requirements from users and sometimes programmers have to look into Swing design details. Below are samples of such circumstance. Focus: Swing provides default color [...]
Meeting on Nov 28th
Posted in DHou's Advices, Ideas, Topics, and Other Issues on November 28, 2009 | Leave a Comment »
Thread length cannot reflect complexity of a certain subject due to some fuzzy factors(like user knowledge level, irrelevant conversation, and etc). Before quantify complexity, we should first discuss the most important cause in a table content. Finish all 70 pilot study before Jan and revise categories.
Nov 23rd meeting
Posted in DHou's Advices, Ideas, Topics, and Other Issues on November 23, 2009 | Leave a Comment »
Prediction of problem complexity should include: importance, table size, learnability and familarity (maybe popularity too). However, estimate of familarity and importance is a puzzle according to present knowledge. Comparison of problem complexity and average thread length seems more feasible.
Version Diff & Focus – 2nd
Posted in Ideas, Topics, and Other Issues, tagged Global on October 27, 2009 | 2 Comments »
Pilot Study: http://lilisworking.wordpress.com/2009/10/07/pilot-study-of-jbutton-button-specific/ Knowledge point: specific point: none; Global point: Java Version difference; Visible focus is necessary for most components;
Global Knowledge
Posted in Ideas, Topics, and Other Issues on October 26, 2009 | 6 Comments »
LayoutManager; Design Discussion, topics require have knowledge of interaction between components – Renderer & Editor, KeyBoard are typical samples; focus; paint; UInterface; Version/OS difference; event handling thread;
Topic
Posted in Ideas, Topics, and Other Issues on October 23, 2009 | 1 Comment »
paper idea： When programmers start leaning a new tool, which part of knowledge is most necessary? In general, majority and most important part is the Frame knowledge. How much is the percentage of each widget’s specific knowledge in Swing? And most of the rest are the Software’s architecture knowledge? Take JButton, JDialog and JTree as [...]
