What's new with WebCLIPS
WebCLIPS moves to SourceForge.
The WebCLIPS source code and website are now hosted on SourceForge
WebCLIPS Version 2.0.3
Corrections made for Preserving facts via cookie wasn't working when the target
and source screen were the same. This has been corrected. Also cookie
expiration dates now contain the full year.
The WebCLIPS page and batlship.clp program have been updated to demonstrate
preserving facts via cookie.
For User-Defined Routers being preserved to file, errors were occurring if the
filename contained spaces. This has been corrected.
Better error reporting for the ODBCQuery interface.
- The ability to use FuzzyCLIPS for WebCLIPS screens. Please review some notes concerning Fuzzy WebCLIPS screens.
An Integrated Development Environment (IDECLIPS) now available! Includes a command-line interface with some extra functions as well as an Interactive Debugger similiar to MS Dev Studio.
WebCLIPS Version 2.0.2
First on the list is a correction of serious bug. WebCLIPS was
saving all visible facts TWICE
. This was illustrated if you tried running the battleship program
You can now save facts between session with the
PreserveFacts. This might be useful for long running programs where the person might have to stop between screens. This option will allow a person to pick up where they left off. For more information please see How facts are passed
GIFs-on-the-Fly! There are 40 functions that allow a developer to manipulate
GIF images within a WebCLIPS program. For more information
please see GIFs-on-the-Fly Functions
Miscellaneous functions! There are 5 functions that I have wanted in the
CLIPS environment. For more information please see
These new functions are 'User-Define Functions' (ala the
CLIPS Advanced Programmers Guide -- apg.pdf). The WebCLIPS
allows you to check the syntax of programs containing these new functions.
[CLIPSOutput]entry in the
WebCLIPS.INIis no longer a suggested location for temporary files. With this version the directory pointed to by this entry will be the location where temporary files are located for WebCLIPS programs only. For more information please see Administration issues
What's comingThis list is by NO MEANS cast in stone. If there is anything you would like to see implemented in WebCLIPS, please feel free to email me, I am open to ALL suggestions.
Allowing the CF for a Fuzzy-fact to be specified in a separate field.
Running WebCLIPS as an ISAPI DLL.
Five ODBC update functions for database manipulation :
ODBC-connect : This would establish a persistent connection to a database
ODBC-assert : This would be similiar to the
CLIPS/ODBC interface for embedded programs (i.e. asserting
facts based on an ODBC-based SQL query)
ODBC-command : This would allow for database update functions (i.e. Insert,
Update, Delete) using ODBC
ODBC-querycount : This would return the record count for a particular query
- ODBC-close : This would close an open database
- ODBC-connect : This would establish a persistent connection to a database
An install screen for WebCLIPS
Logging events in programs such as when files are created/deleted. An
accompanying program to help the administrator determine if files are still
needed will also be included.
Implement the FTP and HTTP protocols to allow files (scripts, binary images,
Initial screens, fact groups etc.) to reside on remote machines.
Implement HTTP and FTP routers for WebCLIPS
An email interface for WebCLIPS
. This would allow a program to send and receive email.
Remote evaluation. This would allow WebCLIPS programs to
communicate with a 'master'
CLIPS instance across the Internet.
The ability to run a WebCLIPS
as an SSI.
Date/Time objects. This would allow a developer to create, manipulate and
perform math-type functions (addition, subtraction) on date/time object.
Functions will be provided to return differences between date/time objects as
well as robust formatting similiar to the
Better Debugging Tools :
An entry in
watchitems before a program executes.
An entry in
rulesafter the program has finished executing.
An entry in
- An entry in
A run-time mechanism (probably an environment variable) to set the 'mode' of a
program from Production to T
est. This would allow developers to leave debugging code in programs for test
runs and not impact production runs.
qsort-mixedfunction to allow multifields of differing types to be sorted, at the cost of performance (of course).
msortfunction to sort LARGE fact-bases or mutlifields using merge-sort. This would be cheaper from a memory perspective and still provide an nlogn alogorithm for sorting files.
Last modified : 07-Dec-1999