These examples have pointed to the idea that we can create at least a trivial application by hooking beans together in a mostly visual way. In other development environments, this kind of bean hookup has been pushed even further. For example, Sun’s original “BeanBox” experimental Java bean container took a different approach than NetBeans. It allowed the developer to work with “live” Java bean instances, dynamically generating adapter code at runtime and relying solely on object serialization to save the resulting work. This kind of design is, in a sense, the real goal of the JavaBeans architecture. It is true “what you see is what you get” (WYSIWYG) programming. However, pure visual design without the ability to integrate handwritten code, as we can do in NetBeans, has not yet proven to scale beyond these kinds of simple applications, and pure visual programming environments beyond just GUI screen layout have thus far failed to catch on.
Get Learning Java, 4th Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
