SiteMap
Page Bottom  Work program

The User Interface

The QKW publishing system is intended to publish in a variety of formats and with the least possible effort. Whereas most publishing systems offer a luxurious array of features available through mouse clicks, the QK publishing system is designed to require the least possible effort while leaving generous possiblities for achieving very special publishing effects for those who wish to go to the trouble.

The greatest benefit of this approach is to the learning curve; one simply gets started faster. Moreover, many systems are used by people who do not use them continuously every day. For example, a project manager may use a system intensively for a day or a week or a month and then not return to it until the next round of decison-making on his project. Our approach means he is more likely to hit the ground running when returning to his project.

A second important benefit will be in our pricing structure. While our systems are available for the desktop computer running Windows today, in the future we will be part of the .net strategy where the most crucial and frequently updated parts of our systems will be accessed through a server on the internet. The parts of our system that do not need frequent updates and that are more dependent on the user will reside solely on the user's system and no server access will be required for their use. Special report formatting is certainly in this category, and so is the integration of information from our systems to other systems within the enterprise.

The formats we are developing in today are these:

The architecture of our systems includes a distinct break between work that is intensely dependent on our calculating engine and our proprietary databases and work that is not. Information is passed across this break in a special format presently called "M3M". When it is passed from server to client the format will be called "W3W".

ProCash & Landev are black boxes with 86 (81) & 182 case studies serving as test data (f8894.sf & f8794.sf). There have been several attempts to create a user interface, none satisfactory at this point (QKMDI.w3 & dESTQ). Davin Church is developing a new approach using the apl2000 grid object; prototype completed 1/27/03 (Phoenix.w3). Carl has created "views" & refresh code for the new approach that show it works quite well (Input_PVP_TEST Format_PVP_TEST). PVMs and PVPs are being handled very well after some help from James Merrill. "Views" now are organized by submenus and we have control over sequencing.

Related Links:

TaskDescriptionType TaskImportanceStatusWhoTask COA#Review DateEst. CostActual Cost
Unassigned         
The User Interface desc.52Unassigned8010   

horizontal line
to home page e-mail Page Top