This section introduces you to the Genero Web Client (GWC). The GWC is included as part of the GAS, starting with GAS 2.11.
The Genero Web Client (GWC), you can deliver true Web applications from those applications developed in the Genero Business Development Language (BDL). Having the underlying source written in Genero BDL means that the GWC is flexible enough to let you build a simple Web application to a corporate Web application, with only a few limitations. It brings to BDL applications the Internet world and the ability to be integrated in a Web site. It renders the application using technologies understood by a browser using well-known Web technologies like xHTML, XSLT, CSS and JavaScript. As a result, it can deliver the application to any device equipped with a Web browser.
Why deliver an application as a Web application?
The GWC uses templates and snippet sets, written using a Genero "template language" in addition to other Web-based languages (xHTML, XSLT, JavaScript) to create dynamic web pages. Different snippet sets are provided to allow the dynamic web pages to be created using the language appropriate for the client browser. The AJAX theme snippet set is aimed at desktop browsers, while the PDA theme snippet set is aimed at handheld devices.
Starting with GWC 2.10, a snippet-based rendering engine replaces the legacy built-in rendering engine. This new rendering engine provides you with complete control of the customization of the user interface components, and removes many of the limitations imposed by the legacy rendering engine.
Four J's will continue to provide the legacy built-in rendering engine for those GWC deployments that are already in place, however it will no longer be enhanced. If you do not wish to migrate your application to use the snippet-based rendering engine, you can configure your applications to run in the legacy mode. The documentation in this guide is primarily for those applications that use the snippet-based rendering engine. For documentation covering the legacy built-in rendering engine, refer to the GWC 2.00 manual available on the Four J's Web site (http://www.4js.com).
When working with applications deployed in a Web environment, you will likely need to identify or add team members who are proficient in various Web technologies. Many of these technologies will be unfamiliar to your traditional Genero BDL application developer.
The key players involved in developing Web-based applications are listed by area:
| Area | Player Responsibility |
| Application Design | Responsible for the rendering aspects of the application within GWC by adding and modifying templates and CSS to influence the look-and-feel of the application. Members of this team should be proficient with HTML and CSS. |
| Application Development | Responsible for the development of the Genero application, concentrating on the business logic. Members of this team should be proficient with Genero Business Development Language. |
| Advanced Production | Responsible for the additional functionality and navigation added to an application through the use of the template language to link BDL form objects and JavaScript to define the behavior. Members of this team should be proficient with HTML and JavaScript. |
| Deployment and Infrastructure | Responsible for the complete GWC solution from a component perspective: the installation and configuration of the application server and Web server; the communication between the user agent, Web server, application server, DVM, and database server. Members of this team should be proficient in working on the different platforms and operating systems where the application will reside and proficient in administration of the Web server. |
It is rare that a single person fulfills the requirements demanded in each of these areas.
Having some knowledge of Web technologies like HTML, XML, style sheets and JavaScript ease GWC understanding. You can find Web standards at http://www.w3.org. Take a look at http://www.w3schools.com tutorials to get a quick start.
For the most part, a Genero application reacts the same across the different Front End clients (GWC, GDC, and so on). There are, however, limitations for applications being rendered by the GWC 2.10 snippet-based rendering engine:
The GWC will recognize the first accelerator defined for an action (acceleratorName). It will not recognize those accelerators defined by acceleratorName2, acceleratorName3, or acceleratorName4.
You can set the accelarator key combination to any combination you wish. There are, however, a set of keys that you should avoid using, as there may be unintended side effects. This set includes: