Contents - Cultural View
Contents - Cultural View Contents - Cultural View
Plain Old Java Object 252 An open source framework that auto-creates an object-oriented user interface from POJOs using the naked objects pattern. Metawidget [15] A 'smart User Interface widget' that populates itself, at runtime, with UI components to match the properties of POJOs. fbDaoGenerator [16] Fbdaogenerator connects to a Firebird Database, reads the metadata of the Database by querying the system-tables, and generates POJOs and Data Access Objects. Pojo Testing Projects • OpenPojo [17] a pluggable testing framework See also • Data Transfer Object • Anemic Domain Model References [1] MF Bliki: POJO (http:/ / www. martinfowler. com/ bliki/ POJO. html) from MartinFowler.com [2] http:/ / prevayler. org [3] https:/ / sourceforge. net/ projects/ beanexaminer [4] http:/ / www. romaframework. org [5] http:/ / sourceforge. net/ projects/ openxava [6] http:/ / sourceforge. net/ projects/ plainxml [7] http:/ / sourceforge. net/ projects/ patsystem [8] http:/ / sourceforge. net/ projects/ jor [9] http:/ / sourceforge. net/ projects/ auto-persist-j [10] http:/ / sourceforge. net/ projects/ pojogen [11] http:/ / sourceforge. net/ projects/ pojodbc [12] http:/ / cwiki. apache. org/ FELIX/ ipojo. html [13] http:/ / labs. jboss. com/ jbossmc/ [14] http:/ / www. nakedobjects. org/ home/ index. shtml [15] http:/ / www. metawidget. org [16] http:/ / code. google. com/ p/ fbdaogenerator [17] http:/ / code. google. com/ p/ openpojo
Pluggable look and feel 253 Pluggable look and feel Pluggable look and feel is a mechanism used in the Java Swing widget toolkit allowing to change the look and feel of the graphical user interface at runtime. Swing allows an application to specialize the look and feel of widgets, by modifying the default (via runtime parameters), deriving from an existing one, by creating one from scratch, or, beginning with J2SE 5.0, by using the skinnable synth look and feel, which is configured with an XML property file. The look and feel can be changed at runtime. Architecture The corresponding API includes: • Hooks in Swing widgets to interact with their look and feel. Each widget defined in Swing can delegate its "painting" to its associated user interface classes called UI delegates. • An API to manage existing look and feel definitions. This API allow to set the look and feel or switch from look and feels at runtime. • Another API to define a specific look and feel, or derive a look and feel from an existing one. Examples of look and feels Platform look and feels The Java platform comes with several bundled look and feels [1] : • A default cross-platform look and feel, called Metal (see MetalLookAndFeel). This look and feel comes with several themes: • The DefaultMetalTheme, which was historically the first Swing default theme. • The smoother OceanTheme, which became the default theme for Java 5.0. • Other cross-platform look and feels: • A skinnable look and feel called synth (see synth), which is configured with an XML property file. • The Nimbus look and feel (based on synth), which is added for the Java SE 6 Update 10 [2] [3] . • Platform dependent look and feels [4] : Look and feels that aim to be the closest as possible to the platform native GUI. The fidelity to the native look and feel theming has been improved in recent Java versions by leveraging the [5] [6] platform native GUI theming library when possible • A Windows look and feel (this look and feel depends on the version of the Windows Operating System), • A Motif or GTK+ (for newer distributions) look and feel on Linux or Solaris, • A specific vendor look and feel for IBM AIX, HP-UX, and Mac OS X.
- Page 205 and 206: JavaBeans Activation Framework 201
- Page 207 and 208: javac 203 References [1] http:/ / j
- Page 209 and 210: JavaFX 205 profile includes Swing a
- Page 211 and 212: JavaFX 207 External links • Offic
- Page 213 and 214: JExamples 209 JExamples Industry Co
- Page 215 and 216: Jikes 211 Jikes Developer(s) IBM St
- Page 217 and 218: Michael Kölling 213 Microsoft Pate
- Page 219 and 220: List of Java keywords 215 case catc
- Page 221 and 222: List of Java keywords 217 long nati
- Page 223 and 224: List of Java keywords 219 Reserved
- Page 225 and 226: Name mangling 221 Name mangling In
- Page 227 and 228: Name mangling 223 } }; }; /* = _ZN9
- Page 229 and 230: Name mangling 225 if (__1cGstrcmp6F
- Page 231 and 232: Name mangling 227 ['_Test__private_
- Page 233 and 234: Name mangling 229 External links
- Page 235 and 236: Patrick Naughton 231 See also • H
- Page 237 and 238: New I/O 233 FileChannel can be used
- Page 239 and 240: New I/O 235 // Pattern used to pars
- Page 241 and 242: New I/O 237 References [1] "JSR 51:
- Page 243 and 244: Omniscient Debugger 239 Omniscient
- Page 245 and 246: OpenJDK 241 Inclusion in software d
- Page 247 and 248: OpenJDK 243 [12] "Open JDK is here!
- Page 249 and 250: PHP/Java Bridge 245 References [1]
- Page 251 and 252: Java package 247 External links jav
- Page 253 and 254: Parboiled (Java) 249 } } return seq
- Page 255: Plain Old Java Object 251 POJO gene
- Page 259 and 260: Primitive wrapper class 255 Primiti
- Page 261 and 262: Quark Framework 257 Quark Framework
- Page 263 and 264: Quark Framework 259 has proven to p
- Page 265 and 266: Quark Framework 261 //illustrates p
- Page 267 and 268: Quark Framework 263 As well as LECC
- Page 269 and 270: Quark Framework 265 `catch` (\ex ->
- Page 271 and 272: REPLAY (software) 267 Qualities REP
- Page 273 and 274: Real time Java 269 References [1] J
- Page 275 and 276: Restlet 271 Connectors The list of
- Page 277 and 278: SLAMD 273 SLAMD The SLAMD Distribut
- Page 279 and 280: SLAMD Server 275 SLAMD Server A SLA
- Page 281 and 282: Bruno Souza 277 Bruno Souza Born Na
- Page 283 and 284: Static import 279 References [1] Ja
- Page 285 and 286: strictfp 281 Behaviors and restrict
- Page 287 and 288: Sun Web Developer Pack 283 Sun Web
- Page 289 and 290: Swing (Java) 285 The Swing Architec
- Page 291 and 292: Swing (Java) 287 Relationship to AW
- Page 293 and 294: Swing (Java) 289 } window } See als
- Page 295 and 296: SwingLabs 291 • JDNC [7] : Contai
- Page 297 and 298: Synth Look and Feel 293 Supposing t
- Page 299 and 300: TeachScheme! 295 • a function def
- Page 301 and 302: TeachScheme! 297 TeachScheme! and B
- Page 303 and 304: Unified Expression Language 299 Imp
- Page 305 and 306: Java Virtual Machine 301 Bytecode v
Pluggable look and feel 253<br />
Pluggable look and feel<br />
Pluggable look and feel is a mechanism used in the Java Swing widget toolkit allowing to change the look and feel<br />
of the graphical user interface at runtime.<br />
Swing allows an application to specialize the look and feel of widgets, by modifying the default (via runtime<br />
parameters), deriving from an existing one, by creating one from scratch, or, beginning with J2SE 5.0, by using the<br />
skinnable synth look and feel, which is configured with an XML property file. The look and feel can be changed at<br />
runtime.<br />
Architecture<br />
The corresponding API includes:<br />
• Hooks in Swing widgets to interact with their look and feel. Each widget defined in Swing can delegate its<br />
"painting" to its associated user interface classes called UI delegates.<br />
• An API to manage existing look and feel definitions. This API allow to set the look and feel or switch from look<br />
and feels at runtime.<br />
• Another API to define a specific look and feel, or derive a look and feel from an existing one.<br />
Examples of look and feels<br />
Platform look and feels<br />
The Java platform comes with several bundled look and feels [1] :<br />
• A default cross-platform look and feel, called Metal (see MetalLookAndFeel). This look and feel comes with<br />
several themes:<br />
• The DefaultMetalTheme, which was historically the first Swing default theme.<br />
• The smoother OceanTheme, which became the default theme for Java 5.0.<br />
• Other cross-platform look and feels:<br />
• A skinnable look and feel called synth (see synth), which is configured with an XML property file.<br />
• The Nimbus look and feel (based on synth), which is added for the Java SE 6 Update 10 [2] [3] .<br />
• Platform dependent look and feels [4] : Look and feels that aim to be the closest as possible to the platform native<br />
GUI. The fidelity to the native look and feel theming has been improved in recent Java versions by leveraging the<br />
[5] [6]<br />
platform native GUI theming library when possible<br />
• A Windows look and feel (this look and feel depends on the version of the Windows Operating System),<br />
• A Motif or GTK+ (for newer distributions) look and feel on Linux or Solaris,<br />
• A specific vendor look and feel for IBM AIX, HP-UX, and Mac OS X.
Change language