有才華的人，別忘記給滋潤你的那塊土壤施肥
          
				
          
			          		
		
          
	
          

          

          
	
          
		
          
			
 
BlogJava ::
首頁 ::
新隨筆 ::
聯系 ::
聚合
 ::
管理 ::


			
			
				

          
	
          
		
          
			
			
			
				 
				28 
				隨筆 ::
				5 文章
				::
				147 評論
				::
				0 Trackbacks
			
		
          
	
          

          

			          		
		
          
	
          

          


          


          
	
					

          
	
	
	
          
		
           
          

        1. You know your target domain or business logic, so that you are able to design expressive and concise domain objects. 
          

          

        2. You are thinking in "swing models", not the UI-components. If you understand your domain, you probably have an idea as well how to visualize the business concepts in object oriented way. The use of Swing models just becomes natural.
          

          

        3. You are starting with the domain objects covered with unit tests, then develop the Swing models - after that the work is almost complete. You "only" have to create the view and pass the model to it. 
          

          

        4. You are NOT trying to work with the views directly and force them to behave in your way. This could become quite complex, cumbersome and very hard to maintain. E.g. if you are working with the JTable directly, instead of TableModel, even reordering the table columns can cause you some headaches. The are no issues with a custom model in this case. 
          

          

        5. The use of TableCellRenderers and TableCellEditors in JTables helps you to visualize you domain objects directly - without any overhead. 
          

          

        6. You are using visual designers like e.g. Matisse in pragmatic way and separate the generated, from your code. 
          

          

        7. You have a clear concept how to bind (e.g. with reflection+annotations or JSR-295) the UI-components to domain objects and how and where to validate the input (e.g. in controllers, domain objects or converters). 
          

          

        8. Try to leverage existing JavaBean patterns like PropertyChangeListener, PropertyChangeSupport and the already built-in listeners in the UI-components. There is lot of stuff which can be reused.
          

          

        9. If you spend more than half hour to solve a specific "Swing-problem", just stop hacking and use google to find a solution for your problem. There are amazingly good tutorials, articles and posts out there. 
          

          

        10. If you lose your motivation. Just stop developing Swing, build a quick prototype with SWT/JFace for few hours (but use Tables and Trees). Your motivation should increase dramatically after this experiment :-)
          11. 

           
          

          From: Adam Bien's Weblog
          

	
          
	
	
          
		posted on 2008-11-27 11:57 kissjava 閱讀(333) 評論(0)  編輯  收藏  所屬分類: swing 
	
          

          







          
	    
    




          








          

				

          




    







          
        
	




主站蜘蛛池模板：
东兰县|
婺源县|
新郑市|
明光市|
城口县|
巴彦县|
克山县|
隆尧县|
出国|
泸溪县|
巴彦淖尔市|
青阳县|
图木舒克市|
昭觉县|
临猗县|
阿坝县|
徐水县|
来凤县|
紫云|
吴江市|
百色市|
洛川县|
东宁县|
宜丰县|
安龙县|
亚东县|
秦皇岛市|
梅河口市|
黎川县|
闽侯县|
五莲县|
三门县|
即墨市|
讷河市|
达拉特旗|
桐庐县|
伽师县|
白河县|
平舆县|
和顺县|
湾仔区|