The Information System Development Kit gives the developer a platform-independent method of creating Information Systems with data forms, SQL database access, database-browsing support, report generator and many other useful features. ISDK is now in a development stage and it is available only for the Linux operating system. The form module now works on text terminals using the ncurses library (not functional right now), and on the X-Window system using the GTK+ toolkit.
The Event monitor project is an approach to network management based on message passing between manager and managed nodes. It's based on a client/server platform, where the server is the manager node, and all clients are managed nodes. This tool is under development, but has lots of features implemented, like a graphical console, message passing layer, one disk monitor and clients for sending messages (both API and binary forms are provided).
ctGUI is the window system abstraction and associated widget sets in the Coral Tree Library Set. The window system abstraction currently supports X/OpenGL, X/Xlib, Win32/OpenGL, and Win32/GDI (window & event system/drawing mechanism). ctGUI (aka LEWDS and EW/WDS/IWS) provides yet another approach in addition to the approaches taken by Qt, gtk, MFC, etc.
The Coral Tree Library Set includes modules for basic operating system abstractions, general purpose templates and classes, well behaved application modules, platform independent builder, thread abstraction, network abstractions, event/window system abstraction, and a widget set for the event/window system abstraction. The library set now also includes the distributed shared memory modules.
BX/XIK automates the integration of Sitraka's (formerly KL Group) Motif based XRT widgets into Builder Xcessory PRO. After installing the XRT Integration Kit, the XRT widgets will appear on the BX PRO palette and can be "dragged-and-dropped" to create a sophisticated Motif-based user interface.
NFSv4 specifies that the RPC calls be batched into a "compound" call. There is no support for this in RPCGEN. By rearranging the ONC IDL for NFSv4 into AutoGen definitions, these templates will emit the original IDL *plus* all the code to package, send, distribute, collect, return, and dispatch the results. The distributed program author merely needs to call and supply server procedures for the routines specified in the IDL. Templates for these calls and service routines is provided, too. The NFSv4 definitions are included.