Windows Vista Support
dbQwikSite runs under Windows Vista. In this release we offer our first official support for Windows Vista. We have tested all core features, in design and PC testing and we now support all core functions on Vista.
HTML Editor Integration
dbQwikSite now supports working with your favorite HTML editor. HTML pages and embedded HTML fragments (such as page header and footers) can now be open in your preferred HTML editor from within dbQwikSite, replacing dbQwikSite's the internal HTML Editor. Changes made in your HTML editor are seamlessly incorporated back into dbQwikSite when you end your HTML edit session. dbQwikSite also tracks all your HTML files and advises you of any inconsistencies between dbQwikSite's information and the external files. This means that you can work in your HTML editor and when you start dbQwikSite, it will flag any pages that have been updated since your last dbQwikSite session.
Web Form Converter
Convert any web form from a web URL or a file on your PC into a database table in dbQwikSite and generate sets of web pages from your new table. This powerful new functionality allows you to build "back ends" with amazing ease.
"Universal" Database Table Editor
In version 4.2 we introduced several ways that you could create tables in a local (MS Access format) database. Now you get even more power, with the introduction of the "Universal" Table Editor. You can edit the structure of any table available via your database connection. This means you can modify not only local tables, but also tables in mySQL, Oracle, MS SQL, MS Access, whatever database your dbQwikSite project is connected to during design. Add/Edit/Change Fields, manage identifiers, and manage indexes.
Refresh Datasets Option
You can now manually force a database schema refresh in dbQwikSite. A new option "Refresh Dataset" is found in the explorer menu, allowing you to check that dbQwikSite datasets are up to date with your physical database structures. The check can be done at various levels, Project, Page Group or Page. This new feature helps if you are modifying your database outside of dbQwikSite while designing pages.
Project Reporting
dbQwikSite implements a brand new reporting architecture. The project reporting architecture is based on XML and plug-in reports, so you can look forward to a growing number of project reports. Project reporting can greatly assist in managing, maintaining and troubleshooting your projects. Consolidated, structured reporting allows you to view information at a project level. In version 5.0 you will find a few of these reports. For example the project summary report gives information on all your pages, their SQL, security settings and more, presented in a single listing. You no longer need to click trough property dialogs your project design settings. If you have an Idea for a report that you would find useful, send your request to Support@TheDevShop.com
Smarter Automatic Page Items
In earlier versions, when you redefine your datasets, dbQwikSite flags any existing pages items who's field mapping have been invalidated and it inserts new page items corresponding to new fields found in the new dataset. Now, dbQwikSite will not automatically add in new fields, better preserving your current page design.
Consistency Check Enhanced
A little known feature of dbQwikSite is the Design Consistency Check. This smart little utility normally runs quietly in the background, checking your design for potential problems that may result in the generated pages not working as you expect. It checks for such things a orphan links. In this version we have added checking for any known dataset inconsistencies, that may prevent your pages from working. If any problems are detected, a dialog is shown itemizing the inconsistencies, and you can take corrective actions. This facility is also now available through the reports editor.
When testing Consistency Check now inserts a warning in the generated pages, to help you troubleshoot abnormal behavior.
XML Repository
dbQwikSite now stores your project data in XML format as well as dbh. This is a interim step to migrating to a purely XML based repository (project file). At this time both files are required by dbQwikSite. Over time the .dbh files will be dropped. Developers, experienced in XML and XSL, can query the project's XML. They can also create new reports using the new reporting plug-in architecture.
|