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

          

          
	
          
		
          
			
 
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 閱讀(337) 評論(0)  編輯  收藏  所屬分類: swing 
	
          

          







          
	    
    




          








          

				

          




    







          
        
	




主站蜘蛛池模板：
怀化市|
财经|
民乐县|
娄烦县|
轮台县|
团风县|
夏津县|
留坝县|
滨州市|
桦甸市|
双柏县|
荣成市|
宜城市|
宿松县|
佛山市|
元阳县|
岗巴县|
两当县|
靖宇县|
辉县市|
新乡市|
彰武县|
曲阳县|
长阳|
景宁|
南投县|
蓬溪县|
洪江市|
视频|
凤冈县|
天台县|
满洲里市|
江孜县|
颍上县|
永新县|
文山县|
定襄县|
河南省|
江孜县|
纳雍县|
常山县|