Thanks - it's a concerted effort with the Slipstream group. We only use
SF for the SVN.
We are trying to reinvigorate EsiObjects by:
1) Getting the next release candidate out - new server side install
(script), new Client install (NSIS) and enhanced ESI$IndexedTable class
that will be used in EsiDB. Yes, we need a new client that is not nailed
to Windows :-)
2) Continue work on EsiDB which I have been evolving (albeit slowly).
The infrastructure (error handling/logging, XML export and import, etc)
and data base (IndexedTables only at this point) are in place. BTW - the
project description is at assembla under EsiDB.
3) Convert our Computer Based Packages (MUMPS, File Manager, etc.) to
EsiObjects and EsiDB as the database and use EWD and SVG for content
delivery. I want to release everything but the content to Open Source -
got to make a little cash to support all this :-)
EsiObjects should work fine with packages that permit access to GT.M
entry points since it has an "external API" for MUMPS calls (VESOEX
routine). However, unlike the Java Gateway, events cannot be passed back
- some other mechanism would have to be used (or developed)?? At one
point a guy out in CA developed a PHP Gateway for EO but then did not
continue with the work. At some point I will integrate it with EWD. One
step at a time.
If you have the inclination (and time), we could use the help?
Terry
Terry L. Wiechmann
978-779-0257
http://www.esitechnology.com