Changes for page Java Client-Overview
                  Last modified by Lazy Lazarus on 2025/03/27 10:23
              
      
      From version  16.1 
    
    
              edited by David Avendasora
        
on 2008/07/16 10:13
     on 2008/07/16 10:13
      Change comment:
              There is no comment for this version
          
         
      To version  17.1 
    
    
              edited by David Avendasora
        
on 2008/07/16 10:13
     on 2008/07/16 10:13
      Change comment:
              There is no comment for this version
          
         Summary
- 
          Page properties (2 modified, 0 added, 0 removed)
 - 
          Attachments (0 modified, 1 added, 0 removed)
 
Details
- Page properties
 - 
      
- Parent
 -   
... ... @@ -1,0 +1,1 @@ 1 +Java Client  - Content
 -   
... ... @@ -6,14 +6,14 @@ 6 6 1. Java Client using Interface Builder to create NIB files that define the UI 7 7 1. Java Client using pure Swing 8 8 9 -The first two types used other files (XML/NIB files) to build the Swing code during run-time. This can make for quick development times requiring very little Java programming. 9 +The first two types used other files (XML/NIB files) to build the Swing code during run-time. This can make for quick development times requiring very little Java programming. 10 10 11 11 D2JC is very flexible with the UI generated almost entirely at runtime by text-based configuration files (the same rules-system used by Direct to Web). This allows the developer to go from Database or Model to a native-UI application in just minutes. Major changes to the underlying database/EOModel can often-times be reflected in the UI with little or no Java programming or refactoring at all. 12 12 13 -NIB-Based development used Project Builder/Xcode's Interface Builder application to create cocoa-based NIB files that were then interpreted at run-time using the Cocoa-Java Bridge to create a pure Swing application. NIB-based development has been deprecated due to the deprecation of the tools required for development and the Cocoa-Java Bridge. 13 +NIB-Based development used Project Builder/Xcode's Interface Builder application to create cocoa-based NIB files that were then interpreted at run-time using the Cocoa-Java Bridge to create a pure Swing application. NIB-based development has been deprecated due to the deprecation of the tools required for development and the Cocoa-Java Bridge. 14 14 15 -Swing-based Java Client Development has recently gotten much simpler with the release of Florijan Stamenkovic's [[javaBound (JBND) framework>>http://web.mac.com/flor385/JBND/]] which greatly streamlines many key pieces of native-client application development. 15 +Swing-based Java Client Development has recently gotten much simpler with the release of Florijan Stamenkovic's [[javaBound (JBND) framework>>url:http://web.mac.com/flor385/JBND/||shape="rect"]] which greatly streamlines many key pieces of native-client application development. 16 16 17 17 While there are not a lot of WebObjects Java Client projects when compared to the quantity of Web-Based projects, it seems to be getting more attention now than it has in several years. 18 18 19 -There are a couple third-party developers working on solutions to streamline the development of pure Swing/SWT/etc Java Client applications for Web Objects. See [[Complimentary Frameworks>>Java Client-Complimentary Frameworks]] 19 +There are a couple third-party developers working on solutions to streamline the development of pure Swing/SWT/etc Java Client applications for Web Objects. See [[Complimentary Frameworks>>doc:Java Client-Complimentary Frameworks]]  
 
- WebObjects Desktop Applications.pdf
 -   
- Author
 -   
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest  - Size
 -   
... ... @@ -1,0 +1,1 @@ 1 +8.4 MB  - Content