Zestaw szablonów Clarion/ASP generuje aplikacje Active Server Pages (ASP) wyposażone w procedury tworzenia zapytań, przeglądania i aktualizowania danych dla aplikacji typu klient/serwer działających w sieci Internet. Dzięki tym szablonom znacznie zwiększa się wydajność pracy nad bazodanowym serwisem WWW, poprzez translację rozwiązań sprawdzonych na biznesowych aplikacjach desktopowych. Co więcej, wygenerowane strony ASP w łatwy sposób integruje się z już istniejącymi serwisami WWW zarówno pod względem wizualnym, jak i logicznym (powiązanie stron).
Wyprodukowany kod zawiera dodatkowo funkcjonalność niezbędną przy budowie publicznych, często odwiedzanych serwisów. Należy do tego m.in. ograniczenie dostępu do tylko tych danych, do których użytkownik ma uprawnienia.
Aplikacja, którą otrzymujemy w wyniku zastosowania szablonów Clarion/ASP jest wysoce niezawodna, skalowalna i zawiera rozbudowaną obsługę błędów.
Watch a video of an unedited "generated" Clarion/ASP application here.
How quickly can you build and deploy a Clarion/ASP application, and how much do you need to know about ASP? Learn the answers in less than four minutes, click on the Video Demo 1 link on the right to download the video to your system.
What can you do with just a little customization? Here's what you can do with a product that completely separates the user interface from the application logic. Approximately five minutes, click on the Video Demo 2 link on the right to download the video to your system.
There are three important things that Clarion developers should know about the Clarion/ASP development paradigm:
By providing a system relying on runtime HTML templates and style sheets for the browser client layout, Clarion/ASP completely separates the User Interface from the Application and Business logic. This means the developer is free to concentrate on the application, and the web designer can make the page fit into the existing web design via HTML formatting and style sheets. Either side can make changes without affecting the other, yet not lose them at generation time.
The code generation system itself is template driven (of course). The developer doesn’t have to know anything about ASP, VBScript, ADO, HTML design, or Cascading Style Sheets to produce a fully functional, fully customized application. As the first SoftVelocity Clarion add-in to produce non-Clarion applications, this is a transition point to a time in which Clarion developers will take their data dictionaries and decide what language to generate by deciding what target they wish to deploy to.
The system is completely extensible, via embed points. In this case, however, your embeds must consist of VBScript and/or ADO/SQL statements. The system, as is, is very complete, but as always, Clarion provides unlimited options for the developer. (Note: if maintaining both desktop and ASP targets in a single app, ASP generation ignores the Clarion embed code, and Windows OS generation ignores the ASP embed code).
The Clarion/ASP templates produce complete working routines to perform all specified tasks; no additional custom code is necessary to utilize them.
In addition to the many resources available, SoftVelocity offers professional services, technical support, and educational courses that cover multiple levels of materials.
No, an emphasis was placed on separating the business logic / data access from the user interface. The result is a run-time HTML template that contains “tokens” that are replaced at runtime with the corresponding data values. In addition 99% of the formatting, fonts, colors, sizes etc; are controlled by a generated Cascading Style Sheet. The starting HTML design-time template can be specified by you globally and on a procedure basis, this permits mass generation of a particular look and feel with the minimum amount of effort. These HTML templates can be modified in most WYSIWYG editors.
No, the generated applications can be deployed to work standalone or within a frameset, your choice. How is data validation performed? There are several levels of validation: 1 - Each HTML input field receives JavaScript validation attributes which are constructed from your Data Dictionary and selections made in the Clarion/ASP templates interface. 2 - The Clarion/ASP “Processor Page” which receives a submitted HTML form also contains validation rules built from the Data Dictionary and selections made in the Clarion/ASP templates interface. Both of these tests are applied prior to any database updates. 3 – The final validation tests are the constraints and rules that have been defined at the column level in the database by the DBA.
The Clarion/ASP templates are intended to generate industry standard HTML and work on the broadest number of client web browsers. As a result there are overall architecture constraints; which the generated code must work within. Even so we have introduced a number of features that recreate a number of “desktop” like functions like a pop-up calendar, must-be-in-list and must-be-in-file select controls (dropdowns), pop-up help screens, and pop-up select procedures which can return multiple column values.
Yes, by using the correct HTML include statement in your HTML design-time template you have access to your existing library.
Yes, you have two options. 1 – You can use the appropriate EMBED point within the IDE to enter your own code which will be preserved on subsequent generations. 2 – You can modify the generated ASP code, which will not be preserved on subsequent generations.
Yes, you have the option with the Clarion/ASP templates to suppress generation of the HTML and CSS files globally or on a procedure basis. Additionally you can merely choose not to deploy them once generated.
We implement every option and attribute possible given the architecture. There are some differences such as picture formatting. On a column basis we allow you to select from a standard list of VBScript format functions and options such as FormatDateTime(), FormatCurrency(); which include regional locale settings.